[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090527.132328.78091350.davem@davemloft.net>
Date: Wed, 27 May 2009 13:23:28 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: rmk+lkml@....linux.org.uk
Cc: scottwood@...escale.com, 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,
timur@...escale.com
Subject: Re: [RFC] [PATCH] Device Tree on ARM platform
From: Russell King <rmk+lkml@....linux.org.uk>
Date: Wed, 27 May 2009 20:29:10 +0100
> To program them into the hardware registers, which is not what we in
> the ARM community say, but it's what the _network_ guys tell people
> they should be doing.
>
> I've suggested in the past having a standard kernel parameter such
> that you can specify a mac address on a per-device basis in a totally
> platform independent way, but the network folk don't like that idea.
As a "network guy" I can tell you that when the system firmware
provides a system-wide or device specific MAC address in it's device
tree, that is what you should use.
And that's what I've been doing on sparc FOR 15 YEARS.
Device trees are the only systematic generic mechanism for
describing device layouts on the myriad of embedded boards
out there which you will ever find.
Two platforms, and now a third, have been using this scheme
over a very proven period of time. It's not a hack, there is
infrastructure to get the boot loaders to do the right thing,
and only ARM seems to resist it. :-)
--
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