From: fraher <fraher@pweh.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MVME2604 Problems with MMU
Date: Tue, 14 Nov 00 07:00 EST [thread overview]
Message-ID: <3a1129490.957@clbdev2.eh.pweh.com> (raw)
Thanks for the suggestions, it looks like upgrading
to 2.2.17 is the next thing to try.
Bill Fraher
fraher@pratt-whitney.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-11-14 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 12:00 fraher [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-09 20:48 MVME2604 Problems with MMU fraher
2000-11-10 9:00 ` Gabriel Paubert
2000-11-10 10:08 ` Michael Lundkvist
2000-11-10 15:29 ` Don Holmgren
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=3a1129490.957@clbdev2.eh.pweh.com \
--to=fraher@pweh.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).