On Fri, Aug 24, 2007 at 10:06:28AM +0200, Carsten Schlote wrote: > Yes, indeed. But with the latest GCC version on SVN trunk there should > some usable support for v4e cores now :-) Just another good reason to > put the mcf548x into consideration for our next platform. As an > long-yeared m68k/coldfire fan, I would really like to do some work > with this core.
Hmm, I'm not sure. m68k is a niche port of Linux, and you will for example probably not get features like NPTL and RT-Preempt for it. > I agree. Probably it's best to use the latest official 4.2.1 GCC > version and apply some hand-generated monster patch to the latest > trunk version. At least this would fit best into the ptxdist > framework. Yes. And it would make it easy to throw away that monster patch once the next revision is out which supports m68k. > > > GLibC Ports 2.6.1 seems to support these latest GCC improvements > > > already. > > > > Good start. > > I hope it's not just vapor code :-) Usually not. Since the codesourcery people took over port maintenance, there is substance behind it. > I would also like to create some updated configs for ARM, MIPS etc > using GCC 4.2.1 and glibc 2.6.1. Just to keep the OSELAS toolchains as > much up-to-date as possible. Yes, some help in this area would be pretty good. We'd like to do some updating, but testing takes quite some time and we have so much customer projects at the moment that there's not that much time for technology. > > If you want to, please send me an encrypted mail with your > > favourite svn password. > > I will do. I first need to setup my gpg stuff at company. Great! Robert -- Pengutronix - Linux Solutions for Science and Industry Entwicklungszentrum Nord http://www.pengutronix.de -- ptxdist mailing list [email protected]
