>> f_vdc >> ... > >Is this so that a host can use a device as a video output device? Like the display-link devices? If so, very nice, I don't think we >have a driver for this yet, care to split it out so we can queue it up? No, this does not (yet) support video out. It should not be that difficult to change this, I believe the UVC (host) stuff already supports Bulk video out. It would be pretty cool indeed. >> f_adc >> ... > >How does this compare to the in-kernel version? We have been working on this stuff for quite some time now and only recently we've found that this in-kernel version exists. To late for our product engineers to start using the in-kernel version. From my brief inspection, it seems that the in-kernel version has probably a better design structure, but it does not support bi-directional audio. Our version also has a specific feature that continues a running audio stream for the application using the virtual USB soundcard, even when the USB cable is disconnected. The audio-out path will continue to generate silence, while the audio-in path simply drops the audio data at the configured rate. >> f_hidc >> ------ >> ... >> Both feed received events directly into the input framework. > >How does this compare to the one that has been submitted recently? Our requirements for this function were that it should support receiving raw-key events and touchpanel events, which were to be injected directly into the linux input framework. Next, it had to support read/write access for reports from user-space for those reports that are not handled completely by the kernel driver. There might be quite some overlap with the already posted framework. Regards, Robert -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
