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:


hub.c: portstatus 301, change 1, 1.5 Mb/s
hub.c: portstatus 303, change 10, 1.5 Mb/s
usb.c: USB new device connect, assigned device number 2
usb.c: kmalloc IF c152dd80, numif 1
usb.c: skipped 1 class/vendor specific interface descriptors
usb.c: new device strings: Mfr=1, Product=2, SerialNumber=0
usb.c: USB device number 2 default language ID 0x409
Manufacturer: Cypress Sem.
Product: Cypress USB Mouse
usb.c: unhandled interfaces on device
usb.c: This device is not recognized by any installed USB driver.
  Length              = 18
  DescriptorType      = 01
  USB version         = 1.00
  Vendor:Product      = 05fe:0003
  MaxPacketSize0      = 8
  NumConfigurations   = 1
  Device version      = 4.9d
  Device Class:SubClass:Protocol = 00:00:00
    Per-interface classes
Configuration:
  bLength             =    9
  bDescriptorType     =   02
  wTotalLength        = 0022
  bNumInterfaces      =   01
  bConfigurationValue =   01
  iConfiguration      =   04
  bmAttributes        =   a0
  MaxPower            =  100mA

  Interface: 0
  Alternate Setting:  0
    bLength             =    9
    bDescriptorType     =   04
    bInterfaceNumber    =   00
    bAlternateSetting   =   00
    bNumEndpoints       =   01
    bInterface Class:SubClass:Protocol =   03:01:02
    iInterface          =   05
    Endpoint:
      bLength             =    7
      bDescriptorType     =   05
      bEndpointAddress    =   81 (in)
      bmAttributes        =   03 (Interrupt)
      wMaxPacketSize      = 0004
      bInterval           =   0a
hub.c: port 2 connection change
hub.c: portstatus 101, change 1, 12 Mb/s
hub.c: portstatus 103, change 10, 12 Mb/s
usb.c: USB new device connect, assigned device number 3
usb.c: kmalloc IF c152dec0, numif 1
usb.c: new device strings: Mfr=1, Product=2, SerialNumber=3
usb.c: USB device number 3 default language ID 0x409
Manufacturer: SMC, Inc
Product: EZ USB/Ethernet Converter
SerialNumber: 0001
usb.c: unhandled interfaces on device
usb.c: This device is not recognized by any installed USB driver.
  Length              = 18
  DescriptorType      = 01
  USB version         = 1.10
  Vendor:Product      = 0707:0200
  MaxPacketSize0      = 8
  NumConfigurations   = 1
  Device version      = 1.01
  Device Class:SubClass:Protocol = 00:00:00
    Per-interface classes
Configuration:
  bLength             =    9
  bDescriptorType     =   02
  wTotalLength        = 0027
  bNumInterfaces      =   01
  bConfigurationValue =   01
  iConfiguration      =   00
  bmAttributes        =   a0
  MaxPower            =  160mA

  Interface: 0
  Alternate Setting:  0
    bLength             =    9
    bDescriptorType     =   04
    bInterfaceNumber    =   00
    bAlternateSetting   =   00
    bNumEndpoints       =   03
    bInterface Class:SubClass:Protocol =   00:00:00
    iInterface          =   00
    Endpoint:
      bLength             =    7
      bDescriptorType     =   05
      bEndpointAddress    =   81 (in)
      bmAttributes        =   02 (Bulk)
      wMaxPacketSize      = 0040
      bInterval           =   00
    Endpoint:
      bLength             =    7
      bDescriptorType     =   05
      bEndpointAddress    =   02 (out)
      bmAttributes        =   02 (Bulk)
      wMaxPacketSize      = 0040
      bInterval           =   00
    Endpoint:
      bLength             =    7
      bDescriptorType     =   05
      bEndpointAddress    =   83 (in)
      bmAttributes        =   03 (Interrupt)
      wMaxPacketSize      = 0008
      bInterval           =   01

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

P.S.  In other news, I replaced my computer's internal parallel port
cable and my printer works again.  I must have damaged that cable
somehow while installing the USB cables, although I don't see any
obvious damage.  Huh.  Anyway, it's all working.  I'll send another post
to ask questions about the USB mouse.

-- 
  Eddie Kuns  |  Home: [EMAIL PROTECTED]
--------------/  URL:  http://www.physics.rutgers.edu/~ekuns/
  "Ah, savory cheese puffs, made inedible by time and fate."  -- The
Tick

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to