Re: [linux-usb-devel] usbmon: Extended text API

2007-02-28 Thread Jon Smirl
On 2/26/07, Alan Stern <[EMAIL PROTECTED]> wrote: > On Mon, 26 Feb 2007, Greg KH wrote: > > > On Mon, Feb 26, 2007 at 05:14:38PM -0500, Jon Smirl wrote: > > > On 2/26/07, Alan Stern <[EMAIL PROTECTED]> wrote: > > > >> Another way to control this would be to put all of the USB Host IDs > > > >> into

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-27 Thread Jon Smirl
On 2/26/07, Alan Stern <[EMAIL PROTECTED]> wrote: > On Mon, 26 Feb 2007, Jon Smirl wrote: > > I'd vote for getting rid of the text mode interface to usbmon and > > replace it with a tiny app which decodes the binary interface. You > > could then give the app a device or class ID and it would filter

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-26 Thread Alan Stern
On Mon, 26 Feb 2007, Jon Smirl wrote: > > Remember too that it's possible to hotplug USB buses. There are USB > > controllers on PCcards. > > If CONFIG_HOTPLUG is on the new _init PCI ID table in USB core won't > be discarded. Hotplug will work the same way it works currently. You > don't need t

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-26 Thread Alan Stern
On Mon, 26 Feb 2007, Greg KH wrote: > On Mon, Feb 26, 2007 at 05:14:38PM -0500, Jon Smirl wrote: > > On 2/26/07, Alan Stern <[EMAIL PROTECTED]> wrote: > > >> Another way to control this would be to put all of the USB Host IDs > > >> into a single module (usbcore), and then that module would load i

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-26 Thread Alan Stern
On Mon, 26 Feb 2007, Jon Smirl 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 probl

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-26 Thread Jon Smirl
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 w

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-26 Thread Pete Zaitcev
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 t

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-26 Thread Jon Smirl
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 bo

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-26 Thread Greg KH
On Mon, Feb 26, 2007 at 05:14:38PM -0500, Jon Smirl wrote: > On 2/26/07, Alan Stern <[EMAIL PROTECTED]> wrote: > >> Another way to control this would be to put all of the USB Host IDs > >> into a single module (usbcore), and then that module would load in > >> ehci, uhci, etc. > > > >That would wor

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-26 Thread Jon Smirl
On 2/26/07, Alan Stern <[EMAIL PROTECTED]> wrote: > > Another way to control this would be to put all of the USB Host IDs > > into a single module (usbcore), and then that module would load in > > ehci, uhci, etc. > > That would work. But it would be a lot of effort for not much advantage. It's n

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-26 Thread Alan Stern
On Mon, 26 Feb 2007, Jon Smirl wrote: > > You could remove this indeterminism by explicitly loading ehci-hcd and > > uhci-hcd (that is the preferred order) in a system start-up script before > > udev. In FC6, for example, the modules are loaded from an initramfs > > script. > > In think the usb

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-26 Thread Jon Smirl
On 2/26/07, Alan Stern <[EMAIL PROTECTED]> wrote: > On Mon, 26 Feb 2007, Jon Smirl wrote: > > > My instability seems to come from a race between EHCI and UHCI. I have > > one EHCI and four UHCI host controllers (ICH5). > > > > I usually get this at boot: > > bus 1 UHCI-A > > bus 2 UHCI-B > > bus 3

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-26 Thread Alan Stern
On Mon, 26 Feb 2007, Jon Smirl wrote: > My instability seems to come from a race between EHCI and UHCI. I have > one EHCI and four UHCI host controllers (ICH5). > > I usually get this at boot: > bus 1 UHCI-A > bus 2 UHCI-B > bus 3 UHCI-C > bus 4 UHCI-D > bus 5 EHCI > > But occasionally I get thi

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-26 Thread Jon Smirl
On 2/25/07, Alan Stern <[EMAIL PROTECTED]> wrote: > On Sat, 24 Feb 2007, Jon Smirl wrote: > > > On 2/24/07, Pete Zaitcev <[EMAIL PROTECTED]> wrote: > > > Also, Jon was hitting some problems with tcpdump and Paolo's libpcap, > > > so let's keep one more revision stable to help them to figure this ou

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-25 Thread Alan Stern
On Sun, 25 Feb 2007, Jon Smirl wrote: > I seem to be in an unstable race between the ehci and uhci buses for > assigning bus #1. That shouldn't happen unless you have enabled the config option for for parallel PCI probing. If you have, you might as well turn it off -- it has caused a number of

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-24 Thread Jon Smirl
On 2/25/07, Alan Stern <[EMAIL PROTECTED]> wrote: > On Sat, 24 Feb 2007, Jon Smirl wrote: > > > On 2/24/07, Pete Zaitcev <[EMAIL PROTECTED]> wrote: > > > Also, Jon was hitting some problems with tcpdump and Paolo's libpcap, > > > so let's keep one more revision stable to help them to figure this ou

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-24 Thread Jon Smirl
On 2/25/07, Pete Zaitcev <[EMAIL PROTECTED]> wrote: > On Sat, 24 Feb 2007 22:55:28 -0500, "Jon Smirl" <[EMAIL PROTECTED]> wrote: > > > For example, as far as I can tell there is no info in the capture > > packet stream describing the attached devices unless I so something > > like "lsusb -v" while

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-24 Thread Pete Zaitcev
On Sat, 24 Feb 2007 22:55:28 -0500, "Jon Smirl" <[EMAIL PROTECTED]> wrote: > For example, as far as I can tell there is no info in the capture > packet stream describing the attached devices unless I so something > like "lsusb -v" while data is being captured. [...] True, the intent was that the

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-24 Thread Alan Stern
On Sat, 24 Feb 2007, Jon Smirl wrote: > On 2/24/07, Pete Zaitcev <[EMAIL PROTECTED]> wrote: > > Also, Jon was hitting some problems with tcpdump and Paolo's libpcap, > > so let's keep one more revision stable to help them to figure this out > > and bring libpcap into shape. They may yet find a ker

Re: [linux-usb-devel] usbmon: Extended text API

2007-02-24 Thread Jon Smirl
On 2/24/07, Pete Zaitcev <[EMAIL PROTECTED]> wrote: > Also, Jon was hitting some problems with tcpdump and Paolo's libpcap, > so let's keep one more revision stable to help them to figure this out > and bring libpcap into shape. They may yet find a kernel bug too. I wish the bus numbers were stabl

[linux-usb-devel] usbmon: Extended text API

2007-02-24 Thread Pete Zaitcev
This patch adds a new text API, codenamed '1u', which captures more URB fields than old '1t' interface did. Also the '1u' text API is compatible with the future "bus zero" extension. Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]> Acked-by: Alan Stern <[EMAIL PROTECTED]> --- Alan "acked this", I