From: Jon Masters <jonmasters@gmail.com>
To: Jon Masters <jonathan@jonmasters.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: bi_recs
Date: Fri, 1 Oct 2004 22:54:32 +0100 [thread overview]
Message-ID: <35fb2e590410011454270f2698@mail.gmail.com> (raw)
In-Reply-To: <415D3C2C.7050704@jonmasters.org>
On Fri, 01 Oct 2004 12:14:52 +0100, Jon Masters <jonathan@jonmasters.org> wrote:
> Benjamin Herrenschmidt wrote:
> > I'd rather see you guys sync with what I did on ppc64 and use that
> > kind of OF device-tree, we already have all the code for using it
> > and it would make the mecanism compatible with the prep/chrp/pmac
> > kernel...
>
> Yeah. I'm going to start ripping through your code at the weekend and
> figure out how what you've done - not having a nice shiney ppc64 box
> means I've not yet got an excuse to play with that tree myself. I am
> however hopefull that my next Powerbook will be a G5 :-).
Hmmm...
ppc64 head.S and startup looks quite fun. After jumping through a few
hoops you eventually end up in prom_init and start setting up the OF
device-tree (btw it looks like at least one call to prom_panic doesn't
relocate the string it wants to print to real memory - is this what
the comments are referring to out of sheer interest?). I am assuming
that you always expect to see an Open Firmware on ppc64 and simply use
bi_recs to pass accross additional information from the bootloader,
but I've only had a cursory look on the train on the way home from
work this evening so please be gentle.
I'll give this a go through over the weekend and figure out how to get
this hooked in to the ppc32 tree.
Jon.
next prev parent reply other threads:[~2004-10-01 21:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 23:02 bi_recs Jon Masters
2004-09-30 23:21 ` bi_recs Benjamin Herrenschmidt
2004-09-30 23:53 ` bi_recs Jon Masters
2004-10-01 3:11 ` bi_recs Kumar Gala
2004-10-01 3:40 ` bi_recs Benjamin Herrenschmidt
2004-10-01 11:14 ` bi_recs Jon Masters
2004-10-01 14:53 ` [PATCH] for linuxppc-2.4 tree: adds Memec 2VP7 / 2VP4 board support Andrei Konovalov
2004-10-01 21:54 ` Jon Masters [this message]
2004-10-02 4:35 ` bi_recs Benjamin Herrenschmidt
2004-10-02 12:59 ` bi_recs Jon Masters
2004-10-01 22:06 ` bi_recs Tom Rini
2004-10-04 6:07 ` bi_recs Pantelis Antoniou
2004-10-04 12:09 ` bi_recs Mark Chambers
2004-10-04 12:45 ` bi_recs Jon Masters
2004-10-04 16:43 ` bi_recs Dan Malek
2004-10-04 21:53 ` bi_recs Tom Rini
2004-10-04 20:20 ` bi_recs Wolfgang Denk
2004-10-04 14:29 ` bi_recs Tom Rini
2004-10-04 14:41 ` bi_recs Matt Porter
2004-10-04 15:00 ` bi_recs Kumar Gala
2004-10-04 15:06 ` bi_recs Jon Masters
2004-10-04 15:47 ` bi_recs Kumar Gala
2004-10-04 20:18 ` bi_recs Wolfgang Denk
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=35fb2e590410011454270f2698@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=jonathan@jonmasters.org \
--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).