Marcel I was concerned that your statement implied:
"Any HID-compatible device should be controlled from user space." Did you intend this meaning, or did I infer incorrectly? As for the device, it is a USB temperature sensor: http://www.vernier.com/go/index.html I plan to submit the driver after I comply with "the" coding style ... I'm a "tab=4", "curly-braces on their own line" kind of guy. Sincerely ray --- Marcel Holtmann <[EMAIL PROTECTED]> wrote: > Hi Raymond, > > > This is off the topic of the EIZO device driver. > > Please excuse my ignorance if this is not an acceptable way to ask an off topic > > question. > > > > In response to Jan, you wrote that: > > > The final goal after we moved over to generic HID driver should be to > > > send/receive any HID report to/from the device from the user space. > > > > I've nearly completed my first device driver and > > it happens to be for a hid-compliant device. > > The driver uses Set Report to command the device and receives results/readings off > > the > interrupt > > pipe. > > > > Do I read your response as saying I have not written this as a kernel space driver? > > Does this final goal mean there is little/no chance of this driver being > > accepted/integrated? > > I have no idea about what kind of driver you are talking nor for what > kind of device this driver is good for. Show us the source code and we > will see ;) > > Regards > > Marcel > > > _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com ------------------------------------------------------- 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
