All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Scott Wood <scottwood@freescale.com>,
	galak@kernel.crashing.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2 1/3] 8xx: Analogue & Micro Adder875 board support.
Date: Mon, 17 Dec 2007 09:15:17 -0600	[thread overview]
Message-ID: <47669285.8010707@freescale.com> (raw)
In-Reply-To: <20071217035706.GA3262@localhost.localdomain>

David Gibson wrote:
> On Wed, Dec 12, 2007 at 04:54:27PM -0600, Scott Wood wrote:
>> Signed-off-by: Scott Wood <scottwood@freescale.com>
> [snip]
>> diff --git a/arch/powerpc/boot/dts/adder875-redboot.dts b/arch/powerpc/boot/dts/adder875-redboot.dts
>> new file mode 100644
>> index 0000000..4d28220
>> --- /dev/null
>> +++ b/arch/powerpc/boot/dts/adder875-redboot.dts
> [snip]
>> diff --git a/arch/powerpc/boot/dts/adder875-uboot.dts b/arch/powerpc/boot/dts/adder875-uboot.dts
>> new file mode 100644
>> index 0000000..33d198c
>> --- /dev/null
>> +++ b/arch/powerpc/boot/dts/adder875-uboot.dts
> 
> Having two different device trees for the different firmwares is
> pretty yucky, and could be a pain in the bum for synchronization of
> fixes.

Yes, that's why we need some sort of macro/template facility in dtc. :-)

> Can't you have a common tree, and just poke the places that
> are differently configured by the two firmwares from the bootwrapper.

Enh.  That can get icky as well, and the bootwrapper isn't necessarily 
even used for u-boot, and I'd rather not require it be used just for this.

-Scott

  reply	other threads:[~2007-12-17 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 22:54 [PATCH v2 1/3] 8xx: Analogue & Micro Adder875 board support Scott Wood
2007-12-17  3:57 ` David Gibson
2007-12-17 15:15   ` Scott Wood [this message]
2007-12-18  0:43     ` David Gibson
2007-12-18 16:09       ` Scott Wood

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=47669285.8010707@freescale.com \
    --to=scottwood@freescale.com \
    --cc=galak@kernel.crashing.org \
    --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.