Yes, this dumping is normal behavior in the current
kernel (2.4.0-test2). Some of it probably does depend
on CONFIG_USB_DEBUG (as you suggested in another message),
but if a driver for a device is not already loaded,
we currently dump the device's descriptors.
~Randy
-----Original Message-----
From: Eddie Kuns [mailto:[EMAIL PROTECTED]]
Sent: Sunday, June 25, 2000 6:49 PM
To: '[EMAIL PROTECTED]'
Cc: Dunlap, Randy; 'Martin Mares'; [EMAIL PROTECTED]
Subject: Re: [linux-usb] Re: usb-ohci insmodding not working because of
IRQ 0 ...
I can't remember if I posted or not, but with 2.4.0-test2, I am now
working 100% with USB and my pegasus driven network device. I have only
one minor complaint, grin. I have USB built into the kernel but
"pegasus" built as a module. When booting, I get this:
[snip kernel messages]
I don't know about the mouse. (I can't get it to work at all.) But the
EZ USB/Ethernet Converter works *perfectly* after the system is up. As
y'all can tell since I'm using that network connection to type this!
Is this a currently normal behavior of the 2.4.0-test2 USB code? ie, if
USB is built in to the kernel and a device is plugged into the USB bus
that requires a modularized driver, you'll always get this?
I am very, very happy right now. I can live with all that dumped text.
It's just too cool to have it all working.
Thanks!
Eddie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
