From: Dan Malek <dmalek@jlc.net>
To: Grant Erickson <grant@lcse.umn.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: *_find_end_of_memory Mach Dep?
Date: Fri, 14 Jan 2000 17:31:34 -0500 [thread overview]
Message-ID: <387FA3C6.18E1DB1A@jlc.net> (raw)
In-Reply-To: Pine.SGI.4.10.10001141448520.254646-100000@brule.borg.umn.edu
Grant Erickson wrote:
>
> Instead of having a mess of ifdef's and such in MMU_init for {apus, pmac,
> m8xx, oak, chrp, etc}_find_end_of_memory, is there any compelling reason
> not to make a ppc_md machine dependency entry for these?
I didn't see a mess of ifdef's.....in fact a ppc_md entry wouldn't
change the ifdef's, it would just remove a couple of lines of code
in MMU_init().
I put the ifdef's there originally to remove lots of code from the 8xx
port that isn't needed. Perhaps with your 40x stuff we should consider
a more modular MMU_init() instead of the ifdef's, like creating multiple
mm/xxx_init.c files for the different MMU configurations (I can't believe
I said this, as I hate multiple files like this :-).
> If no one is in disagreement, I'd like to put a patch together for it.
Let's see what it looks like........
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-14 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-14 20:51 *_find_end_of_memory Mach Dep? Grant Erickson
2000-01-14 22:31 ` Dan Malek [this message]
[not found] <387F8EB3.B8098131@mitre.org>
2000-01-14 21:07 ` Grant Erickson
2000-01-14 22:34 ` Dan Malek
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=387FA3C6.18E1DB1A@jlc.net \
--to=dmalek@jlc.net \
--cc=grant@lcse.umn.edu \
--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).