Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Karsten Merker <karsten@excalibur.cologne.de>,
	Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: MIPS Kernel size
Date: Mon, 2 Feb 2004 21:32:37 +0100	[thread overview]
Message-ID: <20040202203237.GG24843@linux-mips.org> (raw)
In-Reply-To: <20040202200742.GG1458@rembrandt.csv.ica.uni-stuttgart.de>

On Mon, Feb 02, 2004 at 09:07:42PM +0100, Thiemo Seufer wrote:

> > Oh, it boots everything as long as it's a compress ELF executable named
> > /vmlinux.gz
> 
> AFAIK it also boots such a kernel from a NFS(!) export.

Well possible - the firmware contains a Linux kernel of approx 2.0.30
vintage, so that would have been easy to arrange.  When I kernel work for
Cobalt however booting from disk and over serial were the only two
available options.

  Ralf

  reply	other threads:[~2004-02-02 20:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 14:51 MIPS Kernel size kip.r2
2004-01-27 16:10 ` Thiemo Seufer
2004-02-02 14:09 ` Ralf Baechle
2004-02-02 18:43   ` Karsten Merker
2004-02-02 18:57     ` Ralf Baechle
2004-02-02 19:38       ` Geert Uytterhoeven
2004-02-02 19:46         ` Ralf Baechle
2004-02-02 19:50           ` Geert Uytterhoeven
2004-02-02 19:59             ` Ralf Baechle
2004-02-02 20:07               ` Thiemo Seufer
2004-02-02 20:32                 ` Ralf Baechle [this message]
2004-02-02 22:29         ` Peter Horton
  -- strict thread matches above, loose matches on Subject: below --
2004-02-02 16:12 Smith, Todd
2004-02-02 18:53 ` Ralf Baechle
2004-02-02 21:48 Smith, Todd
2004-02-03 13:41 ` Maciej W. Rozycki
2004-02-03 15:17   ` Ralf Baechle
2004-02-03 14:50 ` Jan-Benedict Glaw
2004-02-03 15:18   ` Ralf Baechle
2004-02-03 16:52     ` Jan-Benedict Glaw
2004-02-03 17:07       ` Ralf Baechle
2004-02-03 15:16 ` Ralf Baechle

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=20040202203237.GG24843@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=geert@linux-m68k.org \
    --cc=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=karsten@excalibur.cologne.de \
    --cc=linux-mips@linux-mips.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