From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Huawei 3131 with idVendor=12d1, idProduct=14fe
Date: Mon, 04 Jan 2016 10:18:57 -0600 [thread overview]
Message-ID: <568A9B71.7080208@gmail.com> (raw)
In-Reply-To: <CADnUhn1iurv551=GeaJpP23Jscpu9GDtcybPSZ4tTePrvS-NNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
Hi Matti,
> -------------------------
> usbserial:
> --------------------------
> usbserial: USB Serial support registered for GSM modem (1-port)
> usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
> usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
> usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
>
Are you sure the ttys are handled by the 'usbserial' module and not
'option'? If they really are, then you might need to update
plugins/udevng.c appropriately.
Right now I see the following in the vendor_list[] table:
{ "huawei", "option", "201e" },
{ "huawei", "cdc_wdm", "12d1" },
{ "huawei", "cdc_ether", "12d1" },
{ "huawei", "qmi_wwan", "12d1" },
{ "huawei", "option", "12d1" },
You probably also need to add an entry for cdc_ncm. See the recent
patch adding similar support for mbm:
git show b04fabcda34b6433209bacab32b78a95b1c11b3e
I'd start with adding the cdc_ncm entry to vendor_list[] table and see
if that makes things work.
Regards,
-Denis
next prev parent reply other threads:[~2016-01-04 16:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 10:31 Huawei 3131 with idVendor=12d1, idProduct=14fe matti kaasinen
2015-12-31 8:39 ` matti kaasinen
2016-01-04 16:18 ` Denis Kenzior [this message]
[not found] <CADnUhn1efXRB7fZGkSfsToHH5gxd-tK4OxJxF9MhP334P1Pvcw@mail.gmail.com>
2016-01-11 15:02 ` matti kaasinen
2016-01-11 17:18 ` Denis Kenzior
2016-01-11 17:52 ` matti kaasinen
2016-01-12 8:38 ` matti kaasinen
2016-01-12 8:47 ` matti kaasinen
2016-01-12 9:40 ` matti kaasinen
2016-01-12 10:04 ` matti kaasinen
2016-01-12 16:30 ` Denis Kenzior
2016-01-12 16:46 ` matti kaasinen
2016-01-12 16:52 ` Denis Kenzior
2016-01-12 16:56 ` matti kaasinen
2016-01-12 17:20 ` Denis Kenzior
2016-01-13 10:40 ` matti kaasinen
2016-01-13 16:04 ` Denis Kenzior
2016-01-14 10:19 ` matti kaasinen
2016-01-14 15:32 ` Denis Kenzior
2016-01-14 15:53 ` matti kaasinen
2016-01-14 15:55 ` Denis Kenzior
2016-01-15 10:14 ` matti kaasinen
2016-01-20 14:47 ` matti kaasinen
2016-01-20 15:25 ` =?unknown-8bit?q?Bj=C3=B8rn?= Mork
2016-01-20 17:20 ` matti kaasinen
2016-01-21 8:05 ` matti kaasinen
2016-01-23 20:32 ` CedrIc Jehasse
2016-02-24 14:49 ` matti kaasinen
2016-01-21 12:56 ` matti kaasinen
2016-01-12 19:08 ` =?unknown-8bit?q?Bj=C3=B8rn?= Mork
2016-01-13 16:08 ` Denis Kenzior
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=568A9B71.7080208@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.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