On Fri, Feb 19, 2016 at 12:02:04AM -0800, Daniel Patrick Johnson wrote:
> Adds HP lt4114 LTE module USB ID as a Huawei device.
>
> Currently 4 ttyUSB devices are detected, but only the second two respond to
> AT commands. The first two serial ports may be falsely detected.
>
> Of the two responsi
On Thu, 2016-02-25 at 18:15 +0100, Bjørn Mork wrote:
> Dan Williams writes:
> > On Mon, 2016-02-22 at 18:03 +0700, Lars Melin wrote:
> > > On 2016-02-21 10:09, Daniel Johnson wrote:
> > > > On Fri, Feb 19, 2016 at 12:27 AM, Bjørn Mork
> > > > wrote:
> > > > > One of them is likely a QCDM port if
Dan Williams writes:
> On Mon, 2016-02-22 at 18:03 +0700, Lars Melin wrote:
>> On 2016-02-21 10:09, Daniel Johnson wrote:
>> > On Fri, Feb 19, 2016 at 12:27 AM, Bjørn Mork wrote:
>> > > One of them is likely a QCDM port if this is really a Qualcomm
>> > > based
>> > > device. The other might be
On Sun, 2016-02-21 at 12:44 +0700, Lars Melin wrote:
> On 2016-02-20 03:34, Dan Williams wrote:
> > On Fri, 2016-02-19 at 18:21 +0100, Bjørn Mork wrote:
> > > Dan Williams writes:
> > > > On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote:
> > > >
> > > > > cfg #1
> > > > > MI_00 HP Mobile Conne
On Mon, 2016-02-22 at 18:03 +0700, Lars Melin wrote:
> On 2016-02-21 10:09, Daniel Johnson wrote:
> > On Fri, Feb 19, 2016 at 12:27 AM, Bjørn Mork wrote:
> > > One of them is likely a QCDM port if this is really a Qualcomm
> > > based
> > > device. The other might be an inactive NMEA port. Seria
On 2016-02-21 10:09, Daniel Johnson wrote:
On Fri, Feb 19, 2016 at 12:27 AM, Bjørn Mork wrote:
One of them is likely a QCDM port if this is really a Qualcomm based
device. The other might be an inactive NMEA port. Serial doesn't
necessarily imply AT commands...
I found the FCC ID for the de
On 2016-02-20 03:34, Dan Williams wrote:
On Fri, 2016-02-19 at 18:21 +0100, Bjørn Mork wrote:
Dan Williams writes:
On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote:
cfg #1
MI_00 HP Mobile Connect - PC UI Interface
MI_01 HP Mobile Connect - Application Interface
MI_02 HP Mobile Connect - M
On Fri, Feb 19, 2016 at 12:27 AM, Bjørn Mork wrote:
> One of them is likely a QCDM port if this is really a Qualcomm based
> device. The other might be an inactive NMEA port. Serial doesn't
> necessarily imply AT commands...
I found the FCC ID for the device.
QISME206V-561
Searching for this a
On Fri, Feb 19, 2016 at 2:31 AM, Bjørn Mork wrote:
> Good. So you have a few alternative configs here. I forgot to ask, but
> I assume you've ended up with cfg #2 by default (because Linux has a
> class preference, making it select the first config with a non 0xff
> class as the first interface).
On Fri, 2016-02-19 at 18:21 +0100, Bjørn Mork wrote:
> Dan Williams writes:
> > On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote:
> >
> > > cfg #1
> > > MI_00 HP Mobile Connect - PC UI Interface
> > > MI_01 HP Mobile Connect - Application Interface
> > > MI_02 HP Mobile Connect - Modem
> > > M
Dan Williams writes:
> On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote:
>
>> cfg #1
>> MI_00 HP Mobile Connect - PC UI Interface
>> MI_01 HP Mobile Connect - Application Interface
>> MI_02 HP Mobile Connect - Modem
>> MI_03 HP Mobile Connect - Network Card (jungo ncm)
>> MI_04 HP Mobile Connec
On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote:
> On 2016-02-19 17:31, Bjørn Mork wrote:
> > Daniel Johnson writes:
> >
> > > > > Currently 4 ttyUSB devices are detected, but only the second
> > > > > two respond to
> > > > > AT commands. The first two serial ports may be falsely
> > > > > d
On 2016-02-19 17:31, Bjørn Mork wrote:
Daniel Johnson writes:
Currently 4 ttyUSB devices are detected, but only the second two respond to
AT commands. The first two serial ports may be falsely detected.
One of them is likely a QCDM port if this is really a Qualcomm based
device. The other m
Daniel Johnson writes:
>>> Currently 4 ttyUSB devices are detected, but only the second two respond to
>>> AT commands. The first two serial ports may be falsely detected.
>>
>> One of them is likely a QCDM port if this is really a Qualcomm based
>> device. The other might be an inactive NMEA po
>> Currently 4 ttyUSB devices are detected, but only the second two respond to
>> AT commands. The first two serial ports may be falsely detected.
>
> One of them is likely a QCDM port if this is really a Qualcomm based
> device. The other might be an inactive NMEA port. Serial doesn't
> necessar
Daniel Patrick Johnson writes:
> Adds HP lt4114 LTE module USB ID as a Huawei device.
>
> Currently 4 ttyUSB devices are detected, but only the second two respond to
> AT commands. The first two serial ports may be falsely detected.
One of them is likely a QCDM port if this is really a Qualcomm
Adds HP lt4114 LTE module USB ID as a Huawei device.
Currently 4 ttyUSB devices are detected, but only the second two respond to
AT commands. The first two serial ports may be falsely detected.
Of the two responsive serial devices the first is the source of unsolicited
information such as a SIM i
17 matches
Mail list logo
