4.7 Branch Status -- TESTING PLEA!!

[Steven Johnson]

Hi Joel,

I have no faults to report on 4.6.99.3 (with my submitted patches), I 
don't think CVS has anything in it that will effect my application.
My target is PowerPC MPC862, custom BSP.  Classic API Only + Networking 
stack seem to work just fine.

Steven J


Joel Sherrill wrote:
> Hi,
>
> I have been running tests and looking at logs this past week.
> I have been repeatedly running the tests on various platforms.
>
> My testing overview:
>
> + SPARC/sis    (gdb):    all sp, tm, psx, and itron look OK
> + SPARC/erc32  (tsim):   spot testing looks OK
> + SPARC/leon2  (tsim):   spot testing looks OK
> + SPARC/leon3  (tsim):   all sp, tm, psx, and itron look OK
> + MIPS/jmr3904 (gdb):    all sp, tm, psx, and itron look OK
> + PowerPC/psim (gdb):    all look ok except for unimplemented
>                          FPU instruction
> + m68k/mcf5206elite (sim): ticker and hello OK
> + i386/pc386   (qemu):    spot checked with network about a week ago
> + arm/edb7312  (skyeye):  no success -- could be operator. :)
>
> I have been updating the Wiki with status reports as I go but
> may not be 100% up to date. 
>
> PLEASE PLEASE TEST!!! As far as I can tell, the 4.7.0 release
> is going to put cut as soon as I can tidy things up.
>
> Reports are needed.  Looking back in the Wiki, it was nice to
> see others are updating the BSP status to indicate when it was
> last tested.  If a report is not against a release version
> but against CVS please indicate branch and date.
>
> --joel
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.com
> http://rtems.rtems.org/mailman/listinfo/rtems-users
>
>
>
> __________________________________________________________
> Message transport security by GatewayDefender.com
> 6:28:54 PM ET - 11/17/2006
>
>
>