From: Oliver Neukum <oneukum@suse.de>
To: Alexey ORISHKO <alexey.orishko@stericsson.com>
Cc: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
Dan Williams <dcbw@redhat.com>,
Stefan Metzmacher <metze@samba.org>,
Oliver Neukum <oliver@neukum.name>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] TODO FLAG_POINTTOPOINT => FLAG_WWAN? usbnet/cdc_ncm: mark ncm devices as "mobile broadband devices" with FLAG_WWAN
Date: Fri, 3 Jun 2011 12:50:27 +0200 [thread overview]
Message-ID: <201106031250.28041.oneukum@suse.de> (raw)
In-Reply-To: <2AC7D4AD8BA1C640B4C60C61C8E520153E3C13B620@EXDCVYMBSTM006.EQ1STM.local>
Am Freitag, 3. Juni 2011, 12:23:21 schrieb Alexey ORISHKO:
> There is no difference between cdc_ncm and cdc_ether devices, besides
> the fact cdc_ncm is more efficient in data transfer and cpu load.
> The problem is that you cannot say much about device functionality based
> just on interface name. As example existing devices with cdc_ether
> interface could be mobile phone which provides connectivity to 3G network,
> or could be a phone in the mode "over PC", where phone applications
> access internet via broadband connection on PC (to save money).
>
> Network manager cannot simply make decision which devices can be used
> for mobile broadband access based on interface name. It needs an additional
> info, which does not exist in device descriptor.
Well, but cdc-ether usually means that you can start up dhcp and use the
interface as a network card. Can the same be done with cdc-ncm or do you always
need to establish a connection through a secondary interface?
Regards
Oliver
--
- - -
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
- - -
next prev parent reply other threads:[~2011-06-03 10:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 10:08 cdc_ncm: Ericsson F5521gw appears as usbX, while Ericsson F3507g as wwanX Stefan Metzmacher
2011-06-01 10:08 ` [PATCH] TODO FLAG_POINTTOPOINT => FLAG_WWAN? usbnet/cdc_ncm: mark ncm devices as "mobile broadband devices" with FLAG_WWAN Stefan Metzmacher
2011-06-01 10:20 ` Alexey ORISHKO
2011-06-01 10:47 ` Stefan (metze) Metzmacher
2011-06-01 11:39 ` Alexey ORISHKO
2011-06-01 11:54 ` Stefan (metze) Metzmacher
2011-06-01 12:27 ` Alexey ORISHKO
2011-06-03 9:35 ` Stefan (metze) Metzmacher
2011-06-02 22:29 ` Dan Williams
2011-06-02 22:35 ` Dan Williams
2011-06-03 0:58 ` Valdis.Kletnieks
[not found] ` <5203.1307062683-+bZmOdGhbsPr6rcHtW+onFJE71vCis6O@public.gmane.org>
2011-06-03 9:45 ` Alexey ORISHKO
2011-06-03 10:01 ` Oliver Neukum
2011-06-03 10:23 ` Alexey ORISHKO
2011-06-03 10:50 ` Oliver Neukum [this message]
[not found] ` <201106031250.28041.oneukum-l3A5Bk7waGM@public.gmane.org>
2011-06-03 11:47 ` Alexey ORISHKO
2011-06-03 12:31 ` Bjørn Mork
2011-06-03 19:24 ` Dan Williams
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=201106031250.28041.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=alexey.orishko@stericsson.com \
--cc=dcbw@redhat.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=metze@samba.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).