From: "Dan A. Dickey" <ddickey@charter.net>
To: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>,
cort@fsmlabs.com
Subject: NO_RELOAD_HTAB
Date: Wed, 10 May 2000 21:07:10 -0500 [thread overview]
Message-ID: <391A15CE.41488C9D@charter.net> (raw)
Cort (or anyone else),
can you tell me what NO_RELOAD_HTAB does in more detail?
I see it says its an optimization for the 603. Currently
in the source that I'm using, its set to 1 (so it *is* defined).
Some of the mmu code changes depending on whether it is
defined or not, and I'm having problems with the the first
InstructionTLBMiss. I have an MPC850SAR on a FADS board.
(Yes, I've heard all about the lowly fads...)
So, I was wondering what NO_RELOAD_HTAB is for before I go
delving into 860 & 850 mmu differences and the linux code
for them.
If anyone else is reading this, can you verify that your
linux code runs on both an 860 and 850 with no changes?
Thanks.
-Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-05-11 2:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-11 2:07 Dan A. Dickey [this message]
2000-05-11 16:56 ` NO_RELOAD_HTAB Dan Malek
2000-05-12 22:57 ` NO_RELOAD_HTAB 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=391A15CE.41488C9D@charter.net \
--to=ddickey@charter.net \
--cc=cort@fsmlabs.com \
--cc=linuxppc-embedded@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).