Thread (36 messages) flat view 36 messages, 13 authors, 2006-08-09

RE: RFC: Location for Device Tree Sources?

From: Li Yang-r58472 <hidden>
Date: 2006-08-02 03:34:46

-----Original Message-----
From: linuxppc-dev-bounces+leoli=3Dfreescale.com@ozlabs.org
[mailto:linuxppc-dev-bounces+leoli=3Dfreescale.com@ozlabs.org] On =
Behalf
Of Mark A.
Greer
Sent: Wednesday, August 02, 2006 8:35 AM
To: McClintock Matthew-R56630
Cc: linuxppc-dev@ozlabs.org; Guennadi Liakhovetski
Subject: Re: RFC: Location for Device Tree Sources?
=20
On Tue, Aug 01, 2006 at 04:01:33PM -0500, Matthew McClintock wrote:
quoted
On Tue, 2006-08-01 at 23:00 +0200, Guennadi Liakhovetski wrote:
quoted
Mark A. Greer in his patch to port sandpoint to arch/powerpc put
sandpoint.dts under arch/powerpc/boot/dts/sandpoint.dts
I believe in his latest patches he removed this part. The device
trees
quoted
were not included at all and he left this point open for discussion.
=20
That's correct.
=20
TBH, I think its wrong to keep them in the kernel source at all--yes,
the same argument could be made for arch/powerpc/boot but that's been
settled.
=20
We already have dtc kept externally to the kernel source.  Why not
keep a single site where all things necessary to powerpc linux are
kept?
It could house dtc, the dt attach tool, and all the dt source files.
We already have gcc out of the kernel source, but we need to have all
the source code in.  :)  I strongly agree to keep dts in tree, or it
will be hard to find out what the driver really does.
=20
I doesn't matter to me where as long as its highly available and has
reasonable bandwidth.  jdl.com?  source.mvista.com?  penguinppc.org?
other?
=20
-Leo
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help