Proposal for processing patches for the eCos 2.0 branch

[Andrew Lunn]

> The above procedure should be adopted for all target side code in the branch 
> at minimum. 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?

      Andrew

PS 

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.