From: Lars Melin <larsm17@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: johan@kernel.org, bjorn@mork.no, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, Matthew Garrett <mgarrett@aurora.tech>
Subject: Re: [PATCH 1/3] USB: serial: option: Add generic MDM9207 configurations
Date: Mon, 26 Dec 2022 12:38:25 +0700 [thread overview]
Message-ID: <859a548e-299a-fbd4-1f48-44347eedef0f@gmail.com> (raw)
In-Reply-To: <20221226024307.GA12011@srcf.ucam.org>
On 12/26/2022 09:43, Matthew Garrett wrote:
> On Mon, Dec 26, 2022 at 02:08:23AM +0000, Matthew Garrett wrote:
>
> Ah, it looks like the qcmdm driver is actually just an alias for the
> serial interface, so including that here seems reasonable. I've only
> included devices I can verify, but if you like I can just turn the whole
> .inf data into IDs here?
Yes the WIN qcmdm driver is a serial driver but with dial-up support, in
linux we use the option driver and ModemManager will handle the dial-up.
So for your v2 of the patch you only need to remove the blacklisting of
interfaces #1 and #3 respectively and all should be good.
next prev parent reply other threads:[~2022-12-26 5:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 20:52 Add some USB hotspot IDs Matthew Garrett
2022-12-25 20:52 ` [PATCH 1/3] USB: serial: option: Add generic MDM9207 configurations Matthew Garrett
2022-12-26 1:23 ` Lars Melin
2022-12-26 2:08 ` Matthew Garrett
2022-12-26 2:43 ` Matthew Garrett
2022-12-26 5:38 ` Lars Melin [this message]
2022-12-25 20:52 ` [PATCH 2/3] net: usb: qmi_wwan: Add generic MDM9207 configuration Matthew Garrett
2022-12-25 20:52 ` [PATCH 3/3] USB: serial: option: Add Novatel MiFi 8800L diag endpoint Matthew Garrett
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=859a548e-299a-fbd4-1f48-44347eedef0f@gmail.com \
--to=larsm17@gmail.com \
--cc=bjorn@mork.no \
--cc=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgarrett@aurora.tech \
--cc=mjg59@srcf.ucam.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;
as well as URLs for NNTP newsgroup(s).