RTEMS4.7 CVS (was Re: Motorola roadmap)

[Thomas Doerfler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kate,

see:

http://www.rtems.com/cgi-bin/gnatsweb.pl?debug=&database=RTEMS&cmd=view+audit-trail&cmd=view&pr=846

wkr,

Thomas Doerfler.

Kate Feng schrieb:
> Kate Feng wrote:
> 
>> Kate Feng wrote:
>>
>>> This is what Motorola  responded :
>>> "The current roadmap shows the 5500 and the 6100 with the same
>>> life cycle."
>> I forgot to mention that there was a formal presentation about the
>> performance of  RTEMS-MVME5500 BSP at :
>> http://icalepcs2005.web.cern.ch/Icalepcs2005/Presentations/11oct_Tuesday/TU4A/TU4A_1-5O.ppt
>>
>> The associated  paper  is  published at :
>> http://elise.epfl.ch/pdf/O2_011.pdf
>>
> 
> I downloaded the RTEMS4.7 CVS on  Tues., Aug. 1, and found
> out that  on Nov. 3, 2005, the make/custom/mvme5500.cfg  was updated
> so that :
> 
> "CPU_CFLAGS = -mcpu=7450 -Dmpc7455 ......."
> became :
> "CPU_CFLAGS = -mcpu=750 ......"
> 
> May I know why ?  I am not sure if the later  one is OK.   I always
> used the " CPU_CFLAGS = -mcpu=7450 -Dmpc7455 ......".
> 
> Also, The mvme5500 BSP is not up-to-date as the one posted on the web :
> http://www.nsls.bnl.gov/facility/expsys/software/EPICS/
> 
> The  above mentioned paper is based on the RTEMS-4.6.0-MVME5500
> source posted at:
> http://www.nsls.bnl.gov/facility/expsys/software/EPICS/
> The only known bug (cavet : probably due to my not
> up-to-date version of cexp/GeSys) is that :
> 
> /usr/local/source/RTEMS/rtems-4.6.x/cpukit/aclocal/canonicalize-tools.m4.orig
> /usr/local/source/RTEMS/rtems-4.6.x/cpukit/wrapup/Makefile.am.orig
> /usr/local/source/RTEMS/rtems-4.6.x/c/src/wrapup/Makefile.am.orig
> are needed to build the original RTEMS release.
> 
> After  RTEMS is built, then the
> /usr/local/source/RTEMS/rtems-4.6.x/cpukit/aclocal/canonicalize-tools.m4
> /usr/local/source/RTEMS/rtems-4.6.x/cpukit/wrapup/Makefile.am
> /usr/local/source/RTEMS/rtems-4.6.x/c/src/wrapup/Makefile.am
> has to be copied back to build the cexp/GeSys.
> This is documented under synAppsRTEMS/R3.14.6.cexp_patch/patches.
> I will put the warning in a more obvious place on the WEB for rtems-4.6.x.
> 
> However, I do not know if this cavet still applies in RTEMS4.7  because
> I did'nt try it yet.
> 
> Since I have no write permission to the RTEMS4.7CVS, I will
> put up an updated version of RTEMS-MVME5500 BSP for the
> RTEMS4.7 on the
> http://www.nsls.bnl.gov/facility/expsys/software/EPICS/
> 
> Regards,
> Kate
> 


- --
- --------------------------------------------
IMD Ingenieurbuero fuer Microcomputertechnik
Thomas Doerfler           Herbststrasse 8
D-82178 Puchheim          Germany
email:    Thomas.Doerfler at imd-systems.de
PGP public key available at:
     http://www.imd-systems.de/pgpkey_en.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE01/QwHyg4bDtfjQRAhfrAKCZWZieW4ZbfUMlq7F472MQoua93wCfRjJH
6ad4+2OfeaD9rtzoYHxPXxo=
=63VY
-----END PGP SIGNATURE-----