[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090527.143516.-1836205167.imp@bsdimp.com>
Date: Wed, 27 May 2009 14:35:16 -0600 (MDT)
From: "M. Warner Losh" <imp@...imp.com>
To: davem@...emloft.net
Cc: timur@...escale.com, rmk+lkml@....linux.org.uk,
devicetree-discuss@...abs.org, linux-kernel@...r.kernel.org,
scottwood@...escale.com, yuan-bo.ye@...orola.com,
linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: [RFC] [PATCH] Device Tree on ARM platform
In message: <20090527.132553.40558501.davem@...emloft.net>
David Miller <davem@...emloft.net> writes:
: From: Timur Tabi <timur@...escale.com>
: Date: Wed, 27 May 2009 14:54:14 -0500
:
: > How does a Linux driver normally get a MAC address if it's not
: > passed via the device tree and it isn't already programmed in the
: > hardware? Is there some file in /etc that stores these things?
:
: 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.
Some also put it into their CIS for things like PC Card, CardBus and
SDIO too. It is the definition of device specific :).
: 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.
This is but one of many ways to get it...
Warner
--
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