From: Kent Borg <kentborg@wavemark.com>
To: fray@gate.crashing.org
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: RFC: Embedded Linux Page
Date: Tue, 20 Jun 2000 10:00:59 -0400 [thread overview]
Message-ID: <200006201400.KAA19361@rome.wavemark.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10006191845040.19948-100000@gate.crashing.org> (message from Mark Hatle on Mon, 19 Jun 2000 18:48:59 -0500 (CDT))
Mark Hatle <fray@gate.crashing.org> wrote:
>Now what I need from you folks are suggests on content
As a representative of one part of your audience, let me describe what
I have been missing: a non-Linux perspective. Now before you dismiss
me as a weirdo who is posting to the wrong mailing list, please read a
bit further.
I have been a user of Linux for some time, I currently use it as a
platform for cross development work, and I used various versions of
Sun's Unix back when. But my current work is writing embedded
software. I start out knowing next to nothing about the Linux kernel,
I have never programmed Linux itself, I don't know (though am
learning) Linux internals. I am an embedded person looking at Linux,
not a Linux person looking at embedding it.
Whether it be true or not, I get the impression that the embedded
community is largely Linux experts who have decided that Linux can
even be used for embedded purposes, ("Isn't Linux great!"). The
sequence seems to be that many of you folks know Linux first, and then
work to adapt it to embedded uses.
Well, I think Linux is great too, but I know less about it and so my
affection for Linux is based more on faith and politics than it is
based on deep knowledge. My sequence is different, I have very
specific embedded needs and also somehow have this idea I need to
learn how to how to get Linux to fill them.
The difference might be subtle, but I think there is one.
As a smidge of evidence, one of the open questions we have is how to
execute embedded software directly from ROM (yes, flash ROM!) without
needing to page it through RAM first. No one seems to do this because
it is very much at odds with how Linux traditionally works, but it is
very common (might I say standard?) in embedded systems to execute
code directly out of ROM, and when you add up the parts costs it can
frequently be economical.
I don't mention this to complain over Linux's defects for not already
having such an option (something tells me I will be the one to write
it once I learn enough about Linux to figure out how), rather I use it
to illustrate a difference in perspective that might be shared by the
next wave of adopters of embedded Linux.
What does this mean for setting up the embedded section of
linuxppc.org? Only to remember that as Linux becomes more mainstream
(my biggest allies here in looking at embedded Linux are possibly
non-technical folks!) some of your audience will be now coming from
embedded environments and just beginning to look at Linux, not coming
from Linux and adapting it to embedded programming.
The difference in what folks like me don't know will be different, so
how we look at your parts of linuxppc.org will be different too.
OK, I'll shut up now.
Thanks,
-kb, the Kent who has been doing "old" work the last few days and so
not getting any time to play with Linux.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-20 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 23:48 RFC: Embedded Linux Page Mark Hatle
2000-06-20 14:00 ` Kent Borg [this message]
2000-06-20 14:44 ` Daris Nevil
2000-06-20 15:20 ` Ron Flory
-- strict thread matches above, loose matches on Subject: below --
2000-06-20 2:40 Mark Hatle
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=200006201400.KAA19361@rome.wavemark.com \
--to=kentborg@wavemark.com \
--cc=fray@gate.crashing.org \
--cc=linuxppc-embedded@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).