On Mon, Apr 26, 2010 at 05:36:15PM +0200, Robert Lukassen wrote: > f_vdc > ----- > The video function is an implementation of the Video Device Class. It > supports Bulk video mode only. At initialization, it attaches itself to > a framebuffer device (defaults to the first), and takes its properties > (currently only width and height) and exposes these to the USB host. > This implementation requires the framebuffer to hold pixel data in > RGB565 format. > > A video frame is send over a Bulk endpoint each time the framebuffer > 'pans', so it can be used 'transparently' by applications that already > deal with a double-buffered framebuffer. 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? > f_adc > ----- > This audio function is an implementation of the Audio Device Class and > implements bi-directional audio streaming. The user-space side of this > function is an ALSA soundcard with two devices, one for input and one > for output. How does this compare to the in-kernel version? > f_hidc > ------ > This is an 'implementation' of the Human Interface Device Class. There > is a small framework that supports multiple reports. Added are two > report implementation. One is for a report that allows delivery of 'raw > key' events, and one is for delivery of 'raw touchpanel' events. Both > feed received events directly into the input framework. How does this compare to the one that has been submitted recently? > drivers/usb/gadget/f_adc.c | 2157 > ++++++++++++++++++++++++++++++++++ Your patch is linewrapped and can't be applied :( Thanks for posting this, greg k-h -- 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
