[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

More info - bad HW, woody does't cut it, now have /dev/ttyACM0



Oh well, I keep posting followups to my own questions...

I'm finding more info:

1 - the thinkpad apparently has a hw problem with the USB port, so
    even though it has the latest OS, it never sees the phone.

2 - The 8600 has good hardware but the OS (woody) is too old.  That's
    the reason for the "unknown descriptor type" errors.

3 - A third (desktop) computer with USB and sarge (kernel 2.6.8 with
    CONFIG_USB_ACM) gives the following:


Bus 001 Device 002: ID 22b8:2a62 Motorola PCS 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            2 Communications
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x22b8 Motorola PCS
  idProduct          0x2a62 
  bcdDevice            0.01
  iManufacturer           1 Motorola, Inc.
  iProduct                2 Motorola E815
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           67
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower               20mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              3 Motorola Communication Interface
      CDC Header:
        bcdCDC               1.09
      CDC Call Management:
        bmCapabilities       0x03
          call management
          use DataInterface
        bDataInterface          1
      CDC ACM:
        bmCapabilities       0x0f
          connection notifications
          sends break
          line coding and serial state
          get/set/clear comm features
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              3 Motorola Communication Interface
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0

So no more USB errors.  Furthermore,  the device /dev/ttyACM0
appears after manually loading cdc-acm.  I still can't get anything out
that device with minicom so I can't really talk to the modem.
Maybe wrong baud rate or other parameter.  Or maybe this driver is still
not the right one.  I'll keep investigating tomorrow.

Augustine



Reply to: