From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org,
"David A. Gatwood" <marsmail@globegate.utm.edu>,
a sun <asun@saul9.u.washington.edu>
Subject: Re: Porting to NuBus PowerMacs
Date: Thu, 14 Jan 1999 12:12:21 +0100 [thread overview]
Message-ID: <19990114121221.005972@mail.mipsys.com> (raw)
In-Reply-To: <199901131910.LAA28570@saul9.u.washington.edu>
On Tue, Jan 12, 1999, a sun <asun@saul9.u.washington.edu> wrote:
>so, ben, i guess i'll also need memory addresses/sizes as well. after
>perusing the m68k code, i think that's the only thing that i forgot to
>tell you about. this will essentially make bootx report essentially
>the same information as the m68k boot loader.
I'll download this bootloader and see what it does. I don't know exactly
how to get this memory map yet, it would be great if David could manage
to find the info ...
>well, my "oh so clever plan" is actually to use the gestalt
>information to mock up something that i pass to the m68k interrupt
>routines. presto! no more uglification of irq.c. given the
>similarities between the apus stuff and the nubus powermac stuff, i'm
>actually turning the nubus powermacs into a variant of apus for now. a
>lot of my fiddling actually ends up making some minor changes to the
>m68k code and calling that instead.
>
>for now, i'm conveniently ignoring the dma stuff, but it looks like
>modifying the mac68k devices will actually prove to be more useful
>than dealing with the the standard pci powermac stuff.
I think so too. And PCI powermac is still evolving, it would be more
difficult to take care of not breaking the NuBus support during evolutions.
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-14 11:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-12 15:26 Porting to NuBus PowerMacs Hubert Figuiere
1999-01-12 19:29 ` Benjamin Herrenschmidt
1999-01-13 0:12 ` David A. Gatwood
1999-01-13 4:17 ` Dan Malek
1999-01-13 9:40 ` Hubert Figuiere
1999-01-13 16:18 ` Gary Thomas
1999-01-13 16:25 ` Hubert Figuiere
1999-01-13 17:27 ` [OT] " Geert Uytterhoeven
1999-01-13 20:07 ` David A. Gatwood
1999-01-13 18:55 ` David A. Gatwood
1999-01-14 18:15 ` Jules Bean
1999-01-14 18:33 ` Michael Schmitz
1999-01-14 20:18 ` David A. Gatwood
1999-01-12 20:31 ` David A. Gatwood
1999-01-12 23:32 ` Paul Mackerras
1999-01-13 21:14 ` Tom Vier
1999-01-12 20:31 ` a sun
1999-01-13 19:21 ` David A. Gatwood
1999-01-13 19:27 ` David A. Gatwood
1999-01-14 4:09 ` a sun
1999-01-14 4:23 ` David A. Gatwood
1999-01-14 2:12 ` Troy Benjegerdes
1999-01-14 11:12 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-01-13 5:40 Ron Nelson
1999-01-13 21:22 ` Tom Vier
1999-01-13 13:57 Kaoru Fukui
1999-01-14 15:24 Porting to Nubus PowerMacs Alexander Gustav Deucher
1999-01-14 22:37 ` Gabriel Paubert
1999-01-15 9:03 ` Troy Benjegerdes
1999-01-15 11:09 ` Gabriel Paubert
1999-01-15 16:12 ` Alois Fertl
1999-01-15 19:36 ` 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=19990114121221.005972@mail.mipsys.com \
--to=bh40@calva.net \
--cc=asun@saul9.u.washington.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=marsmail@globegate.utm.edu \
/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.