From: Dan Malek <dmalek@jlc.net>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: linuxppc-dev@lists.linuxppc.org,
Hubert Figuiere <Hubert.Figuiere@solsoft.fr>
Subject: Re: Porting to NuBus PowerMacs
Date: Tue, 12 Jan 1999 23:17:25 -0500 [thread overview]
Message-ID: <369C1E55.A6B14256@jlc.net> (raw)
In-Reply-To: 19990112202948.028828@mail.mipsys.com
Benjamin Herrenschmidt wrote:
> 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 ;-)
This is what we do with the embedded LinuxPPC ports now.
The data structure is a combination of things the boot rom gives
us and other configuration tidbits the Linux boot loader can find.
It wouldn't be hard to expand this to other systems.
The next challenge would be to support OF fucntions (like find_devices(), etc.)
for those drivers that run on both platforms. As the embedded systems
mature, we may soon be doing this.......
-- Dan
[[ 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 4:17 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 [this message]
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=369C1E55.A6B14256@jlc.net \
--to=dmalek@jlc.net \
--cc=Hubert.Figuiere@solsoft.fr \
--cc=bh40@calva.net \
--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 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).