public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
* Re: [RFC] [PATCH] Device Tree on ARM platform
       [not found]       ` <20090527.132328.78091350.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
@ 2009-05-27 20:27         ` Jean-Christophe PLAGNIOL-VILLARD
       [not found]           ` <20090527202701.GA16219-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
  0 siblings, 1 reply; 3+ messages in thread
From: Jean-Christophe PLAGNIOL-VILLARD @ 2009-05-27 20:27 UTC (permalink / raw)
  To: David Miller
  Cc: rmk+lkml-lFZ/pmaqli7XmaaqVzeoHQ,
	devicetree-discuss-mnsaURCQ41sdnm+yROfE0A,
	linux-sh-u79uwXL29TY76Z2rM5mHXA,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA,
	linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW,
	scottwood-KZfg59tc24xl57MIdRCFDg,
	yuan-bo.ye-3WKxDLwmzFNWk0Htik3J/w, timur-KZfg59tc24xl57MIdRCFDg

On 13:23 Wed 27 May     , David Miller wrote:
> From: Russell King <rmk+lkml@arm.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. :-)
The SH, avr32, mips, x86 does not support it too IIRC

Best Regards,
J.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RFC] [PATCH] Device Tree on ARM platform
       [not found]           ` <20090527202701.GA16219-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
@ 2009-05-27 20:48             ` Josh Boyer
  2009-05-27 20:56             ` David Miller
  1 sibling, 0 replies; 3+ messages in thread
From: Josh Boyer @ 2009-05-27 20:48 UTC (permalink / raw)
  To: Jean-Christophe PLAGNIOL-VILLARD
  Cc: rmk+lkml-lFZ/pmaqli7XmaaqVzeoHQ,
	devicetree-discuss-mnsaURCQ41sdnm+yROfE0A,
	linux-sh-u79uwXL29TY76Z2rM5mHXA, timur-KZfg59tc24xl57MIdRCFDg,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA,
	linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW,
	scottwood-KZfg59tc24xl57MIdRCFDg,
	yuan-bo.ye-3WKxDLwmzFNWk0Htik3J/w, David Miller

On Wed, May 27, 2009 at 10:27:01PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
>On 13:23 Wed 27 May     , David Miller wrote:
>> From: Russell King <rmk+lkml@arm.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. :-)
>The SH, avr32, mips, x86 does not support it too IIRC

x86 has a variant.  The OLPC uses OF.

josh

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RFC] [PATCH] Device Tree on ARM platform
       [not found]           ` <20090527202701.GA16219-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
  2009-05-27 20:48             ` Josh Boyer
@ 2009-05-27 20:56             ` David Miller
  1 sibling, 0 replies; 3+ messages in thread
From: David Miller @ 2009-05-27 20:56 UTC (permalink / raw)
  To: plagnioj-sclMFOaUSTBWk0Htik3J/w
  Cc: rmk+lkml-lFZ/pmaqli7XmaaqVzeoHQ,
	devicetree-discuss-mnsaURCQ41sdnm+yROfE0A,
	linux-sh-u79uwXL29TY76Z2rM5mHXA,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA,
	linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW,
	scottwood-KZfg59tc24xl57MIdRCFDg,
	yuan-bo.ye-3WKxDLwmzFNWk0Htik3J/w, timur-KZfg59tc24xl57MIdRCFDg

From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Date: Wed, 27 May 2009 22:27:01 +0200

> The SH, avr32, mips, x86 does not support it too IIRC

Actually x86 does support OF, via real OF firmware in fact :-)


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-05-27 20:56 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20090527175609.GB31861@flint.arm.linux.org.uk>
     [not found] ` <4A1D8FBA.6040802@freescale.com>
     [not found]   ` <20090527192909.GA32398@flint.arm.linux.org.uk>
     [not found]     ` <20090527.132328.78091350.davem@davemloft.net>
     [not found]       ` <20090527.132328.78091350.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-05-27 20:27         ` [RFC] [PATCH] Device Tree on ARM platform Jean-Christophe PLAGNIOL-VILLARD
     [not found]           ` <20090527202701.GA16219-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2009-05-27 20:48             ` Josh Boyer
2009-05-27 20:56             ` David Miller

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox