public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: Booting the Linux/ppc64 kernel without Open Firmware HOWTO
Date: Thu, 19 May 2005 16:18:11 -0400	[thread overview]
Message-ID: <b1723d35d0375b75ec3e5ed2d4a4b31f@embeddededge.com> (raw)
In-Reply-To: <20050519193731.GF4138@austin.ibm.com>

On May 19, 2005, at 3:37 PM, Linas Vepstas wrote:

> :-/ I was once very disatisfied with an earlier job I had because the
> boss kept trying to make me use a "rabbitcore" which had only 1MB for
> everything, and there was no way I'd be able to fit Linux into that.

People understand the trade off of the need for resources to get
the features they want, which is why they choose Linux in the
first place.  Yes, sometimes people ask for what seems to be
unreasonable in such products, but it also forces us to be clever
about how we configure the systems.

The difficult trade off is when some states they get the same
feature set with one particular piece of software as they do with
Linux, but in much less space.  The advantage of Linux is open
source and no royalties, but many of the RTOS systems these days
no longer have royalties, just a one time up front cost.  When they
weigh that against the extra cost of memory for Linux and the number
of systems, the Linux "royalty" is more than the purchase of the
competing OS.  It's really happening that way today.

Thanks.


	-- Dan

  reply	other threads:[~2005-05-19 20:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18  7:09 [U-Boot-Users] RFC: Booting the Linux/ppc64 kernel without Open Firmware HOWTO Benjamin Herrenschmidt
2005-05-18  8:12 ` Marius Groeger
2005-05-18 23:11   ` Benjamin Herrenschmidt
2005-05-19  9:52     ` Marius Groeger
2005-05-19 10:22       ` Benjamin Herrenschmidt
2005-05-19 13:18         ` Wolfgang Denk
2005-05-19 19:37           ` Linas Vepstas
2005-05-19 20:18             ` Dan Malek [this message]
2005-05-19 22:33           ` Benjamin Herrenschmidt
2005-05-19 23:20             ` Wolfgang Denk
2005-05-19 23:42               ` Benjamin Herrenschmidt
2005-05-20  3:11             ` Benjamin Herrenschmidt
2005-05-20  7:11               ` Marius Groeger
2005-05-20  7:23                 ` David Gibson
2005-05-20  7:27                 ` Benjamin Herrenschmidt
2005-05-18 23:32   ` Benjamin Herrenschmidt
2005-05-19  4:56 ` [U-Boot-Users] RFC: Booting the Linux/ppc64 kernel without Open Firmware HOWTO (#2) Benjamin Herrenschmidt
2005-05-19  7:46   ` [U-Boot-Users] " Arnd Bergmann
2005-05-19  8:09     ` Benjamin Herrenschmidt
2005-05-19 16:24     ` Segher Boessenkool
2005-05-19 13:18   ` [U-Boot-Users] " Wolfgang Denk
2005-05-19 13:16     ` Pantelis Antoniou
2005-05-19 22:20     ` Benjamin Herrenschmidt
2005-05-19 23:14       ` Wolfgang Denk
2005-05-19 23:28         ` Benjamin Herrenschmidt
2005-05-20  6:44         ` Stefan Nickl
2005-05-20  3:51     ` Hollis Blanchard
2005-05-20  6:59       ` Wolfgang Denk
2005-05-20  4:24     ` Paul Mackerras
2005-05-20  4:28       ` Paul Mackerras
2005-05-20  4:26   ` [U-Boot-Users] " Hollis Blanchard
2005-05-20  5:04     ` Benjamin Herrenschmidt

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=b1723d35d0375b75ec3e5ed2d4a4b31f@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=u-boot@lists.denx.de \
    /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