On Sun, 26 Jun 2005, Helix wrote: > > > > There is no particular relationship between the results of lsusb -v and > > the usb_control_msg function, except that lsusb uses usb_control_msg > > internally. That's why you can't find any documentation or examples. :-) > > > > What other part of usb_control_msg puzzles you? > > > > I don't undertstand what parameters I have to pass to this function > considering the lsusb -v output.
The parameters have nothing at all to do with the lsusb -v output. I can't imagine why you think they are related. The parameters you need to pass to usb_control_msg are explained in the USB 2.0 Specification, available in the Developer's section at www.usb.org. > >> > How can I start creating the required entries ? > > > > What entries are you talking about? > > > > I'd like to create a minimal functionality for this device, > I wonder if is possibile to do that as Greg K-H said into his article. It probably is possible. Alan Stern ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
