Folks, I stumbled into a couple of questions for which some on this list might know the answer rightaway, and, if possible, i like to learn about your advice or opinion.
I'm currently specifying the comminication protocol for a usb controlled TV set. It appears as if something along the lines of the monitor class could be used. It is for channel setting, loudness, power control, and all that kind of stuff. After a glance over the monitor class, it seems to be the most standard conformant way. Is that the right way to go? Or, do you consider the monitor class unsuited for my intention and advice to better do some free style vendor specific interface? For the userland, I thought the hiddev driver might be fine, but a look into the source showed that "write" is implemented as "return -EINVAL". That's strange for me. Is there any deep intention behind it or is it just an omission i should fill in? Or, as another alternative should i better go and do a user space driver via libusb instead? What basically confuses me most is that the HID class appears throughout being considered as a input-_only_ thingy in the linux drivers. Now how i understand hid, it is well intended to control a hid device, also. Again my question whether not having implemented writable devices is a casual omission or something really intended due your deeper usb understanding. Thanks for your help -lars ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
