Marcel
Okay, i did understand your statement enough to hear that I had designed my driver
incorrectly.
So a driver for a hid-compliant device, non-mouse, non-keyboard, should probably live
in user
space.
If possible, please excuse my ignorance.
This "driver" then should be a lib that applications will link against?
Do you know if it is possible to submit interrupt urbs from user space with completion
procs?
Something like:
urb = usb_fill_int_urb ( udev, usb_rcvintpipe( ... ) ... );
usb_submit_urb( urb );
I'd hoped this driver could create a devfs (or procfs) file which could be cat'd
Do you know if this is possible from user space?
Sincerely
ray
--- Marcel Holtmann <[EMAIL PROTECTED]> wrote:
> no. The input devices like mice, keyboards etc. will be still in kernel
> space, but for other devices I don't really see any need to have a
> driver inside the kernel. However this is not my decision.
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
