From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Huawei 3131 with idVendor=12d1, idProduct=14fe
Date: Wed, 13 Jan 2016 10:08:13 -0600 [thread overview]
Message-ID: <5696766D.9060307@gmail.com> (raw)
In-Reply-To: <87fuy2vco9.fsf@nemi.mork.no>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
Hi Bjorn,
On 01/12/2016 01:08 PM, Bjørn Mork wrote:
> matti kaasinen <matti.kaasinen@gmail.com> writes:
>> 2016-01-12 18:30 GMT+02:00 Denis Kenzior <denkenz@gmail.com>:
>>
>>> Please note, that there are two different versions of the Huawei cards
>>> supported by oFono. One uses the "gobi" driver (these are Qualcomm
>>> chips). While the more traditional one uses PPP & the "huawei" driver.
>>
>>
>> I suppose I should edit setup_gobi() and vendor_list() as before in case
>> it's "gobi"?
>
> It's not "gobi". At least not in the firmware cfg you are using. The
> 255/2/22 class/subclass/protocol indicates an NCM function with an AT
> command channel transported via SEND_ENCAPSULATED_COMMAND and
> GET_ENCAPSULATED_RESPONSE. The huawei_cdc_ncm driver will handle this,
> exporting the AT command channel as a /dev/cdc-wdmX device.
I suspected as much. Thanks for confirming that.
>
> The NCM network interface is managed via Huawei AT commands like e.g
> AT^NDISDUP, either over the /dev/cdc-wdmX device or one of the serial
> functions. Don't know if ofono supports that? If not, then I guess PPP
> is your option.
Looks like Marcel added support for this back in 2010:
bfd2c768cd97e92347325363b92292cd6bb27e9f. But it looks like the
'huawei' driver was never updated to make use of it.
Regards,
-Denis
next prev parent reply other threads:[~2016-01-13 16:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADnUhn1efXRB7fZGkSfsToHH5gxd-tK4OxJxF9MhP334P1Pvcw@mail.gmail.com>
2016-01-11 15:02 ` Huawei 3131 with idVendor=12d1, idProduct=14fe 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 [this message]
2015-12-30 10:31 matti kaasinen
2015-12-31 8:39 ` matti kaasinen
2016-01-04 16:18 ` 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=5696766D.9060307@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