On Sat, 08 May 2004 19:51:42 -0700 David Brownell <[EMAIL PROTECTED]> wrote:
Ok... applied that patch and rewent through the boot-up sequence and checked the
output of dmesg.
//-------------------------------------------------------
ehci_hcd 0000:00:02.2: GetStatus port 1 status 003402 POWER OWNER sig=k CSC
hub 1-0:1.0: port 1, status 0, change 1, 12 Mb/s
ehci_hcd 0000:00:02.2: GetStatus port 5 status 001803 POWER sig=j CSC CONNECT
hub 1-0:1.0: port 5, status 501, change 1, 480 Mb/s
hub 1-0:1.0: debounce: port 5: delay 100ms stable 4 status 0x501
ehci_hcd 0000:00:02.2: port 5 full speed --> companion
ehci_hcd 0000:00:02.2: GetStatus port 5 status 003001 POWER OWNER sig=se0
CONNECT
ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [3] = 0x00010101 CSC PPS CCS
hub 2-0:1.0: port 3, status 101, change 1, 12 Mb/s
hub 2-0:1.0: debounce: port 3: delay 100ms stable 4 status 0x101
ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [3] = 0x00100103 PRSC PPS
PES CCS
usb 2-3: new full speed USB device using address 3
usb 2-3: new device strings: Mfr=1, Product=2, SerialNumber=3
usb_control_msg2: result = 4
drivers/usb/core/message.c: USB device number 3 default language ID 0x409
usb_control_msg2: result = 2
usb 2-3: Product: USB Cable Modem
usb_control_msg2: result = 0
usb_control_msg2: result = 2
drivers/usb/core/usb.c: usb_hotplug
usb 2-3: registering 2-3:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
usb 2-3: registering 2-3:1.1 (config #1, interface 1)
drivers/usb/core/usb.c: usb_hotplug
usbnet 2-3:1.0: usb_probe_interface
usbnet 2-3:1.0: usb_probe_interface - got id
usbnet 2-3:1.0: CDC descriptors on config
usb_control_msg2: result = 26
usbnet: probe of 2-3:1.0 failed with error -22
drivers/usb/core/usb.c: registered new driver usbnet
//-------------------------------------------------------
The only difference is that line that says "usbnet 2-3:1.0: CDC descriptors on
config". Hmm... this gets me thinking, my CDCEther driver always says when it
loads
//-------------------------------------------------------
usb.c: registered new driver CDCEther
CDCEther.c: Ethernet information found at device configuration. Trying to use
it anyway.
CDCEther.c: Found Header descriptor, CDC version 110.
CDCEther.c: Imperfect filtering support - need sw hashing
CDCEther.c: Can't use SetEthernetMulticastFilters request
CDCEther.c: detected BULK OUT packets of size 64
//-------------------------------------------------------
Ok... so now my attention has been shifted to this "device configuration"... I
paid a little read to the usbnet.c code, and it says
//-------------------------------------------------------
/* expect strict spec conformance for the descriptors, but
* cope with firmware which stores them in the wrong place
*/
if (len == 0 && dev->udev->actconfig->extralen) {
/* Motorola SB4100 (and others: Brad Hards says it's
* from a Broadcom design) put CDC descriptors here
*/
buf = dev->udev->actconfig->extra;
len = dev->udev->actconfig->extralen;
if (len)
dev_dbg (&intf->dev,
"CDC descriptors on config\n");
}
//-------------------------------------------------------
So that was to be expected? It still does not sounds like an error message yet
to me =/ Maybe I am missing something, but usb verbose messages should had
barked somewhere else too. Maybe I should replace the calls to that
usb_control_msg2 function back to usb_control_msg? (Ah no need.. just checked
the code and it's the same except it's more "verbose"). Hmm...
> Zariel Skotlex wrote:
> > Well, my kernel is still 2.6.5, so I had to manually apply the patch's
> > chunks #2 and #3 (after 2.6.6 goes out, I'll try it on that). And this
> > is what now happens when I plugin the modem:
> >
> > ...
> > //-------------------------------------------------------
> > usbnet 2-2:1.0: usb_probe_interface
> > usbnet 2-2:1.0: usb_probe_interface - got id
> > usb_control_msg2: result = 26
> > usbnet: probe of 2-2:1.0 failed with error -22
> > drivers/usb/core/usb.c: registered new driver usbnet
> > //-------------------------------------------------------
>
> You know, it's supposed to be MUCH more informative when you enable
> CONFIG_USB_DEBUG (which, thank you!, you did).
>
> This patch should make "usbnet" more informative about what
> the real error was. In that one little stretch of init code,
> the debug messages weren't getting turned on ... :(
>
> - Dave
>
>
pgp00000.pgp
Description: PGP signature
