From: Scott Wood <scottwood@freescale.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/5] bootwrapper: Add CONFIG_DEVICE_TREE
Date: Thu, 12 Apr 2007 10:36:10 -0500 [thread overview]
Message-ID: <461E51EA.90600@freescale.com> (raw)
In-Reply-To: <17949.47307.827348.233684@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Hmmm, I'm not sure that I want to be asked about CONFIG_DEVICE_TREE on
> *all* powerpc platforms... Surely this option should depend on
> something that says we're including support for a uBoot-able platform?
That's how I originally had it, but I was asked to make it more general.
One non-uboot usage is Mark Greer's "Add Makefile rule to wrap dts
file in zImage" patch.
What about a CONFIG_WANT_DEVICE_TREE that platforms can select if they
want to ask the user for a device tree?
-Scott
next prev parent reply other threads:[~2007-04-12 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 20:51 [PATCH 0/5] bootwrapper: cuImage Scott Wood
2007-03-26 20:52 ` [PATCH 1/5] bootwrapper: Add dt_xlate_reg(), and use it to find serial registers Scott Wood
2007-03-26 20:52 ` [PATCH 2/5] bootwrapper: Add CONFIG_DEVICE_TREE Scott Wood
2007-04-12 4:42 ` Paul Mackerras
2007-04-12 15:36 ` Scott Wood [this message]
2007-04-12 16:11 ` Kumar Gala
2007-04-12 16:17 ` Scott Wood
2007-04-12 16:49 ` Kumar Gala
2007-03-26 20:52 ` [PATCH 3/5] bootwrapper: Add a cuboot platform and a cuImage target Scott Wood
2007-03-26 20:52 ` [PATCH 4/5] bootwrapper: Add ppcboot.h Scott Wood
2007-03-26 20:52 ` [PATCH 5/5] bootwrapper: cuboot for 83xx 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=461E51EA.90600@freescale.com \
--to=scottwood@freescale.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 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.