RFC: Location for Device Tree Sources?

Li Yang-r58472 LeoLi at freescale.com
Wed Aug 2 13:35:07 EST 2006

> -----Original Message-----
> From: linuxppc-dev-bounces+leoli=freescale.com at ozlabs.org
> [mailto:linuxppc-dev-bounces+leoli=freescale.com at ozlabs.org] On Behalf
Of Mark A.
> Greer
> Sent: Wednesday, August 02, 2006 8:35 AM
> To: McClintock Matthew-R56630
> Cc: linuxppc-dev at ozlabs.org; Guennadi Liakhovetski
> Subject: Re: RFC: Location for Device Tree Sources?
> On Tue, Aug 01, 2006 at 04:01:33PM -0500, Matthew McClintock wrote:
> > On Tue, 2006-08-01 at 23:00 +0200, Guennadi Liakhovetski wrote:
> > >
> > > 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
> > were not included at all and he left this point open for discussion.
> That's correct.
> 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.
> We already have dtc kept externally to the kernel source.  Why not
> keep a single site where all things necessary to powerpc linux are
> 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.

> 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?

More information about the Linuxppc-dev mailing list