On Thu, 27 Oct 2005, Andrew Lunn wrote:
eCos 2.0 is very old, something like 3 years.
The problem you are having was fixed a couple of years ago. Update to
the latest code.
Umm, this does bring to mind... What is the release cycle for eCos? It
would seem following the general drift of queries and answers of late
(it's been fixed, it's in CVS), that at very least a eCos version 2.1 is
needed.
Traditionally one doesn't use code from the tip of CVS mainline in
production software because enhancements have destabilized it and
have introduced a rash of new bugs.
Is the answer then that no new enhancements have gone in in the last three
years?
One of the things that have always concerned me about eCos is the C bit.
Configurable. How on earth do you test whether each and every possible
configuration still works?
Perhaps an eCos release process needs a lot of community involvement. ie.
several release candidates made and all users requested to give it try in
the configuration they use. ie. Rather than attempting test coverage of
all possible configurations, at least get coverage of all existing usages.
I'm also sure there exist patches and bug fixes on peoples disks that the
announcement of a forthcoming release may shake loose.
John Carter Phone : (64)(3) 358 6639
Tait Electronics Fax : (64)(3) 359 4632
PO Box 1645 Christchurch Email : [EMAIL PROTECTED]
New Zealand
Carter's Clarification of Murphy's Law.
"Things only ever go right so that they may go more spectacularly wrong later."
From this principle, all of life and physics may be deduced.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
