linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: mojtaba <kernelppc@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Booting Linux from an ACE File
Date: Fri, 16 May 2008 08:26:47 -0600	[thread overview]
Message-ID: <fa686aa40805160726i59c3d88l99c12a130eb073e2@mail.gmail.com> (raw)
In-Reply-To: <007a01c8b74c$0ad9c2e0$208d48a0$@com>

On Fri, May 16, 2008 at 5:57 AM, mojtaba <kernelppc@gmail.com> wrote:
> Dear all,
>
> Could you please explain what happens exactly when Linux is booting from a
> compact flash?
>
> To my few knowledge, the Linux compressed image will be copied somewhere in
> memory, will be uncompressed and the control will jump to the beginning
> address of the Linux kernel.

There are several methods to do this.

Option 1 is to pass the kernel zImage.elf to genace so that it gets
wrapped up into the ace file itself and is loaded into RAM by the
SystemACE on FPGA initialization.  However, this requires that your
FPGA design gets RAM initialized before the SysACE starts squirting in
the Linux image (which isn't always the case).  This option is also
slow.

Option 2 is to use an small bootloader blob (I think Xilinx has a
technote with something suitable) loaded into BRAM that reads the CF
card and copies a Linux image (hint; build a simpleImage when using
arch/powerpc) off the CF and into RAM.  This method boots the system
faster, but requires a little bit more work.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  parent reply	other threads:[~2008-05-16 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 11:57 Booting Linux from an ACE File mojtaba
2008-05-16 12:18 ` Marco Stornelli
2008-05-16 14:26 ` Grant Likely [this message]
2008-05-19 16:54 ` Stephen Neuendorffer

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=fa686aa40805160726i59c3d88l99c12a130eb073e2@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=kernelppc@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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).