linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <dwg@au1.ibm.com>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: linuxppc-dev@ozlabs.org, Jon Loeliger <jdl@jdl.com>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: DTC 1.0.0 Release Coming?
Date: Sun, 12 Aug 2007 19:26:27 +1000	[thread overview]
Message-ID: <20070812092627.GB6803@localhost.localdomain> (raw)
In-Reply-To: <46BD1272.9060107@am.sony.com>

On Fri, Aug 10, 2007 at 06:35:46PM -0700, Geoff Levand wrote:
> Paul Mackerras wrote:
> > David Gibson writes:
> > 
> >> We decided that since a formal dtc release was imminent, it would be
> >> simpler to make dtc a new kernel build requirement, rather than
> >> integrate the substantial blob of dtc code into the kernel tree and
> >> then have to deal with the maintenance / synchronization issues
> >> between the in-kernel and upstream versions.
> > 
> > Um, what I thought we decided was to ship a pre-built .dtb for ps3
> > (once its dts settles down), and make dtc a kernel build requirement
> > only for embedded platforms.
> 
> We could also ship a generated .S file (dtc -O asm -o ps3-dt.S ps3.dts),
> which would be easier to maintain in the source tree than a binary file,
> then use something like this in the wrapper script:
>   
>   ${CROSS}gcc -c -o ${platform}-dt.o ${platform}-dt.S
>   ${CROSS}objcopy -O binary ${platform}-dt.o ${platform}.dtb
> 
> Untested, but it seems like it would work.

Yes, I'm aware of that option and am considering it.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-08-13  1:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 16:12 DTC 1.0.0 Release Coming? Jon Loeliger
2007-07-26  3:05 ` David Gibson
2007-07-26  7:25   ` David Gibson
2007-07-26 13:04   ` Jon Loeliger
2007-07-26 14:27     ` David Gibson
2007-07-26 15:21       ` Jon Loeliger
2007-07-27  1:33         ` David Gibson
2007-07-27  2:00           ` David Gibson
2007-07-31 21:11             ` Segher Boessenkool
2007-08-01  1:19               ` David Gibson
2007-08-06 19:33                 ` Segher Boessenkool
2007-08-06 13:48           ` Josh Boyer
2007-08-10  1:30             ` David Gibson
2007-08-10  1:37               ` Josh Boyer
2007-08-10  2:59                 ` David Gibson
2007-08-10 20:59                   ` Segher Boessenkool
2007-08-10 22:24                     ` Geoff Levand
2007-08-10 23:39                       ` Segher Boessenkool
2007-08-11  0:52                   ` Paul Mackerras
2007-08-11  1:35                     ` Geoff Levand
2007-08-12  9:26                       ` David Gibson [this message]
2007-08-13  1:39                         ` Stephen Rothwell
2007-08-12  9:25                     ` David Gibson
2007-08-10  2:13               ` Geoff Levand
2007-07-31 21:09 ` Segher Boessenkool
2007-08-01 23:35 ` Arnd Bergmann
2007-08-02  0:14   ` David Gibson

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=20070812092627.GB6803@localhost.localdomain \
    --to=dwg@au1.ibm.com \
    --cc=geoffrey.levand@am.sony.com \
    --cc=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).