From: Chris Zimman <chris@cryptoapps.com>
To: Chris Zimman <chris@cryptoapps.com>,
Linux on PowerPC Developers Mail List
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: looking for documentation on porting Linux to PowerPC platforms
Date: Thu, 5 Dec 2002 10:35:09 -0800 [thread overview]
Message-ID: <20021205183509.GA10250@mail.cryptoapps.com> (raw)
In-Reply-To: <20021205104856.A3899@crystal.2d3d.co.za>
On Thu, Dec 05, 2002 at 10:48:56AM +0200, Abraham vd Merwe wrote:
> I've got a VxWorks boot loader on the thing, so I'm not worrying about a
> boot loader right now. I just need to know what I need to setup before
> branching to the processor. Looking at the source for the 8xx processors, it
> seems I need:
I've never looked at the VxWorks boot loader, so I'm not sure how it
does things.
> ------------< snip <------< snip <------< snip <------------
> r3: ptr to board info data
> r4: initrd_start or if no initrd then 0
> r5: initrd_end - unused if r4 is 0
> r6: start of command line string
> r7: end of command line string
> ------------< snip <------< snip <------< snip <------------
>
> Is that all? Also, what is the "board info data" ?
bd_t contains parameters for the kernel (eg. start of memory, size,
start of flash, etc.).
> I downloaded ppc-patch-2.4.18.bz2 from
> ftp://ftp.kernel.org/pub/linux/kernel/ports/ppc - is that sufficient or is
> there better support in the BK repository?
You'd probably be best getting the code from the BK repository. Again,
what you most likely want is 2.4.x + platforms.
--Chris
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-05 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 8:38 looking for documentation on porting Linux to PowerPC platforms Abraham vd Merwe
[not found] ` <20021204192129.GA8996@mail.cryptoapps.com>
2002-12-05 8:48 ` Abraham vd Merwe
2002-12-05 18:35 ` Chris Zimman [this message]
[not found] ` <1039025018.651.43.camel@zion>
2002-12-05 8:54 ` Abraham vd Merwe
2002-12-05 9:33 ` Benjamin Herrenschmidt
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=20021205183509.GA10250@mail.cryptoapps.com \
--to=chris@cryptoapps.com \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.