From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: tbm@cyrius.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, jbowler@acm.org
Subject: Re: [RFC] [PATCH 1/2] Driver to remember ethernet MAC values: maclist
Date: Sat, 04 Mar 2006 01:17:47 +0900 (JST) [thread overview]
Message-ID: <20060304.011747.07644094.anemo@mba.ocn.ne.jp> (raw)
In-Reply-To: <20060220010113.GA19309@deprecation.cyrius.com>
>>>>> On Mon, 20 Feb 2006 01:01:13 +0000, Martin Michlmayr <tbm@cyrius.com> said:
tbm> Some Ethernet hardware implementations have no built-in storage
tbm> for allocated MAC values - an example is the Intel IXP420 chip
tbm> which has support for Ethernet but no defined way of storing
tbm> allocated MAC values. With such hardware different board level
tbm> implementations store the allocated MAC (or MACs) in different
tbm> ways. Rather than put board level code into a specific Ethernet
tbm> driver this driver provides a generally accessible repository for
tbm> the MACs which can be written by board level code and read by the
tbm> driver.
Slow response:
It can be done with register_netdevice_notifier(). You can catch
NETDEV_REGISTER event, check the device is what you expected by
looking dev->irq or something, and initialize dev->dev_addr. Whole
these can be implemented in your board level code.
---
Atsushi Nemoto
prev parent reply other threads:[~2006-03-03 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 1:01 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
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 [this message]
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=20060304.011747.07644094.anemo@mba.ocn.ne.jp \
--to=anemo@mba.ocn.ne.jp \
--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
all inboxes | Powered by JetHome®