From: Shrirang Bagul <shrirang.bagul@canonical.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: johan@kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: qmi_wwan: add Dell DW5818, DW5819
Date: Mon, 20 Nov 2017 18:01:15 +0800 [thread overview]
Message-ID: <1511172075.3901.4.camel@canonical.com> (raw)
In-Reply-To: <87lgj1thg9.fsf@miraculix.mork.no>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
On Mon, 2017-11-20 at 10:41 +0100, Bjørn Mork wrote:
> Shrirang Bagul <shrirang.bagul@canonical.com> writes:
>
> > Dell Wireless 5819/5818 devices are re-branded Sierra Wireless MC74
> > series modems which will by default boot with vid 0x413c and pid's
> > 0x81cf, 0x81d0, 0x81d1,0x81d2. Along with qcserial, these modems support
> > qmi_wwan on the usb interface #12.
>
> NAK,
>
> Interace #12 is MBIM, as shown by the device descriptors. Please provide
> those descriptors and you will see that this interface is clearly a CDC
> MBIM class interface.
>
> Yes, I know these modems probe the control protocol so that you can make
> QMI work on an MBIM control interface by sending it a QMI request as the
> first messsage. This is still wrong, abusing a quirky firmware
> feature.
>
> You need to reconfigure the modem for QMI using the Sierra specific AT
> command or QMI request (tunneled in MBIM!) to properly switch it to QMI
> mode, which will appear as a vendor specific interface number 8 (and 10
> if you enable both QMI functions).
Understood. Needs more work, will resend with fixes.
- Shrirang
>
>
>
>
>
> Bjørn
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-11-20 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 9:27 [PATCH] net: qmi_wwan: add Dell DW5818, DW5819 Shrirang Bagul
2017-11-20 9:41 ` Bjørn Mork
2017-11-20 10:01 ` Shrirang Bagul [this message]
2017-11-20 10:28 ` Lars Melin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1511172075.3901.4.camel@canonical.com \
--to=shrirang.bagul@canonical.com \
--cc=bjorn@mork.no \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox