From: Dan Malek <dan@netx4.com>
To: "@Jean-Jacques GERMOND" <jjg@sxb.bsf.alcatel.fr>
Cc: dan@penguin.netx4.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: Ramdisk problem with 2.3.18 on mpc8xx boards
Date: Sun, 26 Sep 1999 11:20:22 -0400 [thread overview]
Message-ID: <37EE39B6.9C0AC07@netx4.com> (raw)
In-Reply-To: 199909241350.PAA02356tenor
@Jean-Jacques GERMOND wrote:
> We still want to port Linux, even an older version, on an mpc860
> or mpc823 board in order to get linux experience.
> We have a (probably VM) crash with the 2.2.10 in:
For 8xx, you should only be using the 2.2.5 or 2.3.18 tar image
from ppc.kernel.org/embedded, or the latest CVS tree.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-26 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-24 13:50 Ramdisk problem with 2.3.18 on mpc8xx boards @Jean-Jacques GERMOND
1999-09-26 15:20 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-22 15:28 Christophe Reinbold
1999-09-22 18:47 ` 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=37EE39B6.9C0AC07@netx4.com \
--to=dan@netx4.com \
--cc=dan@penguin.netx4.com \
--cc=jjg@sxb.bsf.alcatel.fr \
--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).