From: "Kevin A. Sapp" <Kevin.Sapp@catapult•com>
To: linuxppc-embedded@lists•linuxppc.org
Subject: Boot Loader
Date: Mon, 22 Dec 2003 06:59:47 -0500 [thread overview]
Message-ID: <3FE6DCB3.109@catapult.com> (raw)
In-Reply-To: <OJEPIMKHOKJAJIDJLJBNAEKLCAAA.jbates@paradise.co.uk>
Hello,
For my end target I have to boot across a shared memory
interface by placing the executable into RAM. This is
part of a multi processor system where the Linux board
is a cPCI slave. The Linux board will not have a flash
or a network connection. I is held in reset by the master
until the s/w is loaded and then released. This is an 8275
target. The "Master" is a Solaris Workstation or a PC
style Linux box or card.
Any suggestions on how to do this ?
Have to fill in my own board info in a bd_t struct,
pass it in R3, if I use and initrd it's start and end ptrs
go into R4, R5 and the cmd line params will
be hard coded and inserted into R6,R7...
I will be using a RAM disk for the root file system.
Instead of compressing and creating uImage for das u-boot,
I create a binary(?) image and just shove it into RAM at
0? Ensure the Reset vec is set to my initialization code
that will be part of the download...
Any ideas would be appreciated.
Thank you
Kevin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-22 11:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031217093448.A18081@lists.linuxppc.org>
2003-12-17 17:11 ` Executable delay James Bates
2003-12-22 9:58 ` James Bates
2003-12-22 11:59 ` Kevin A. Sapp [this message]
2003-12-22 13:08 ` Boot Loader Wolfgang Denk
2002-12-09 6:05 Erik Christiansen
2002-12-09 7:43 ` Wolfgang Denk
2002-12-10 7:54 ` Erik Christiansen
[not found] <36E192B5.6C18381B@noaa.gov>
1999-03-07 1:04 ` boot loader Cort Dougan
1999-03-08 10:14 ` Gabriel Paubert
1999-03-08 19:33 ` Cort Dougan
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=3FE6DCB3.109@catapult.com \
--to=kevin.sapp@catapult$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/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