linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Locke <mlocke@mvista.com>
To: Dan Malek <dan@mvista.com>
Cc: Jure Menart <jure@kom.org>,
	linuxppc dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: linux-2.4 & 405gp & other stuff
Date: Thu, 16 Aug 2001 16:16:44 -0700	[thread overview]
Message-ID: <3B7C545C.9040600@mvista.com> (raw)
In-Reply-To: 3B7C3E51.52B43280@mvista.com


Dan Malek wrote:

> Jure Menart wrote:

> That's hardly a "bare" kernel......A serial port with an attached
> initrd ram disk is a "bare" kernel.  You have selected nearly everything
> that is supported.  I'm not sure if Oak will even run properly.  We
> have been using Tivo as the 403 test platform.
>

Oak doesn't compile anymore.


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

  reply	other threads:[~2001-08-16 23:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-16 15:55 linux-2.4 & 405gp & other stuff Jure Menart
2001-08-16 21:42 ` Dan Malek
2001-08-16 23:16   ` Matthew Locke [this message]
2001-08-17  0:29     ` Dan Malek
2001-08-17 17:19       ` Matthew Locke

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=3B7C545C.9040600@mvista.com \
    --to=mlocke@mvista.com \
    --cc=dan@mvista.com \
    --cc=jure@kom.org \
    --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).