linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Milton Miller" <miltonm@bga.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 1/7] bootwrapper: Add a firmware-independent "raw" target.
Date: Fri, 14 Dec 2007 08:23:41 -0700	[thread overview]
Message-ID: <fa686aa40712140723y26154baauf28444fa73ca54d9@mail.gmail.com> (raw)
In-Reply-To: <f7eb0ae3da29213720e6b0049deca335@bga.com>

On 12/14/07, Milton Miller <miltonm@bga.com> wrote:
> On Fri Dec 14 10:43:27 EST 2007,  Stephen Neuendorffer wrote:
>
> > From: Grant Likely <grant.likely at secretlab.ca>
> >
> > This target produces a flat binary rather than an ELF file,
> > fixes the entry point at the beginning of the image, and takes
> > a complete device tree with no fixups needed.
> >
> > The device tree must have labels on /#address-cells, the timebase
> > frequency, and the memory size.
> >
> > Signed-off-by: Grant Likely <grant.likely at secretlab.ca>

For the record; this patch was lifted from my dev tree and in turn I
stole it from Scott Wood.

>
> > +$(obj)/zImage.raw: vmlinux $(dts) $(wrapperbits)
> > +       $(call if_changed,wrap,raw,$(dts))
> >
>
> This should be handled by the standard zImage% rule.

It's weird.  On my system the standard zImage rule wouldn't do this
target.  I had to add this rule just to get it to compile.  I've not
yet been motivated to revisit and fix it.

> I'm not sure exactly what platform you are using this on.  Apparently
> it is a legacy firmware that loads the image and jumps to it leaving
> interrupts on and not invalidating the cache.

Heh; actually it's a platform with *no* firmware.  :-)

It's on a Xilinx FPGA.  SDRAM is initialized by the FPGA design and
the kernel image is loaded either with a debugger, or via the
SystemACE device.  In either case, the kernel is the first thing to
run after reset.... oh, and reset is not as complete as one would
normally expect.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  reply	other threads:[~2007-12-14 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 23:43 [PATCH 1/7] bootwrapper: Add a firmware-independent "raw" target Stephen Neuendorffer
2007-12-14  8:05 ` Milton Miller
2007-12-14 15:23   ` Grant Likely [this message]
2007-12-14 17:31   ` Stephen Neuendorffer
2007-12-16 11:35   ` 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=fa686aa40712140723y26154baauf28444fa73ca54d9@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=miltonm@bga.com \
    /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).