public inbox for ecos-announce@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@cygnus.co.uk>
To: ecos-announce@sourceware.cygnus.com
Subject: eCos 1.2.1 release now available
Date: Mon, 17 May 1999 08:56:00 -0000	[thread overview]
Message-ID: <199905171553.QAA14969@sheesh.cygnus.co.uk> (raw)

The eCos team is pleased to announce that the second public release of
the Embedded Cygnus Operating System is now available. Since the
original eCos 1.1 release a wide range of new features and additional
ports have been added. eCos 1.2.1 incorporates the following
enhancements:

New architectures:
 * Advanced RISC Machines ARM7
 * Fujitsu SPARClite MB8683x series of processors
 * PowerPC MPC860 support has been extended to include the MPC850 and
   MPC823 variants.
 * Work has started on a further two architectures, the VR4300 and the
   SH-3. See the Cygnus web pages for details of our early access
   program. 

Several new evaluation board ports:
 * ARM PID7T
 * ARM AEB-1 (beta)
 * Cogent CMA287-50 - PowerPC MPC850
 * Cogent CMA287-23 - PowerPC MPC823
 * Motorola FADS860 (unsupported contributed port)
 * Fujitsu MB8683x series evaluation boards

New tools features:
 * Synthetic target support under Linux x86 - run eCos apps natively
   under Linux
 * Config Tool - built-in support for eCos testcase execution
 * Config Tool - memory layout editor, simplifies the task of mapping
   eCos to the target's memory map
 * Enhanced GDB download protocol - halving the download time over
   serial connections

New or extended runtime features:
 * New eCos device driver architecture - including revised serial
   drivers for all supported boards
 * Standardized kernel device driver API
 * ISO C library now includes support for signals and date/time
   functions
 * CygMon ROM monitor support for the SPARClite evaluation boards,
   including ethernet based download and debug
 * Expanded testsuite

In addition to these features the release includes a wealth of minor
refinements, bug fixes, and documentation enhancements.

Contributions:
This release incorporates two major contributions from the net
community. The board port to the Motorola FADS860 board has been
contributed by Kevin Hester, and the Linux synthetic target support
has been contributed by Chris Provenzano. A number of other
contributions have already been accepted and incorporated, and various
bugs reported by the net have been fixed.

Anonymous CVS access:
Cygnus Solutions strongly believes in the benefits of open development
and, to encourage this, it is now possible to obtain the most recent
versions of eCos using anonymous CVS access. This facility provides
immediate access to the latest eCos features and rapid deployment of any
necessary bug fixes.


Visit the home of eCos on the Cygnus sourceware site
http://sourceware.cygnus.com/ecos/ for full downloads, on-line
documentation, mailing lists, FAQ, AnonCVS, and further information.
Further product related information such as brochures, press releases,
etc., can be found on the eCos product web site
http://www.cygnus.com/ecos/

The eCos Team
Cygnus Solutions
http://sourceware.cygnus.com/ecos/

                 reply	other threads:[~1999-05-17  8:56 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=199905171553.QAA14969@sheesh.cygnus.co.uk \
    --to=bartv@cygnus.co.uk \
    --cc=ecos-announce@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).