From: "Bjørn Mork" <bjorn@mork.no>
To: David Miller <davem@davemloft.net>
Cc: dcbw@redhat.com, cpuwolf@gmail.com, gregkh@linuxfoundation.org,
alexey.orishko@stericsson.com, linux-usb@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] CDC_NCM adding support IFF_NOARP for infineon modem platform
Date: Tue, 15 Jan 2013 09:34:07 +0100 [thread overview]
Message-ID: <87hamikfpc.fsf@nemi.mork.no> (raw)
In-Reply-To: <20130114.133412.479351928049237212.davem@davemloft.net> (David Miller's message of "Mon, 14 Jan 2013 13:34:12 -0500 (EST)")
David Miller <davem@davemloft.net> writes:
> From: Dan Williams <dcbw@redhat.com>
>
>> IFF_NOARP is already done for other WWAN devices (sierra_net, hso,
>> cdc-ether, cdc-phonet, lg-vl600, etc) so there is some precedent. Some
>> drivers (phonet, hso) set *both* POINTTOPOINT and NOARP. Is that
>> redundant, and should all WWAN drivers be moved to only POINTTOPOINT?
>>
>> (aside: usbnet has FLAG_POINTTOPOINT, but that's nothing to do with
>> IFF_POINTTOPOINT, it only controls whether the interface is named usbX
>> or ethX. Confusing.)
>
> I can't answer any of your questions unless you tell me what the
> real limitation of these devices is.
>
> For the second time, is the problem that these devices cannot
> support broadcast packets properly?
The main problem is that these devices don't support ethernet. They
support IP (v4 and _maybe_ v6) with an ethernet header. Many of them
will do ARP (and IPv6 ND) as well to complete the picture, but some of
them don't and that's what these drivers try to deal with.
Note that most of the devices will run a DHCP server, so there is some
sort of IP broadcast support. Whether that qualifies as proper ethernet
broadcast support is another question...
These devices are attempting to bridge an IP-only point-to-point
interface and an ethernet over USB interface, with the intention to make
the point-to-point interface look like ethernet to applications and
users. This is of course always going to be imperfect. But I believe
that we should aim to help the firmware achive this goal when writing
drivers instead of working against it. Setting IFF_NOARP and not
IFF_POINTTOPOINT is one way to do that.
Bjørn
next prev parent reply other threads:[~2013-01-15 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 11:34 [PATCH] CDC_NCM adding support IFF_NOARP for infineon modem platform Wei Shuai
2013-01-12 23:35 ` David Miller
2013-01-14 17:19 ` Dan Williams
2013-01-14 18:34 ` David Miller
2013-01-15 0:41 ` Peter Stuge
2013-01-15 8:34 ` Bjørn Mork [this message]
[not found] ` <87hamikfpc.fsf-lbf33ChDnrE/G1V5fR+Y7Q@public.gmane.org>
2013-01-16 21:18 ` David Miller
2013-01-15 13:11 ` Wei Shuai
[not found] ` <1357990479-5836-1-git-send-email-cpuwolf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-16 21:45 ` Dan Williams
2013-01-17 6:44 ` Wei Shuai
2013-01-18 17:43 ` 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=87hamikfpc.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=alexey.orishko@stericsson.com \
--cc=cpuwolf@gmail.com \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).