From: Kumar Gala <galak@kernel•crashing.org>
To: Josh Boyer <jwboyer@jdub•homelinux.org>
Cc: "linuxppc-dev@ozlabs•org" <linuxppc-dev@ozlabs•org>,
Guennadi Liakhovetski <g.liakhovetski@gmx•de>
Subject: Re: RFC: Location for Device Tree Sources?
Date: Wed, 2 Aug 2006 14:26:13 -0500 [thread overview]
Message-ID: <636D3933-399D-45AB-9DAF-74AB77ABA5FF@kernel.crashing.org> (raw)
In-Reply-To: <1154545382.12757.1.camel@weaponx.rchland.ibm.com>
On Aug 2, 2006, at 2:03 PM, Josh Boyer wrote:
> On Wed, 2006-08-02 at 11:49 -0700, Mark A. Greer wrote:
>> On Wed, Aug 02, 2006 at 12:21:37PM -0600, Grant Likely wrote:
>>> On 8/2/06, Mark A. Greer <mgreer@mvista•com> wrote:
>>>> On Tue, Aug 01, 2006 at 09:20:52PM -0600, Grant Likely wrote:
>>>>> I have to second that opinion. The device tree is absolutely
>>>>> integral
>>>>> with the rest of the code/drivers needed to support a board. I
>>>>> say
>>>>> there are stronger arguments for keeping the dts files in the
>>>>> kernel
>>>>> source than there are for the boot wrapper.
>>>>
>>>> Well, the dts is no good to you without dtc so do we put dtc in the
>>>> kernel source tree too?
>>>
>>> I don't know; should we include gcc also?
>>>
>>> :p
>>
>> Yep, my point.
>>
>> I don't really have a problem with keeping known working dts files in
>> arch/powerpc/boot/dts. Perhaps a 1-1 match with files in
>> arch/powerpc/configs?
>
> I like that idea very much. Actually that's what I thought were were
> talking about in the first place.
>
>>
>> It would still be nice to have the dtc source, attach tool source,
>> and,
>> if useful, a more exhaustive collection of dts files in one place.
>
> I also think that would be useful.
While useful, I doubt its likely to happen. I forsee boards that
aren't in the kernel tree having their dts live in their private
worlds. Also tools like mkimage that come from u-boot will probably
still live with u-boot.
- kumar
next prev parent reply other threads:[~2006-08-02 19:26 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 20:32 RFC: Location for Device Tree Sources? Jon Loeliger
2006-08-01 21:00 ` Guennadi Liakhovetski
2006-08-01 21:01 ` Matthew McClintock
2006-08-02 0:35 ` Mark A. Greer
2006-08-02 0:42 ` Mark A. Greer
2006-08-02 1:12 ` Josh Boyer
2006-08-02 3:20 ` Grant Likely
2006-08-02 13:35 ` Kumar Gala
2006-08-02 16:38 ` Tom Rini
2006-08-02 18:09 ` Matthew McClintock
2006-08-02 18:16 ` Vitaly Bordug
2006-08-02 18:21 ` Tom Rini
2006-08-02 18:23 ` Jon Loeliger
2006-08-02 18:57 ` Tom Rini
2006-08-02 20:06 ` Kumar Gala
2006-08-03 14:49 ` Li Yang
2006-08-03 15:47 ` Li Yang
2006-08-02 18:24 ` Mark A. Greer
2006-08-02 18:23 ` Mark A. Greer
2006-08-02 18:21 ` Grant Likely
2006-08-02 18:49 ` Mark A. Greer
2006-08-02 19:03 ` Josh Boyer
2006-08-02 19:26 ` Kumar Gala [this message]
2006-08-02 18:22 ` Mark A. Greer
2006-08-02 18:22 ` Matthew McClintock
2006-08-02 18:42 ` Mark A. Greer
2006-08-02 18:25 ` Jon Loeliger
2006-08-02 18:34 ` Mark A. Greer
2006-08-02 18:41 ` Brent Cook
2006-08-02 18:51 ` Mark A. Greer
2006-08-03 0:35 ` Tom Rini
2006-08-02 3:35 ` Li Yang-r58472
2006-08-04 4:51 ` Paul Mackerras
2006-08-09 11:18 ` Benjamin Herrenschmidt
2006-08-09 12:56 ` Josh Boyer
2006-08-09 16:38 ` Mark A. Greer
2006-08-09 16:48 ` Jon Loeliger
2006-08-09 17:03 ` Mark A. Greer
2006-08-09 14:03 ` Wolfgang Denk
2006-08-09 16:05 ` Benjamin Herrenschmidt
2006-08-09 18:47 ` Andy Fleming
2006-08-09 19:17 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 9:32 Milton Miller
2006-08-03 13:54 ` Tom Rini
2006-08-03 16:30 ` Milton Miller
2006-08-04 4:49 ` Paul Mackerras
2006-08-04 17:54 ` Tom Rini
2006-08-04 23:29 ` Paul Mackerras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=636D3933-399D-45AB-9DAF-74AB77ABA5FF@kernel.crashing.org \
--to=galak@kernel$(echo .)crashing.org \
--cc=g.liakhovetski@gmx$(echo .)de \
--cc=jwboyer@jdub$(echo .)homelinux.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox