From: Matt Porter <mporter@kernel•crashing.org>
To: ming lei <mlei30@yahoo•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: MMUCR on ppc440 GP/GX
Date: Tue, 24 May 2005 13:38:19 -0700 [thread overview]
Message-ID: <20050524133819.B23084@cox.net> (raw)
In-Reply-To: <20050524183650.16871.qmail@web61017.mail.yahoo.com>; from mlei30@yahoo.com on Tue, May 24, 2005 at 11:36:50AM -0700
On Tue, May 24, 2005 at 11:36:50AM -0700, ming lei wrote:
>
> what's the latest ppc440 linux code that I can take
> look at?
Grab the current kernel.org 2.6 release. I suggest you use
dirdiff another recent 2.4 kernel and then analyze the 2.6 stuff
as it is different yet. There are countless bug fixes that have
gone in over the last 3 years. I sincerely hope you aren't
trying to use that old kernel with experimental PPC440 support
for production work.
> BTW, what's the problem three years ago prompted to
> change the code regarding mmucr handling?
The problem was that the initial code would crash apps regularly. I
put the code out in our development tree at the time since it was
taking a long time to find the bug...and you could mostly run a
system. The MMUCR was not having the TID set properly during
a tlbie() and a couple other spots in head_440.S.
-Matt
next prev parent reply other threads:[~2005-05-24 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 18:36 MMUCR on ppc440 GP/GX ming lei
2005-05-24 20:38 ` Matt Porter [this message]
2005-06-01 21:32 ` Does linuxppc_2_4_devel still accept patch? ming lei
-- strict thread matches above, loose matches on Subject: below --
2005-05-24 22:30 MMUCR on ppc440 GP/GX ming lei
2005-05-23 20:55 ming lei
2005-05-23 22:03 ` Matt Porter
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=20050524133819.B23084@cox.net \
--to=mporter@kernel$(echo .)crashing.org \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=mlei30@yahoo$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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