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

[Brett Lymn <blymn%internode.on.net@localhost>]

On Thu, Jan 30, 2014 at 12:09:47PM +0900, Ryo ONODERA wrote:
> 
> However your code does not work for my USB modem.
> dmesg is here. Only control interface is detected.
> 
> umodem0 at uhub2 port 1 configuration 1 interface 0
> umodem0: Conexant USB Modem, rev 1.10/1.00, addr 3, iclass 2/2
> umodem0: data interface 0, has no CM over data, has no break
> umodem0: Could not find data bulk in
> 

bummer - this is getting a bit further though, no?  At least it is
coming up as umodem instead of ugen.

> And diff for usb_quirks.c is not used.
> 

I am not sure what you mean by this - did you not apply this diff or
that you don't believe it has been effective?

> 
> By the way, for blute-forcing interface, such mechanism would be
> implemented in umodem_match function.
> How about this code?
> 

I am not sure.

>  
> 
> Resulting dmesg is here.
> 
> umodem0 at uhub2 port 1 configuration 1 interface 1
> umodem0: Conexant USB Modem, rev 1.10/1.00, addr 10, iclass 10/0
> umodem0: data interface 1, has CM over data, has break
> ucom1 at umodem0
> 
> Functionality is not tested yet, but it should work.
> 

Well, maybe it will, maybe it won't.  Looking back at the output from
the tool I sent you it looks like there is an interrupt pipe on
interface 0.  I believe that would be used to report line status changes
- things like DCD asserted, that sort of thing.  The concern I have with
your code is that it may appear to work in that you get a com interface
but you may be missing the control lines.

-- 
Brett Lymn
Staple Guns: because duct tape doesn't make that KerCHUNK sound - xkcd.com