From: Dan Malek <dan@mvista.com>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Initialization code
Date: Thu, 21 Dec 2000 13:38:25 -0500 [thread overview]
Message-ID: <3A424E21.4B5741F@mvista.com> (raw)
Happy Holidays..........
I feel the need to severely hack up the mm/init.c and probably some
of kernel/setup.c because I am going to make this IBM4xx code work
and fit into the kernel. It is my holiday vacation project, and
any suggestions are welcome. I am going to rely upon many of the
updates that Tom Rini has recently sent around as patches, and do
this only in the linuxppc_2_5 BK tree.
Thanks.
-- Dan
--
I like MMUs because I don't have a real life.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-12-21 18:38 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=3A424E21.4B5741F@mvista.com \
--to=dan@mvista.com \
--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).