From: Bernd Petrovitsch <bernd@firmix.at>
To: Daniel Rodrick <daniel.rodrick@gmail.com>
Cc: kernelnewbies@nl.linux.org, linux-newbie@vget.kernel.org
Subject: Re: Embedded Linux?
Date: Thu, 22 Jun 2006 10:59:30 +0200 [thread overview]
Message-ID: <1150966770.14766.26.camel@tara.firmix.at> (raw)
In-Reply-To: <292693080606212337q61c62cb1s56307a8f00847f8a@mail.gmail.com>
On Thu, 2006-06-22 at 12:07 +0530, Daniel Rodrick wrote:
[...]
> I'm a newbie, true to its every sense, and hence this question.
>
> I have come across the term "Embedded Linux" a lot of times. Is
> embedded linux a different branch of kernel all together? Or is it
Not really.
> that the vanila stock kernel (downloaded from kernel.org) becomes
> "Embedded Linux" when compiled for an embedded processor like ARM /
> PPC etc?
Yes. But nowadays there also "embedded" boards with Intel-compatible
CPUs (e.g. Celerons, VIA-C[23], etc. on PC104 boards, SoC, etc).
And not all PPCs can be considered "embedded" - think of IBM high-end
PPC machines.
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
next prev parent reply other threads:[~2006-06-22 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 6:37 Embedded Linux? Daniel Rodrick
2006-06-22 8:59 ` Bernd Petrovitsch [this message]
2006-06-22 10:38 ` Arjan van de Ven
2006-06-22 11:27 ` Jesper Juhl
2006-06-22 11:29 ` Jesper Juhl
-- strict thread matches above, loose matches on Subject: below --
2006-06-22 6:38 Daniel Rodrick
2006-06-22 7:19 ` Ray Olszewski
2006-06-22 7:30 ` Daniel Rodrick
2006-06-22 16:49 ` Ray Olszewski
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=1150966770.14766.26.camel@tara.firmix.at \
--to=bernd@firmix.at \
--cc=daniel.rodrick@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-newbie@vget.kernel.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