linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: RFC: Location for Device Tree Sources?
Date: Wed, 09 Aug 2006 13:18:29 +0200	[thread overview]
Message-ID: <1155122309.4040.94.camel@localhost.localdomain> (raw)
In-Reply-To: <1154464346.19994.4.camel@cashmere.sps.mot.com>

On Tue, 2006-08-01 at 15:32 -0500, Jon Loeliger wrote:
> Folks,
> 
> Where should we place the sources for the OF Flat Device
> Tree source files?  They used to be in U-Boot, but that
> isn't happening any more.

Why ? While having device-tree's in zImages is good to handle firmwares
that can't pass them, I still think that the proper thing to do is to
have the firmware provide the DT to the kernel. Did Denk decide once for
all against having DTs passed by uboot at all ? In which case, it's
probably time to consider a fork...

> One semi-obvious place would be to co-locate them with
> their corresponding Linux arch/powerpc/platform directory.
> Another would be to have a new directory full of them
> under, say, arch/powerpc/devtrees or so.
> 
> Are there other suggestions or better ideas?
> 
> Thanks,
> jdl
> 
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev

  parent reply	other threads:[~2006-08-09 12:34 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 [this message]
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=1155122309.4040.94.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=jdl@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).