Hans de Goede wrote: > > Let me try to explain why, just as there is a huge difference between > internal functionality and something only available when doing extra > stuff outside of libusbx, there is a huge difference between being > able to access a device without detaching the driver, and accessing it > with detaching the driver. Lets say we've a keyboard with some extra > functionality, ie an lcd display, or whatever. And the functionality > is available through custom hid reports on the same hid interface as > where the actual keyboard functionality is. Then surely having a tool > for the lcd display detaching the driver is a bad idea, since that > will mean that the lcd can now be used, but at the cost of loosing the > keyboard ...
I'm not sure I buy that argument. Everything on that keyboard HID interface should be keyboard HID related. If the LCD isn't keyboard related, then it should be on a separate interface. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
