From: Dan Williams <dcbw@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Richard Weinberger <richard@nod.at>,
gregkh@linuxfoundation.org, jhovold@gmail.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: Add Option GTM681W to qcserial device table.
Date: Fri, 24 May 2013 17:34:06 -0500 [thread overview]
Message-ID: <1369434846.8000.9.camel@dcbw.foobar.com> (raw)
In-Reply-To: <87ehcwfd6m.fsf@nemi.mork.no>
On Fri, 2013-05-24 at 20:25 +0200, Bjørn Mork wrote:
> Richard Weinberger <richard@nod.at> writes:
> > Am 24.05.2013 15:18, schrieb Bjørn Mork:
> >> Richard Weinberger <richard@nod.at> writes:
> >>
> >>> The Option GTM681W uses a qualcomm chip and can be
> >>> served by the qcserial device driver.
> >>
> >> Should it also be added to the qmi_wwan driver?
> >
> > Don't know. But I can happily test it. :)
> > Can you please explain me how to use the qmi_wwan driver?
> > I've never used it.
>
> The QMI management protocol is delegated to userspace using a
> /dev/cdc-wdmX character device. So you need a userspace component to
> test the driver, like for example libqmi. See
> http://sigquit.wordpress.com/2012/08/20/an-introduction-to-libqmi/ for a
> short intro.
Various marketing collateral suggests the 681W is a Gobi3K and thus it
most certainly should also get added to qmi_wwan. lsusb -v output for
it would be helpful too I think?
http://www.option.com/product/gtm681wgtm689w/
Dan
> This library is packaged in Debian. Don't know the status of other
> distros.
>
> The driver supports dynamic device IDs, so if you have qcserial bound to
> all serial ports, and there is a QMI interface with no driver bound yet,
> then testing should be as easy as
>
> modprobe qmi_wwan
> echo "0af0 8120" >/sys/bus/usb/drivers/qmi_wwan/new_id
> qmicli -d /dev/cdc-wdm0 --dms-get-manufacturer
>
>
>
> Bjørn
> --
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-05-24 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 10:01 Richard Weinberger
2013-05-24 13:18 ` Bjørn Mork
2013-05-24 15:35 ` Richard Weinberger
2013-05-24 18:25 ` Bjørn Mork
2013-05-24 22:34 ` Dan Williams [this message]
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=1369434846.8000.9.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=bjorn@mork.no \
--cc=gregkh@linuxfoundation.org \
--cc=jhovold@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=richard@nod.at \
/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
all inboxes | Powered by JetHome®