From: "David Beck" <davidbeck@acm.org>
To: <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] Books
Date: Sat, 03 Feb 2001 08:56:00 -0000 [thread overview]
Message-ID: <00ed01c08e03$3d27abb0$0201030a@dbnt41> (raw)
Check out http://www.compapp.dcu.ie/~cdaly/embed/books.html for a list of
embedded systems books.
I've found these books (in no particular order) to be informative on
embedded/real-time operating system implementation issues. Unfortunately
some of the older ones are probably out of print.
-Operating System Design: The XINU Approach, Vol. I (PC Edition)
by Douglas Comer, 1988
ISBN 0-13-638180-4
-Real-Time Software Design
by Philip Heller, 1987
ISBN 0-8176-3201-8, 3-7643-3201-8
-Real-Time Systems Design and Analysis, An Engineer's Handbook 2nd edition
by Phillip A. Laplante, 1997
ISBN 0-7803-3400-0
-MicroC/OS-II, The Real-time Kernel
by Jean J. Labrosse, 1999
ISBN 0-87930-543-6
-Real Time Programming, Neglected Topics
by Caxton C. Foster, 1982
ISBN 0-201-01937-X
-Introduction to Real-Time Software Design
by S. T. Allworth, 1981
ISBN 0-387-91175-8
===== Original Message =====
Date: Fri, 2 Feb 2001 08:10:09 -0800 (PST)
From: Kevin Werner <kwerner@yahoo.com>
To: ecos list <ecos-discuss@sourceware.cygnus.com>
Any comments on these books? Based on reviews from
Amazon.com, Barr's O'Reilly book seems like a good
place to start.
-Operating System Design (Prentice-Hall Software
Series)
by Douglas Comer
-Operating System Design: The XINU Approach, Vol. I
by Douglas Comer
-An Embedded Software Primer
by David E. Simon
-Programming Embedded Systems in C and C ++
by Michael Barr - O'Reilly
=====
Kevin Werner
kwerner@yahoo.com
next reply other threads:[~2001-02-03 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-03 8:56 David Beck [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-02 7:08 James Dabbs
2001-02-02 8:10 ` Kevin Werner
2001-02-01 16:03 Kevin Werner
2000-11-08 4:46 Claes Stejre
2000-11-08 5:59 ` Bart Veer
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='00ed01c08e03$3d27abb0$0201030a@dbnt41' \
--to=davidbeck@acm.org \
--cc=ecos-discuss@sourceware.cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).