linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Matthew McClintock <msm@freescale.com>
Cc: Tom Rini <trini@kernel.crashing.org>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: RFC: Location for Device Tree Sources?
Date: Wed, 2 Aug 2006 22:16:54 +0400	[thread overview]
Message-ID: <20060802221654.5c54a9a2@localhost.localdomain> (raw)
In-Reply-To: <1154542161.5550.25.camel@localhost>

On Wed, 02 Aug 2006 13:09:21 -0500
Matthew McClintock wrote:

> On Wed, 2006-08-02 at 09:38 -0700, Tom Rini wrote:
> > I'll throw in the caveat that I'm not 100% sure we're that stable
> > yet, but it certainly seems like it, at least for the overall
> > portion where you might really have incompatible trees.  More or
> > less complete (now every device is described!) dts should be
> > interchangable to the kernel for the custom board X is just a
> > little different from ref board Y issues (and now, in theory, the
> > Just Like A Sandpoint board, with a correct dts will boot the
> > 'sandpoint' kernel). 
> 
> The sandpoint (as far as I know) does not have a stable DTS. So in
> this case including the DTS in the kernel would reduce confusion. The
> same could be said for other boards where the DTS needed to be
> changed for the IRQ rework. The old DTS will no longer boot the new
> kernels. I'm not sure how much longer we will run into this problem
> though.
> 
I am right about to submit dts+code working fine w/ recent IRQ stuff for 8540 and 8560,
and will make sure dts coming along.

But, I guess we finally should end up with a place in kernel tree where such a stuff should reside
further.

  reply	other threads:[~2006-08-02 18:17 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 [this message]
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
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=20060802221654.5c54a9a2@localhost.localdomain \
    --to=vbordug@ru.mvista.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=msm@freescale.com \
    --cc=trini@kernel.crashing.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).