netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andrew Bird (Sphere Systems)" <ajb@spheresystems.co.uk>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: oliver@neukum.name, gregkh@linuxfoundation.org,
	linux-usb@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB CDC-Ether - Add ZTE WWAN matches before generic Ethernet
Date: Sat, 19 May 2012 18:42:38 +0100	[thread overview]
Message-ID: <201205191842.38567.ajb@spheresystems.co.uk> (raw)
In-Reply-To: <87aa14jcyi.fsf@nemi.mork.no>

On Saturday 19 May 2012, Bjørn Mork wrote:
> Andrew Bird <ajb@spheresystems.co.uk> writes:
> > Some ZTE WWAN devices have generic CDC Ether descriptors. Add those
> > into the whitelist so that we get FLAG_WWAN on the interface
> 
> Are you sure none of these export QMI via the CDC Ether control
> interface?  Or are they not Qualcomm devices at all?
> 
> As usual, if you see a spurious "CDC: unexpected notification 01" logged
> from cdc_ether, then there is reason to examine those closer.  If you
> don't see any such messages, then there isn't any QMI there.
> 
> 
> Bjørn

Hi Bjørn,
	No these are devices that use the Icera chipset. They have cdc-acm serial 
ports and firmware has implemented AT commands for (de)activating the pseudo 
Ethernet and getting IP + DNS values etc. Actually applying this patch will 
provide little in terms of operation except to make the interface name wwan%d 
unstead of usb%d and to flag the interface such that Network Manager does not 
try to bring it up via DHCP as soon as it appears, like it would with a fixed 
Ethernet interface.

Good tip about the 'unexpected notification 01' I'll look out for that!

Andrew

  reply	other threads:[~2012-05-19 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-19 13:56 [PATCH] USB CDC-Ether - Add ZTE WWAN matches before generic Ethernet Andrew Bird
2012-05-19 17:30 ` Bjørn Mork
2012-05-19 17:42   ` Andrew Bird (Sphere Systems) [this message]
2012-05-19 22:48 ` David Miller

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=201205191842.38567.ajb@spheresystems.co.uk \
    --to=ajb@spheresystems.co.uk \
    --cc=bjorn@mork.no \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oliver@neukum.name \
    /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;
as well as URLs for NNTP newsgroup(s).