From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: David Vrabel <dvrabel@cantab.net>
Cc: Adrian Bunk <bunk@stusta.de>, Martin Michlmayr <tbm@cyrius.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
John Bowler <jbowler@acm.org>
Subject: Re: [RFC] [PATCH 1/2] Driver to remember ethernet MAC values: maclist
Date: Mon, 20 Feb 2006 13:57:18 +0100 [thread overview]
Message-ID: <20060220135718.038b675b@inspiron> (raw)
In-Reply-To: <43F9B32B.3090203@cantab.net>
On Mon, 20 Feb 2006 12:16:43 +0000
David Vrabel <dvrabel@cantab.net> wrote:
> >>>Some Ethernet hardware implementations have no built-in storage for
> >>>allocated MAC values - an example is the Intel IXP420 chip which has
> >>>support for Ethernet but no defined way of storing allocated MAC values.
> >>>With such hardware different board level implementations store the
> >>>allocated MAC (or MACs) in different ways. Rather than put board level
> >>>code
> For those not familar with the IXP4xx, the Ethernet drivers are
> proprietary and given that there are no other proposed users of this
> maclist code there's no need for it in the kernel at this time.
> >>Why can't this be implemented in user space using the SIOCSIFHWADDR
> >>ioctl?
> I'm with Adrian on this -- it's a job for userspace. The storage of the
> MAC address isn't something that's necessarily board specific anyway but
> could depend on which bootloader is used and/or the bootloader version.
> > Because sometimes you need to have networking available
> > well before userspace.
>
> In the specific case of the IXP4xx, you presumably have some userspace
> available because you've just loaded the NPE firmware from it, yes?
Hi David,
you're certainly right on the ixp4xx, but the are other uses
for this driver which we are working on.. for example,
some Cirrus Logic ARM based chips (ep93xx) have an ethernet device
that could benefit from that.
I'm pretty sure that there are and will be more devices
with such requirements, with either proprietary or
open source drivers. My opinion is that a maclist alike
facility can clean some of the mess in that area.
If we implement such a thing in userspace every distribution
will need to be aware of a specific trick for a specific
board. If we have a clean facility in the kernel, userspace
will not need to care.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Turin, Italy
http://www.towertech.it
next prev parent reply other threads:[~2006-02-20 12:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 1:01 [RFC] [PATCH 1/2] Driver to remember ethernet MAC values: maclist Martin Michlmayr
2006-02-20 1:47 ` Adrian Bunk
2006-02-20 2:01 ` Alessandro Zummo
2006-02-20 2:39 ` Adrian Bunk
2006-02-20 16:23 ` John Bowler
2006-02-20 12:16 ` David Vrabel
2006-02-20 12:57 ` Alessandro Zummo [this message]
2006-02-20 13:02 ` Russell King
2006-02-20 13:22 ` Alessandro Zummo
2006-02-20 17:04 ` John Bowler
2006-02-20 13:07 ` Lennert Buytenhek
2006-02-20 13:15 ` jamal
2006-02-20 13:28 ` Alessandro Zummo
2006-03-03 16:17 ` Atsushi Nemoto
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=20060220135718.038b675b@inspiron \
--to=alessandro.zummo@towertech.it \
--cc=bunk@stusta.de \
--cc=dvrabel@cantab.net \
--cc=jbowler@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tbm@cyrius.com \
/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).