From: Carlos Munoz <cmunoz@sablenetworks•com>
To: Sumesh Kaana <sumeshkkn@hotmail•com>
Cc: linuxppc-dev@lists•ozlabs.org
Subject: Re: Loading Linux from already running code..
Date: Mon, 26 Sep 2011 10:26:56 -0700 [thread overview]
Message-ID: <1317058016.1650.50.camel@pug> (raw)
In-Reply-To: <BLU124-W1648A42F7514E880C9B199B4F20@phx.gbl>
You could build a tarball containing the root files system, dtb, Linux,
plus a header indicating where the different pieces need to be loaded.
Then your initial code loads the different parts at the right memory
locations, sets up the Linux arguments, and jumps to Linux.
-Carlos
On Sun, 2011-09-25 at 18:47 +0000, Sumesh Kaana wrote:
> Hi All,
>
>
> I need some suggestions for booting Linux( >2.6.30 ) with my new
> project.
>
>
> Scenario:
> I've a custom built board with PowerPC 440 + 256 MB RAM. there is NO
> FLASH on this board.
> There is a hardware logic which will get an initial piece of
> code (through hardware network) into the ram and then execute it. This
> code does mandatory initialization of a proprietary chip and this code
> MUST execute on power on. any other images (Linux image or ramdisk)
> can be loaded any specified area in the memory along with this code.
>
>
> My requirement is to boot Linux at the end of the this initialization.
>
>
> what is the best way to do it?
>
>
> 1. Will it be possible to transfer control to a
> simpleImage.initrd.myboard.elf(or .bin ..?!) image from
> already_existing_code?
> 2. Should I use u-boot and then load uImage, ramdisk and the dts blob?
> Using u-boot will reduce the effort?
> 3. Is there any other way to approach this??
>
>
>
>
>
>
> Regards,
> Sumesh
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists•ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2011-09-26 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 18:47 Loading Linux from already running code Sumesh Kaana
2011-09-26 17:26 ` Carlos Munoz [this message]
2011-09-26 18:13 ` Philipp Ittershagen
2011-09-27 6:51 ` Sumesh Kaana
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=1317058016.1650.50.camel@pug \
--to=cmunoz@sablenetworks$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=sumeshkkn@hotmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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