The Option GTM681W uses a qualcomm chip and can be
served by the qcserial device driver.
Signed-off-by: Richard Weinberger <[email protected]>
---
drivers/usb/serial/qcserial.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/serial/qcserial.c b/drivers/usb/serial/qcserial.c
index 59b32b7..bd794b4 100644
--- a/drivers/usb/serial/qcserial.c
+++ b/drivers/usb/serial/qcserial.c
@@ -118,6 +118,7 @@ static const struct usb_device_id id_table[] = {
{USB_DEVICE(0x1199, 0x901b)}, /* Sierra Wireless MC7770 */
{USB_DEVICE(0x12D1, 0x14F0)}, /* Sony Gobi 3000 QDL */
{USB_DEVICE(0x12D1, 0x14F1)}, /* Sony Gobi 3000 Composite */
+ {USB_DEVICE(0x0AF0, 0x8120)}, /* Option GTM681W */
/* non Gobi Qualcomm serial devices */
{USB_DEVICE_INTERFACE_NUMBER(0x0f3d, 0x68a2, 0)}, /* Sierra Wireless MC7700 Device Management */
--
1.8.2.3
Richard Weinberger <[email protected]> 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?
Bjørn
Am 24.05.2013 15:18, schrieb Bjørn Mork:
> Richard Weinberger <[email protected]> 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.
Thanks,
//richard
Richard Weinberger <[email protected]> writes:
> Am 24.05.2013 15:18, schrieb Bjørn Mork:
>> Richard Weinberger <[email protected]> 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.
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
On Fri, 2013-05-24 at 20:25 +0200, Bjørn Mork wrote:
> Richard Weinberger <[email protected]> writes:
> > Am 24.05.2013 15:18, schrieb Bjørn Mork:
> >> Richard Weinberger <[email protected]> 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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html