From: Ralf Baechle <ralf@linux-mips.org>
To: Karsten Merker <karsten@excalibur.cologne.de>, linux-mips@linux-mips.org
Subject: Re: MIPS Kernel size
Date: Mon, 2 Feb 2004 19:57:26 +0100 [thread overview]
Message-ID: <20040202185726.GB23667@linux-mips.org> (raw)
In-Reply-To: <20040202184325.GE913@excalibur.cologne.de>
On Mon, Feb 02, 2004 at 07:43:25PM +0100, Karsten Merker wrote:
> Depends on what you consider "that small". Kernel size is a large
> issue for the Cobalt series due to the firmware limits (although
> Peter Hortons attempts at a Cobalt bootloader will hopefully help in
> this regard). Embedded stuff and PDAs is another field where 2.6
> currently seems to pose a problem.
I really hate that term "embedded" - it's very hard to define. Anyway,
there's an increasing amount of so-called embedded systems with several
gigabytes of memory and even for much smaller system 2.6 is already
making 2.4 look pale.
The Cobalt case is special; it's firmware could almost be the definition
of the term crap ...
Ralf
next prev parent reply other threads:[~2004-02-02 18:57 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 [this message]
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
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=20040202185726.GB23667@linux-mips.org \
--to=ralf@linux-mips.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.