devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Shawn Guo <shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	glikely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ARM:boot:device tree: Allow the device tree binary to be appended to zImage
Date: Tue, 15 Mar 2011 02:03:50 -0600	[thread overview]
Message-ID: <20110315080350.GN23050@angua.secretlab.ca> (raw)
In-Reply-To: <20110315075231.GH11098-+NayF8gZjK2ctlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>

On Tue, Mar 15, 2011 at 03:52:32PM +0800, Shawn Guo wrote:
> On Tue, Mar 15, 2011 at 11:44:22AM +0800, Shawn Guo wrote:
> > On Wed, Mar 09, 2011 at 01:58:00PM -0800, John Bonesio wrote:
> > > This patch provides the ability to boot using a device tree that is appended
> > > to the raw binary zImage (e.g. cat zImage <filename>.dtb > zImage_w_dtb).
> > > 
> > > Signed-off-by: John Bonesio <bones-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
> > > ---
> > > 
> > >  arch/arm/Kconfig                |    7 ++++
> > >  arch/arm/boot/compressed/head.S |   75 +++++++++++++++++++++++++++++++++++++--
> > >  2 files changed, 79 insertions(+), 3 deletions(-)
> > > 
> > I played this patch on mx51 babbage a little bit, and noticed that it
> > introduces one difference on both non-dt and dt kernel booting.  The
> 
> To be clear, the difference is being seen when I do not even enable
> CONFIG_ARM_APPENDED_DTB.

That would definitely be a bug then.

g.

  parent reply	other threads:[~2011-03-15  8:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 21:58 [PATCH] ARM:boot:device tree: Allow the device tree binary to be appended to zImage John Bonesio
2011-03-09 23:05 ` Ben Dooks
     [not found]   ` <20110309230542.GC9995-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2011-03-12  8:44     ` Grant Likely
2011-03-15  3:44 ` Shawn Guo
     [not found]   ` <20110315034421.GE11098-+NayF8gZjK2ctlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2011-03-15  7:52     ` Shawn Guo
     [not found]       ` <20110315075231.GH11098-+NayF8gZjK2ctlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2011-03-15  8:03         ` Grant Likely [this message]
2011-03-17 18:42 ` Nicolas Pitre
     [not found]   ` <alpine.LFD.2.00.1103171422500.26889-QuJgVwGFrdf/9pzu0YdTqQ@public.gmane.org>
2011-03-21 17:35     ` John Bonesio
     [not found]       ` <4D878C63.6080205-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
2011-03-21 18:22         ` Nicolas Pitre
     [not found]           ` <alpine.LFD.2.00.1103211413560.11889-QuJgVwGFrdf/9pzu0YdTqQ@public.gmane.org>
2011-03-21 18:36             ` John Bonesio

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=20110315080350.GN23050@angua.secretlab.ca \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=glikely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.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).