From: Wolfgang Denk <wd@denx.de>
To: Paratimer@aol.com
Cc: rddunlap@osdl.org, lm@bitmover.com, erwin@muffin.org,
yodaiken@fsmlabs.com, linux-kernel@vger.kernel.org,
rtai@rtai.org
Subject: Re: RTAI/RtLinux
Date: Mon, 27 May 2002 17:18:48 +0200 [thread overview]
Message-ID: <20020527151853.212DA11973@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 27 May 2002 10:37:47 EDT." <a0.2767541f.2a239ebb@aol.com>
In message <a0.2767541f.2a239ebb@aol.com> Joachim Martillo wrote:
>
> Did I say anything about limited resources? In any case, I have been
> building and designing embedded and turnkey systems for 20 years.
> I would be extremely dubious of any design that passed by my
> desk that proposed the use of a general purpose multiuser,
> multiprocessing, time sliced, preemptive, multimode, virtual
> memory operating system for a digital video recorder.
So what do you recommend when the requirement specification lists
features as
- Web interface (interface to electronic program guide database)
- network interface (up- / download to normal PC over ethernet)
- IEEE1384 interface (for digital cameras)
- USB interface (for keyboard, printer)
...
Would you start from scratch, or buy component by component, or just
use Linux?
> > Again, this is not quite correct. There have been Real-Time and
> > Embedded Unix systems before (LynxOS, to name one). And there are
> > other "common proprietary operating systems" that can be adapted for
> > embedded needs (WinCE).
>
> And is there anything that can be done with WinCE or the various
> RT/unix knock-off's that cannot be done better without?
Please let me keep my mouth shut about WinCE.
But yes, there are situations where "the various RT/unix knock-off's"
are the optimal solution (fastest time to market, lowest cost, most
features, highest reliability).
> Excuse me, but we are talking embedded systems. At some
> point there will be copyrighted tradesecreted or patented programs
> in the system.
Maybe. As application. So what? That does not mean that the OS
kernel, device drivers etc. may not be available under GPL.
> > The problems with Linux in Embedded and especially in Real-Time
> > Systems are not technical ones. It is the political situation, where
> > the user is left in uncertainty about what he can legally do and what
> > not.
>
> Easy enough to deal with. One generates an appropriate real time
> embedded turnkey operating system customized for the embedded
> turnkey application. In my experience, it takes about 4-6 weeks
> without disk management and perhaps 8-12 with disk management.
I see. Yes, there are problems of that class. But that's not what I'm
talking about.
> And then one does not have to deal with multimegabytes of
> non-locally produced code that is just lying in wait to cause
> problems.
??? What are you talking about?
> You may need to learn more about doing business in the USA.
Definitely. I learn a lot each day.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
If ignorance is bliss, why aren't there more happy people?
next parent reply other threads:[~2002-05-27 15:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a0.2767541f.2a239ebb@aol.com>
2002-05-27 15:18 ` Wolfgang Denk [this message]
[not found] <57.c083d0f.2a237c49@aol.com>
2002-05-27 12:36 ` RTAI/RtLinux Wolfgang Denk
2002-05-25 9:05 RTAI/RtLinux Erwin Rol
2002-05-25 9:16 ` RTAI/RtLinux Erwin Rol
2002-05-25 13:30 ` RTAI/RtLinux Alan Cox
2002-05-25 13:42 ` RTAI/RtLinux Erwin Rol
2002-05-25 13:21 ` RTAI/RtLinux Der Herr Hofrat
2002-05-25 15:08 ` RTAI/RtLinux Erwin Rol
2002-05-25 16:05 ` RTAI/RtLinux Larry McVoy
2002-05-25 16:28 ` RTAI/RtLinux Karim Yaghmour
2002-05-25 16:30 ` RTAI/RtLinux Erwin Rol
2002-05-25 17:31 ` RTAI/RtLinux Randy.Dunlap
2002-05-25 17:40 ` RTAI/RtLinux Eric Brunner-Williams in Portland Maine
2002-05-25 18:04 ` RTAI/RtLinux Randy.Dunlap
2002-05-25 17:42 ` RTAI/RtLinux Wolfgang Denk
2002-05-26 4:03 ` RTAI/RtLinux Kevin O'Connor
2002-05-26 4:17 ` RTAI/RtLinux Alexander Viro
2002-05-26 4:18 ` RTAI/RtLinux Larry McVoy
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=20020527151853.212DA11973@denx.denx.de \
--to=wd@denx.de \
--cc=Paratimer@aol.com \
--cc=erwin@muffin.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=rddunlap@osdl.org \
--cc=rtai@rtai.org \
--cc=yodaiken@fsmlabs.com \
/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).