On 2/26/07, Pete Zaitcev <[EMAIL PROTECTED]> wrote: > On Mon, 26 Feb 2007 18:32:06 -0500, "Jon Smirl" <[EMAIL PROTECTED]> wrote: > > On 2/26/07, Greg KH <[EMAIL PROTECTED]> wrote: > > > > But why in the world would we care? These busses can come and go in any > > > number of varied and different ways. If you try to rely on a bus id > > > then you are going to be wrong eventually. > > > > The problem is that usbmon is bus number oriented. When I boot my bus > > numbers get randomly assigned so I have to manually look for where my > > EHCI bus ended up before monitoring on it. > > I always ask my users to deliver /proc/bus/usb/devices together > with the relevant usbmon trace. I think this is hinted in the usbmon.txt, > although perhaps I need to be more explicit.
That's doesn't help with figuring out which bus to monitor. I just find it annoying that I have to recheck which bus I am looking at after each reboot. I can live with not finding a solution for this, but it is annoying. It forces the steps of doing lsusb, look for your device, noting the bus number and then monitoring the right bus. It also doesn't let me write Wireshark modules to automatically decode class and device specific streams. Having something query the descriptors when the monitoring first starts fixes all of the decoding problems. This has to be solved or it is a waste of time implementing Wireshark support. This has to go into usbmon or libpcap. > > -- Pete > -- Jon Smirl [EMAIL PROTECTED] ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
