From: John Dallaway <john@dallaway.org.uk>
To: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: eCos 3.0 beta 1 remaining issues
Date: Fri, 20 Mar 2009 11:31:00 -0000 [thread overview]
Message-ID: <49C37E6E.2030901@dallaway.org.uk> (raw)
eCos maintainers
There are a few issues raised against eCos 3.0 beta 1 which are still open:
http://bugs.ecos.sourceware.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=eCos&version=3.0beta1&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=
This is not a large list and I would like to encourage you all to play a
part in the last push so we can make the final release by the end of
March as intended.
Taking each in turn:
> 1000717 lwIP TCP/IP drops incoming IP packets on SLIP interface
> 1000719 lwip_ppp tests build fails when CYGDBG_LWIP_DEBUG turned on
Can someone step up to look at the above lwIP issues please? Sergei has
provided a patch for one of them. Jifl would be the maintainer with most
experience of lwIP but his availability is limited at present.
> 1000693 flash.c assertion failure
Andrew, can you confirm whether you are able to address 1000693 for eCos
3.0 or whether we should push it out to be fixed later please?
> 1000688 RedBoot GPL message
Jifl, you were intending to tackle 1000688 but it could be addressed by
someone else if necessary. It's probably better for you to focus on the
Thumb compilation issue (1000701). Please do confirm either way whether
you would like someone else to take 1000688.
> 1000689 ompat/posix/current/tests/signal1 hangs
> 1000690 /home/lunn/eCos/work/install/tests/compat/posix/current/tests/signal3 runs forever
POSIX compatibility is important for eCos so we really do need to
determine whether the above POSIX test failures reflect a genuine issue
with the POSIX compatibility layer. These could be tackled by anyone
with experience of POSIX. Please do volunteer.
> 1000701 Error building vectors.S for Thumb on AT91 targets
Jifl has already started looking at 1000701.
> 1000713 RedBoot CDL option hierarchy
1000713 is definitely non-blocking.
> 1000723 Building eCos C library for synthetic target fails with gcc-3.2
Does anyone care about the synthetic target with very old toolchains?
Please shout now if you think 1000723 is important.
> 1000685 isoinfra limits.h breaks with gcc 4.3.3/synth
Andrew has a fix for 1000685.
> 1000707 Multiple is_substr() goals for one CDL item
1000707 will not be addressed in the eCos 3.0 timeframe.
> 1000716 Error launching GDB to run eCos tests
I am looking at 1000716.
> 1000697 ConfigTool: Reset board dialog
1000697 is definitely non-blocking.
Thanks, again, for your support...
John Dallaway
next reply other threads:[~2009-03-20 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 11:31 John Dallaway [this message]
2009-03-25 11:01 ` John Dallaway
2009-03-25 12:22 ` Bart Veer
2009-03-25 13:05 ` John Dallaway
2009-03-25 14:37 ` Bart Veer
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=49C37E6E.2030901@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-maintainers@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).