From: Tom Vier <nester@erols.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Porting to NuBus PowerMacs
Date: Wed, 13 Jan 1999 16:14:25 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.990113161217.4699D-100000@zero> (raw)
In-Reply-To: <Pine.LNX.3.96.990112141237.3746A-100000@globegate.utm.edu>
On Tue, 12 Jan 1999, David A. Gatwood wrote:
> It's a lot harder than this, unfortunately. The NuBus machines' memory
> isn't contiguous. Thus, code would have to be written and/or obtained to
doh!
> find out what memory is available in the machine and where that memory is
> located in RAM. That's going to be a nasty problem unless some code is
> pulled from the MkLinux booter. I'd expect that to also require a
> substantial number of changes to the way memory is handled in linux, but I
> could be wrong.
hhmmm. don't some other arch's have non contiguous memory?
> Beyond that, it will also require changes to irq.c to handle the interrupt
> controller and a lot of code for DMA, if that's desired (I don't think
> it's even remotely similar, AFAICT). Of course, that stuff can be
> obtained from Mach, but it'll be a lot of work. Oh, and the i/o base
> address is different, which may or may not be a problem, and supporting
> certain pieces of hardware (which will remain nameless) will also require
> speed penalties (this is the other reason MkLinux is slower than
> LinuxPPC...).
what pieces of hardware? important ones?
--
Tom Vier - 0x82B007A8
thomassr@erols.com | goto the Zero Page at:
Tortured Souls Software | http://www.erols.com/thomassr/zero/
[[ 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-13 21:14 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 ` 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 [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=Pine.LNX.3.96.990113161217.4699D-100000@zero \
--to=nester@erols.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=thomassr@erols.com \
/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.