From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: Adrian Bunk <bunk@stusta.de>
Cc: 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 03:01:46 +0100 [thread overview]
Message-ID: <20060220030146.11f418dc@inspiron> (raw)
In-Reply-To: <20060220014735.GD4971@stusta.de>
On Mon, 20 Feb 2006 02:47:35 +0100
Adrian Bunk <bunk@stusta.de> 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
> > c
> Silly question:
>
> Why can't this be implemented in user space using the SIOCSIFHWADDR
> ioctl?
Because sometimes you need to have networking available
well before userspace.
(netconsole, root over nfs, ...)
--
Best regards,
Alessandro Zummo,
Tower Technologies - Turin, Italy
http://www.towertech.it
next prev parent reply other threads:[~2006-02-20 2:01 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 [this message]
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
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=20060220030146.11f418dc@inspiron \
--to=alessandro.zummo@towertech.it \
--cc=bunk@stusta.de \
--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).