From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: ecos-maintainers@sources.redhat.com
Subject: Re: Proposal for processing patches for the eCos 2.0 branch
Date: Sat, 12 Apr 2003 05:00:00 -0000 [thread overview]
Message-ID: <3E979D68.1000903@eCosCentric.com> (raw)
In-Reply-To: <20030318185613.GE17373@biferten.ma.tech.ascom.ch>
Andrew Lunn wrote:
>John Dallaway wrote:
>>There is still quite a bit of work to be done on the configtool
>>for 2.0 final so we might consider excepting configtool code from this
>>process.
>
>
> Please could you elaborate on the configtool issues.
>
> I used it yesterday for the first time to do the requested testing of
> 2.0b1. I ran into problems running the test cases. Quite a few times
> it did not detect when the test case had finished. I also had gdb
> protocol errors with signal4. Running the tests by hand worked
> fine. Are these known issues? Do i need to create bugzilla entries?
I don't think I ever saw a reply to this, so if this is still reproducable
with a snapshot from http://www.ecoscentric.com/devzone/configtool.shtml
then bugzilla it.
> The testing of AFE1 passed. I used the HAL from 1.5.2 since this is
> not in 2.0b1. I then tried to put Redboot in the boot block rather
> than using ascom's POST as the boot block and killed the board :-(
> This is probably my error in building the image since its not a normal
> setup. Time to find a JTAG programmer.
Glad AFE sorta worked, and hope you got it sorted!
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
next prev parent reply other threads:[~2003-04-12 5:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 8:47 Patches " John Dallaway
2003-03-18 13:48 ` Gary Thomas
2003-03-18 16:04 ` Proposal for processing patches " John Dallaway
2003-03-18 17:25 ` Jonathan Larmour
2003-03-18 18:21 ` Nick Garnett
2003-03-18 18:56 ` Andrew Lunn
2003-04-12 5:00 ` Jonathan Larmour [this message]
2003-04-14 7:28 ` Andrew Lunn
2003-03-18 19:01 ` Andrew Lunn
2003-03-18 22:58 ` Jonathan Larmour
2003-03-18 19:16 ` SNMP for FreeBSD Andrew Lunn
2003-03-19 13:22 ` Jonathan Larmour
2003-03-19 14:23 ` Gary Thomas
2003-03-19 18:07 ` Nick Garnett
2003-03-25 17:01 ` Andrew Lunn
2003-03-19 14:22 ` 2.0 branch: mn10300 debug info patch Bart Veer
2003-03-19 14:40 ` John Dallaway
2003-03-19 18:07 ` Nick Garnett
2003-03-18 18:09 ` Patches for the eCos 2.0 branch Nick Garnett
2003-03-18 18:25 ` Gary Thomas
2003-03-18 19:05 ` Nick Garnett
2003-03-18 19:13 ` Gary Thomas
2003-03-19 10:18 ` New CPM/DPRAM allocator John Dallaway
2003-03-19 13:02 ` Nick Garnett
2003-03-19 14:38 ` Gary Thomas
2003-03-19 15:44 ` John Dallaway
2003-03-19 17:06 ` Gary Thomas
2003-03-19 18:22 ` Nick Garnett
2003-03-19 18:26 ` Gary Thomas
2003-03-19 18:52 ` Nick Garnett
[not found] ` <1048100525.7462.5617.camel@hermes.chez-thomas.org>
2003-03-19 19:21 ` Nick Garnett
2003-03-20 13:02 ` Nick Garnett
2003-03-20 13:14 ` Gary Thomas
2003-03-20 18:11 ` Nick Garnett
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=3E979D68.1000903@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@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).