lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <98b50ae7-b889-6811-476e-9cdc8a62a484@gmail.com>
Date:   Thu, 26 Apr 2018 18:40:46 +0700
From:   Lars Melin <larsm17@...il.com>
To:     Bjørn Mork <bjorn@...k.no>,
        Johan Hovold <johan@...nel.org>
Cc:     SZ Lin (林上智) <sz.lin@...a.com>,
        stable <stable@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
        Dan Williams <dcbw@...hat.com>
Subject: Re: [PATCH] USB: serial: option: adding support for ublox R410M

On 4/26/2018 18:39, Lars Melin wrote:
> On 4/26/2018 18:19, Bjørn Mork wrote:
>> Anyway, Qualcomm based designs are definitely handled by both drivers.
>> Using qcserial only makes sense if the interface layout matches one of
>> the defined shared schemes, which currently are:
>>
>>     QCSERIAL_G2K = 0,    /* Gobi 2000 */
>>     QCSERIAL_G1K = 1,    /* Gobi 1000 */
>>     QCSERIAL_SWI = 2,    /* Sierra Wireless */
>>     QCSERIAL_HWI = 3,    /* Huawei */
> 
> It seems to me that this Quectel device matches the interface layout for 
> Gobi1K:
> 
>           * Gobi 1K USB layout:
>           * 0: DM/DIAG (use libqcdm from ModemManager for communication)
>           * 1: serial port (doesn't respond)
>           * 2: AT-capable modem port
>           * 3: QMI/net
>           */
> 
> /Lars

Ublox, not Quectel..

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ