Re: libusb+librump patch

[Antti Kantee]

On 15/10/15 01:03, Bruno Félix Rezende Ribeiro wrote:
>    uhci0 at pci0 dev 2 function 0: vendor 8086 product 24c2 (rev. 0x01)
>    uhci0: interrupting at pausebreak
>    usb0 at uhci0: USB revision 1.0
>    uhub0 at usb0: vendor 8086 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
>    uhub0: 2 ports with 2 removable, self powered
>    uhci1 at pci0 dev 3 function 0: vendor 8086 product 24c4 (rev. 0x01)
>    uhci1: interrupting at pausebreak
>    usb1 at uhci1: USB revision 1.0
>    uhub1 at usb1: vendor 8086 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
>    uhub1: 2 ports with 2 removable, self powered
>    uhci2 at pci0 dev 4 function 0: vendor 8086 product 24c7 (rev. 0x01)
>    uhci2: interrupting at pausebreak
>    usb2 at uhci2: USB revision 1.0
>    uhub2 at usb2: vendor 8086 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
>    uhub2: 2 ports with 2 removable, self powered
>  [snip]
>    uhub1: device problem, disabling port 2

> The relevant message is: "uhub1: device problem, disabling port 2".
> That, I think, is the only difference between running 'listdevs' with
> and without a USB device attached to the system.  Any ideas?

I have some very distant memories of that happening when the PCI 
implementation does not correctly deal with multifunction devices and 
the USB stack gets confused when it doesn't find the companion devices. 
 I might be remembering wrong, but at least as supporting evidence I 
observe that there are no fun!=0 devices probed.