[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A1DA24D.5000101@freescale.com>
Date: Wed, 27 May 2009 15:27:57 -0500
From: Timur Tabi <timur@...escale.com>
To: David Miller <davem@...emloft.net>
CC: scottwood@...escale.com, rmk+lkml@....linux.org.uk,
jacmet@...site.dk, r.schwebel@...gutronix.de,
devicetree-discuss@...abs.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.arm.linux.org.uk, yuan-bo.ye@...orola.com
Subject: Re: [RFC] [PATCH] Device Tree on ARM platform
David Miller wrote:
> It depends. Some devices have EEPROM's that store the permanently
> assigned MAC address, some have NVRAM for this, and yet other's put it
> into the PCI ROM.
Well, I specifically said "isn't already programmed in the hardware". I wasn't talking about just the NIC.
> Some platforms that have real OF device trees often do not put the
> permanent MAC address into the EEPROM or NVRAM even if it is
> customary to do so on a particular device. The MAC has to be
> obtained from the OF device tree.
Sorry, you're not answering my question. I asked what do drivers do when the MAC address is not in the OF tree, and it is not programmed in hardware (any hardware).
--
Timur Tabi
Linux kernel developer at Freescale
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists