linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alan Mimms <alan@packetengines.com>
To: Dan Malek <dan@netx4.com>, "Robin O'Leary" <robin@equiinet.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linux-2.3.37 / 2.3.18 / 2.2.13
Date: Mon, 10 Jan 2000 15:32:06 -0800	[thread overview]
Message-ID: <00011015324501.02687@alan.corp.packetengines.com> (raw)
In-Reply-To: <387A5FD5.33A21291@netx4.com>


Dan, the lack of RAMDISK support is still on Alan/Linus's "must do" list
before 2.3.x can become 2.4.x.  That would seem to imply that the necessary
work has not been done.

a

On Mon, 10 Jan 2000, Dan Malek wrote: > Robin O'Leary
wrote: >  > 
> > ....  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?
> 
> 
> As I recall, the ram disk didn't work in 2.3.18.  There are some
> general things that don't work in 2.3.18, so I bailed out and
> updated 2.2.xx to get something stable.  Since 2.3.xx is now
> in it's mid-30's (still younger than I :-), perhaps it is mature
> enough that I should visit again and make sure the 8xx configuration
> continues to work.
> 
> 
> 	-- Dan
-- 
Alan Mimms     Packet Engines, Inc.     Spokane, Washington [99214-0497]
  USA, Earth, Sol, Milky Way, The Local Group, Virgo Supercluster, U0
Despite the cost of living, have you noticed how popular it remains?
  -- Steven Wright?

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-01-10 23:32 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   ` linux-2.3.37 / 2.3.18 / 2.2.13 Robin O'Leary
2000-01-10 22:40     ` Dan Malek
2000-01-10 23:32       ` Alan Mimms [this message]
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=00011015324501.02687@alan.corp.packetengines.com \
    --to=alan@packetengines.com \
    --cc=dan@netx4.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=robin@equiinet.com \
    /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).