Hi Raymond, > 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.
this is the general way and as always there are exceptions. I haven't seen your driver nor I have access to your device and so I am not in the right position to judge about it. But from a naive view I would say a user space program would be better and of course more easier. > If possible, please excuse my ignorance. > > This "driver" then should be a lib that applications will link against? Actually this all depends on what you wanna do with that device and what kind of users you have in mind. > 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 ); Take a look at libusb.sf.net > 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? You don't need this from user space. You simply get the data you need. Regards Marcel ------------------------------------------------------- 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
