linux-kernel - Re: [PATCH] serial: Add Option GTM681W to qcserial device table.

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] [day] [month] [year] [list]

Message-ID: <1369434846.8000.9.camel@dcbw.foobar.com>
Date:	Fri, 24 May 2013 17:34:06 -0500
From:	Dan Williams <dcbw@...hat.com>
To:	Bjørn Mork <bjorn@...k.no>
Cc:	Richard Weinberger <richard@....at>, gregkh@...uxfoundation.org,
	jhovold@...il.com, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] serial: Add Option GTM681W to qcserial device table.

On Fri, 2013-05-24 at 20:25 +0200, Bjørn Mork wrote:
> Richard Weinberger <richard@....at> writes:
> > Am 24.05.2013 15:18, schrieb Bjørn Mork:
> >> Richard Weinberger <richard@....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@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/