Date: Sat, 04 Mar 2006 01:17:47 +0900 (JST)
Message-Id: <20060304.011747.07644094.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
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
In-Reply-To: <20060220010113.GA19309@deprecation.cyrius.com>
References: <20060220010113.GA19309@deprecation.cyrius.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1178
Lines: 26

>>>>> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/