linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eddie Dawydiuk <eddie@embeddedarm.com>
To: Grant Likely <grant.likely@secretlab.ca>, linuxppc-dev@ozlabs.org
Subject: image/wrapper script questions
Date: Mon, 27 Jul 2009 10:10:24 -0700	[thread overview]
Message-ID: <4A6DDF80.209@embeddedarm.com> (raw)

Hello,

I'm working on a custom board using an AMCC 440EP that is using a proprietary 
bootloader(optimized for fast boot time). Currently our bootloader loads a 
simpleImage.initrd into RAM and jumps into it. I originally chose to use a 
simpleImage with an initial ramdisk embedded because it was the simplest 
solution to debug the hardware and get a kernel and initial ramdisk running for 
development. For production I would prefer to put the initial ramdisk on it's 
own partition to allow customers to easily modify the initrd without having to 
concern themselves with the details of how to recompile a kernel. Would you 
recommend using one of the existing images(e.g. boot wrapper) or modify the 
bootrom to load the PPC registers with the details of where to find the dts, 
kernel, and initrd?

Thanks for any suggestions :)

-- 
Best Regards,
________________________________________________________________
  Eddie Dawydiuk, Technologic Systems | voice:  (480) 837-5200
  16525 East Laser Drive              | fax:    (480) 837-5300
  Fountain Hills, AZ 85268            | web: www.embeddedARM.com

             reply	other threads:[~2009-07-27 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 17:10 Eddie Dawydiuk [this message]
2009-07-27 18:31 ` image/wrapper script questions Wolfgang Denk
2009-07-27 20:15   ` Eddie Dawydiuk
2009-07-27 21:53     ` Grant Likely

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=4A6DDF80.209@embeddedarm.com \
    --to=eddie@embeddedarm.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@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).