From: Ralf Baechle <ralf@linux-mips.org>
To: Greg Weeks <greg.weeks@timesys.com>
Cc: linux-mips@linux-mips.org
Subject: Re: 4kc machine check
Date: Wed, 6 Apr 2005 21:02:55 +0100 [thread overview]
Message-ID: <20050406200255.GA4978@linux-mips.org> (raw)
In-Reply-To: <4254181A.9000301@timesys.com>
On Wed, Apr 06, 2005 at 01:10:50PM -0400, Greg Weeks wrote:
> I noticed there was a recent checkin for 4000 series tlb code. It still
> seems to be a problem on the 4kc malta.
4K is not R4000 series ... Anyway, the 4K code you were sent aren't yet
in because they've only empirically proven to be correct; we'd like to
look into the case a little further before comitting the patches into CVS.
Ralf
next prev parent reply other threads:[~2005-04-07 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 17:10 4kc machine check Greg Weeks
2005-04-06 20:02 ` Ralf Baechle [this message]
2005-04-07 11:37 ` Greg Weeks
-- strict thread matches above, loose matches on Subject: below --
2003-05-10 19:49 Linux for MIPS Atlas 4Kc board Jan-Benedict Glaw
2005-07-19 6:43 ` 4kc machine check Michael Anburaj
2005-07-19 12:02 ` Maciej W. Rozycki
2005-07-20 20:05 ` Michael Anburaj
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=20050406200255.GA4978@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=greg.weeks@timesys.com \
--cc=linux-mips@linux-mips.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