From: Mark Pilon <mpilon@midrivers.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: kernel for 405 w/ FPU available
Date: Wed, 11 Dec 2002 16:27:55 -0700 [thread overview]
Message-ID: <3DF7C9FB.C1BB9BA5@midrivers.com> (raw)
I've finished the initial work to support the IBM 405pm
[405 core, larger caches, FPU] and was wondering if anyone
wants it integrated into the _devel tree.
I worked out of the 2.4 _devel rsync tree (2.4.20-rc2) as I wasn't
able to get my bitkeeper snapshot to compile for walnut.
High level view of the changes:
config.in changes to set a cpu type of 405pm,
FPU unavailable exception, load_up_fpu(), giveup_fpu(),
additions to the ibm ethernet code to support the multiplexed
mal ints on the 405pm,
bits & pieces to tie it all together, and a hack or 2 which ought
to be reworked.
Missing:
no PCI, DMA or IDE support yet.
send me email if The Powers That Be want this stuff. It has been
stress tested with a mix of fpu tasks and handling a ping flood.
Mark
--
Mark Pilon
Minolta-QMS
P.O. Box 37
325 Dawson County Road 227
Fallon, MT. 59326-0037
1-406-486-5539 (primary voice line)
1-406-853-0433 (cell)
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2002-12-11 23:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3DF7C9FB.C1BB9BA5@midrivers.com \
--to=mpilon@midrivers.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mark.pilon@minolta-qms.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.