From: David Gibson <dwg@au1.ibm.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Paul Mackerras <paulus@samba.org>,
ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Someone broke my allmodconfig build
Date: Mon, 23 Jul 2007 11:43:37 +1000 [thread overview]
Message-ID: <20070723014337.GC3272@localhost.localdomain> (raw)
In-Reply-To: <20070722020412.GQ3925@crusty.rchland.ibm.com>
On Sat, Jul 21, 2007 at 09:04:13PM -0500, Josh Boyer wrote:
> On Sun, Jul 22, 2007 at 10:37:06AM +1000, Paul Mackerras wrote:
> > Stephen Rothwell writes:
> >
> > > WRAP arch/powerpc/boot/zImage.ps3
> > > /home/sfr/kernels/linus/arch/powerpc/boot/wrapper: line 113: dtc: command not found
> > > make[2]: *** [arch/powerpc/boot/zImage.ps3] Error 1
> >
> > Hmmm, we should be shipping .dtb files with the tree, so people don't
> > have to have dtc installed.
>
> Really? I don't think we're quite ready for that. Particularly for the
> embedded boards. Those DTS files still get lots of churn, and having to
> update both the .dts and .dtb at the same time seems a bit fragile.
I sort of prefer this option in theory, but it's basically
impossible. People updating dts files by patch would also have to
update the dtb, which can't be done in a normal patch, since they're
binary.
I'm working with sfr now on importing dtc into the kernel tree.
--
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
next prev parent reply other threads:[~2007-07-23 1:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 14:12 Someone broke my allmodconfig build Stephen Rothwell
2007-07-22 0:37 ` Paul Mackerras
2007-07-22 1:53 ` Stephen Rothwell
2007-07-23 13:15 ` Timur Tabi
2007-07-23 15:07 ` Grant Likely
2007-07-23 15:17 ` Josh Boyer
2007-07-23 15:47 ` Timur Tabi
2007-07-22 2:04 ` Josh Boyer
2007-07-23 1:43 ` David Gibson [this message]
2007-07-23 15:24 ` Mark A. Greer
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=20070723014337.GC3272@localhost.localdomain \
--to=dwg@au1.ibm.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).