From: Dan Malek <dmalek@jlc.net>
To: Grant Erickson <grant@lcse.umn.edu>
Cc: Charles Lepple <clepple@mitre.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: *_find_end_of_memory Mach Dep?
Date: Fri, 14 Jan 2000 17:34:49 -0500 [thread overview]
Message-ID: <387FA489.1F31B1AA@jlc.net> (raw)
In-Reply-To: Pine.SGI.4.10.10001141504430.254646-100000@brule.borg.umn.edu
Grant Erickson wrote:
> On Fri, 14 Jan 2000, Charles Lepple wrote:
> > When I converted some code to the ppc_md interface, I seem to remember a
> > few cases where I couldn't do it that way because the ppc_md structure
> > was not completely filled out. It can get to be a catch-22 -- there has
> > to be one messy function.
I already checked this before I sent my reply, and it should work fine.
> So, it seems reasonable that "identify_machine" remains the messy
> function and MMU_init could be cleaned up somewhat.
It only looks messy because you haven't seen it grow over the years :-).
I think it is aging rather gracefully.....
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-14 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <387F8EB3.B8098131@mitre.org>
2000-01-14 21:07 ` *_find_end_of_memory Mach Dep? Grant Erickson
2000-01-14 22:34 ` Dan Malek [this message]
2000-01-14 20:51 Grant Erickson
2000-01-14 22:31 ` 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=387FA489.1F31B1AA@jlc.net \
--to=dmalek@jlc.net \
--cc=clepple@mitre.org \
--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).