From: Jonathan Larmour <jifl@eCosCentric.com>
To: eCos announcements <ecos-announce@sources.redhat.com>
Subject: eCos 2.0 announcement
Date: Tue, 20 May 2003 10:42:00 -0000 [thread overview]
Message-ID: <3ECA060C.8010809@eCosCentric.com> (raw)
We are pleased to announce that the eCos 2.0 final release is now
available. This is a stable release incorporating many new features and
support for 74 publically available evaluation and development platforms.
Architectural support covers ARM (including StrongARM and XScale), SuperH,
Intel x86 (IA32), PowerPC, MIPS, Matsushita AM3x, Motorola 68K/Coldfire,
SPARC, Renesas H8/300H and NEC V850.
System enhancements (relative to the previous eCos 1.3.1 release) include:
* RedBoot, the open source bootstrap and debug firmware based on eCos
* A choice of TCP/IP stacks including options for BOOTP/DHCP, DNS,
TFTP/FTP, SNMP, IPv6 and HTTPD
* RAM, ROM and flash file systems
* Power management support
* USB slave support
* A POSIX-compatible API
* Symmetric multiprocessing (SMP) support
This release includes a new version of the graphical eCos Configuration
Tool for both Linux and Windows hosts. Further enhancements are listed in
the NEWS file included in the release.
eCos 2.0 is also the first stable release under a new license which
provides compatibility with the well-known GNU General Public License
(GPL) while also allowing application source code to remain proprietary.
For download details, please visit the eCos project home page at:
http://ecos.sourceware.org/
The complete release, including pre-built GNU toolchains is also available
on CD-ROM from eCosCentric:
http://www.ecoscentric.com/ecos/cdrom.shtml
Finally, many thanks to all those who helped with the beta testing leading
up to this release.
Jonathan Larmour
Chief eCos Maintainer
on behalf of the eCos maintainers
reply other threads:[~2003-05-20 10:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3ECA060C.8010809@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-announce@sources.redhat.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).