From: Jon Loeliger <jdl@jdl.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: RFC: Location for Device Tree Sources?
Date: Wed, 09 Aug 2006 11:48:34 -0500 [thread overview]
Message-ID: <E1GArEQ-0006OP-7H@jdl.com> (raw)
In-Reply-To: Your message of "Wed, 09 Aug 2006 09:38:39 PDT." <20060809163839.GB17759@mag.az.mvista.com>
So, like, the other day "Mark A. Greer" mumbled:
> > We're only talking about the _source_ files. The .dts files. Not the
> > binary trees themselves.
> >
> > The basic summary is that having a .dts in the kernel for every
> > defconfig would be good. (I think that was the summary anyway.)
>
> That's my understanding too. A 1-1 matching of default config files
> and dts files kept in the kernel src trees.
And the keen observer who watches Paul's tree will have
noticed that the first DTS file, mpc8641_hpcn.dts, has already
been added to arch/powerpc/boot/dts!
> Any extra dts files
... of which there are none...
> ...would be kept whereever dtc src is stored (i.e., jdl.com).
> I haven't heard jdl agree to this, though. :)
Sure. No problem by me.
Though I do have a question WRT the notion of the libdt...
So, if I understand this proposal correctly, making libdt.a
would mean that we will now have to link the kernel against
this new, external dependency library. It would also mean
that we'd have to link U-Boot against this new, external
library as well.
Did I misunderstand or is everyone hip, jiggie and down with that?
jdl
next prev parent reply other threads:[~2006-08-09 16:48 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
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 [this message]
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=E1GArEQ-0006OP-7H@jdl.com \
--to=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.