Re: umodem(4) with "no pointer to data interface"

[Ryo ONODERA <ryo_on%yk.rim.or.jp@localhost>]

Hi,

From: Brett Lymn <blymn%internode.on.net@localhost>, Date: Tue, 21 Jan 2014 
20:05:36 +1030

> On Mon, Jan 20, 2014 at 07:18:32PM +0900, Ryo ONODERA wrote:
>> 
>> I have gotten strange dmesg output for umodem(4).
>> How to avoid this strangeness?
>> 
> 
> By not forcing umodem to connect a non-modem interface?
> Does umodem not attach at all without your modifications?  If it doesn't
> then what are the class and subclass values?

Without my modification, my USB modem is recognized as single ugen(4).

Here is output of usbdevs(8) without my modification.

   port 1 addr 11: full speed, power 100 mA, config 1, USB Modem(0x1329), 
Conexant(0x0572), rev 1.00, serial 24680246
     ugen0

and output of dmesg.

ugen0 at uhub4 port 1
ugen0: Conexant USB Modem, rev 1.10/1.00, addr 11


How to get class and subclass value for USB device?


> The attach process should step through all the interfaces declared on
> the device and only attach to the one that has the ACM_CDC class.  Hard
> to say what the other interface is for - perhaps proprietry call
> monitoring or something.

I see.

Thank you.

--
Ryo ONODERA // ryo_on%yk.rim.or.jp@localhost
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB  FD1B F404 27FA C7D1 15F3