public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] eCos 3.0 beta 1 now available for download
Date: Sun, 22 Feb 2009 08:16:00 -0000	[thread overview]
Message-ID: <49A109B7.8020502@dallaway.org.uk> (raw)

eCos community

On behalf of the eCos maintainers, I am pleased to announce that the
eCos 3.0 beta 1 release is now available for download. This release is
intended for testing by all eCos developers and incorporates many
contributions to the public eCos project which have been previously
available via the CVS repository only. These contributions include:

  * Cortex-M, FR30 and 68K/ColdFire architectural ports
  * CAN, I2C, SPI, Framebuffer, disk and ADC infrastructure
  * Enhanced Flash infrastructure (flash v2)
  * FAT filesystem
  * IPsec, PPP, SNTP client, VNC server, and enhanced HTTP server for
    FreeBSD TCP/IP stack
  * lwIP lightweight TCP/IP stack
  * USB serial function driver
  * Object loader
  * HAL and driver packages for many new processor variants, target
    platforms and peripheral devices

eCos 3.0 beta 1 also includes updated eCos configuration tools which
extend host platform coverage to GTK+ 2.x on Linux and to Windows Vista.

We need your help in testing this beta release on a wide variety of
hardware platforms. To this end, we have prepared a set of testing
guidelines to assist you in providing the feedback we need:

  http://ecos.sourceware.org/testing.html

I would particularly encourage eCos developers who have contributed
target platform support in the past to test the new release with their
contributed platform HAL and verify that there are no regressions.

For testing purposes, eCos 3.0 beta 1 should be used in conjunction with
the latest eCos toolchains based on GCC 4.3.2 wherever possible.
Pre-built versions of these toolchains are available for many of the
popular target architectures (contributed by eCosCentric).

We plan to keep the beta testing period short with a view to generating
the eCos 3.0 final release next month (March 2009).

Both eCos and the pre-built toolchains may be downloaded and installed
by following the instructions provided at:

  http://ecos.sourceware.org/getstart.html

Following installation, please refer to the release notes at
ecos-3.0b1/README.txt for details of known issues in this release.

Thank you for your on-going support of eCos.

John Dallaway
eCos 3.0 release manager

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2009-02-22  8:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22  8:16 John Dallaway [this message]
2009-02-23  5:43 ` [ECOS] " vibisreenivasan
2009-02-23  7:51   ` John Dallaway
2009-02-23  9:41     ` vibisreenivasan
2009-02-23 10:04       ` [ECOS] Bug reporting [ was Re: eCos 3.0 beta 1 now available for download ] John Dallaway
2009-02-24 15:45 ` [ECOS] eCos 3.0 beta 1 now available for download Rutger Hofman
2009-02-25 15:33   ` [ECOS] " John Dallaway
2009-02-26 10:51 ` [ECOS] " Ilija Kocho
2009-02-26 11:56   ` John Dallaway
2009-02-27 16:44     ` Ilija Kocho
2009-02-26 11:59   ` Sergei Gavrikov
2009-02-26 12:15     ` Sergei Gavrikov

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=49A109B7.8020502@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).