From: Tony Lee <TonyLee@ambernetworks.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] eCos porting and API document.
Date: Mon, 08 Jan 2001 15:31:00 -0000 [thread overview]
Message-ID: <D1CFA0665B6AD411878F00D0B7212EB766EDD7@usa01.ambernetworks.com> (raw)
Is there any porting and APIs document for eCos? I read the FAQs
but it doesn't have enough information.
I am looking for something similar QNX's documents at:
For system architecture:
http://www.qnx.com/literature/qnx_sysarch/index.html
On their evaluation CD (and website too, but I can' find the link),
there are detail document on all of their API support for BSP, design for
Resource
Manager, File system, etc.
Similar documents can be found for vxWorks.
For eCos to win the RTOS selection process, I think it needs documents for
System Archetecture.
port guide
Application APIs,
Subsystem (TCP/IP, file system, device driver) design document.
Can someone tell me if we pay Cygnus/RedHat for support, do I get any of
these documents?
I am semi-believer on "Feel the force, read the source", but I can't
convince management that is good enough.
-Tony
next reply other threads:[~2001-01-08 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 15:31 Tony Lee [this message]
2001-01-09 0:24 ` Jesper Skov
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=D1CFA0665B6AD411878F00D0B7212EB766EDD7@usa01.ambernetworks.com \
--to=tonylee@ambernetworks.com \
--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).