From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org,
Hubert Figuiere <Hubert.Figuiere@solsoft.fr>
Subject: Re: Porting to NuBus PowerMacs
Date: Tue, 12 Jan 1999 20:29:48 +0100 [thread overview]
Message-ID: <19990112202948.028828@mail.mipsys.com> (raw)
In-Reply-To: <19990112162631.B29622@dirkpitt.solsoft.fr>
On Tue, Jan 12, 1999, Hubert Figuiere <Hubert.Figuiere@solsoft.fr> wrote:
>I'd like to know what would be the complexity of porting LinuxPPC
>to NuBus PowerMacs ?
<asun@saul6.u.washington.edu> is already thinking about it.
>Here are my thoughts:
>
>-we have BootX. So we can BootX LinuxPPC. We just need to build a
> fake OpenFirmware device tree for BootX so he can pass it the
> kernel
That was the original idea, but several things makes me wonder if it
wouldn't be simpler to just pass a list of known infos (total ram size,
processor type, machine ID and a couple of baseaddresses) to the kernel
and almost-hard-code things in drivers since this hardware will not
evolve very much now ;-)
Basically, I have to provide him a version of BootX that works on those
machines and provide the requested infos. I didn't have time to work a
lot on BootX those few last days, but I think I'll send him something
around the end of the week, maybe next week.
>-we have the source of the Mach MicroKernel, hence we have enough
> to rewrite the specification to rewrite drivers for LinuxPPC.
> Some components and drivers may directly come from Linux Mac68k.
We have also a lot of potentially useful things in the mac68k and APUS ports.
>Note that I don't have a NuBus PowerMac. Only a 6200 (and my
>PowerCenter Pro, already supported).
;-)
--
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-12 19:29 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 [this message]
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 ` 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
1999-01-12 20:31 ` David A. Gatwood
1999-01-12 23:32 ` Paul Mackerras
1999-01-13 21:14 ` Tom Vier
-- 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=19990112202948.028828@mail.mipsys.com \
--to=bh40@calva.net \
--cc=Hubert.Figuiere@solsoft.fr \
--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.