On Tue, 2012-02-28 at 11:14 +0100, Maik Zumstrull wrote: > On Tue, Feb 28, 2012 at 06:09, Dan Williams <d...@redhat.com> wrote: > > > Notes I'd seen from another driver indicate that it's got a modem/PPP > > port (intf 0), a DIAG/DM port (intf 1 or 2) and the PCUI port (intf 1 or > > 2). At least the PCUI port should be able to respond to AT commands > > too. Can you talk on ttyUSB1 or ttyUSB2 with AT commands? > > > > Try "AT^GETPORTMODE" on any port that takes AT commands and see what you > > get. > > ttyUSB0 acts like a modem. That it opens instantly holds with picocom > as well, the other ones hang for a bit. > ttyUSB1 doesn't seem to take AT commands (no response). > ttyUSB2 takes AT commands. > > Both AT-capable ports reply "COMMAND NOT SUPPORT" [sic] to AT^GETPORTMODE.
But ttyUSB2 still has the close() blocking problem while ttyUSB0 does not? Dan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1330453163.29120.7.ca...@dcbw.foobar.com
