Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-16 Thread Robert Marquardt
Alan Stern wrote: On the other hand, this proposal involves adding a fair amount of overhead (all those .owner fields) for a rather small benefit. And it involves modifying a core kernel subsystem (kernel/module.c). All to prevent certain unlikely sorts of errors when removing a module -- some

Re: [linux-usb-devel] usb hid: reset NumLock

2007-04-03 Thread Robert Marquardt
Jiri Kosina wrote: As this quirk is only needed once in the initialization method, we could probably get rid of it and just put and explicit test for PID and VID there (with apropriate comment). We can't afford wasting quirk entries, as we are slowly running out of them. Is it a problem of t

Re: [linux-usb-devel] [RFC] HID bus design overview.

2007-04-02 Thread Robert Marquardt
Jiri Kosina wrote: I agree. I am aware of devices for which just inspecting the parsed data would be OK (some keyboards with usage mappings which are not defined by HUT, for example), but also of devices which require special handling on the report level - Robert Marquardt pointed me in a

Re: [linux-usb-devel] [DOC] The documentation for HID Simple Driver Interface 0.5.0

2007-03-05 Thread Robert Marquardt
Jiri Kosina wrote: In addition to that, as I stated in some previous e-mail, I am currently working on new 'hidraw' interface, which will provide more flexibility to userland applications willing to operate on raw HID data, than they currently have with hiddev. I do not know too much about t