From: "Robin O'Leary" <robin@equiinet.com>
To: Dan Malek <dan@netx4.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linux-2.3.37 / 2.3.18 / 2.2.13
Date: Mon, 10 Jan 2000 21:10:47 +0000 [thread overview]
Message-ID: <20000110211045.F8416@mail.ro.nu> (raw)
In-Reply-To: <387A38DB.8C51AB1D@netx4.com>; from dan@netx4.com on Mon, Jan 10, 2000 at 02:54:03PM -0500
On Mon, Jan 10, 2000 at 02:54:03PM -0500, Dan Malek wrote:
> The 2.2.xx kernels are certainly the most stable and recommended
> if you are building products. There is a 2.2.13 tar image on
> ppc.kernel.org/embedded for 8xx processors. I don't know when
> some of the recent changes happened, but the generic 2.3.18
> kernel has all of the 8xx changes.
Most recently (apart from trying the doomed 2.3.37) I have been using
2.3.18 (from ftp://linuxppc.cs.nmt.edu/pub/linuxppc/embedded) on
custom 860T hardware. As you may have gathered from my earlier post
on 1999-11-29, all has not been going smoothly. Although I have now
coaxed 2.3.18 as far as trying to load the initrd, it has been an uphill
struggle all the way and I still haven't got the compressed bootloader
going properly. Could it be that my problems stem from using 2.3.18?
Robin O'Leary.
--
email: robin@equiinet.com Equiinet Ltd., Innovation Centre, Singleton Park,
Tel.: +44 1792 540008 Swansea SA2 8PP, Wales, U.K. 51.6101N 3.9831W
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-10 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-07 21:35 linux-2.3.37 Robin O'Leary
2000-01-10 19:54 ` linux-2.3.37 Dan Malek
2000-01-10 21:10 ` Robin O'Leary [this message]
2000-01-10 22:40 ` linux-2.3.37 / 2.3.18 / 2.2.13 Dan Malek
2000-01-10 23:32 ` Alan Mimms
2000-01-11 19:17 ` Marcus Sundberg
2000-01-12 0:17 ` 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=20000110211045.F8416@mail.ro.nu \
--to=robin@equiinet.com \
--cc=dan@netx4.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).