* Guillem Jover | 2010-04-30 06:10:05 [+0200]: >Hi! Hi Guillem,
>On Thu, 2010-04-29 at 21:09:20 -0500, Moffett, Kyle D wrote: >> I believe we have consensus on the port architecture name of "powerpcspe". >> Is there any chance we can get the attached patch merged soon? I'd like to >> move forward with getting an unofficial debian-ports.org repository created >> and they won't do that until a patch has been merged to upstream dpkg GIT. > >It didn't seem clear to me the double issue had consensus, if it does, >and both of you agree (Sebastian a Signed-off-by from you in this case >would be nice), then yes, I'll gladly add the new architecture. Yes, double precision is what we want, so here you go: Signed-off-by: Sebastian Andrzej Siewior <[email protected]> >> From: Kyle Moffett <[email protected]> >> Date: Thu, 29 Apr 2010 21:47:25 -0400 >> Subject: [PATCH] powerpcspe: New unofficial Debian port > >> The Debian port to this architecture specifically chooses to optimize >> for the higher-end chips (e500v2), as most of the others are targeted at >> automotive applications or no longer in production. > >Do both of you agree on this too? Yes, e500v2 is the way to go. MPC8540 (e500v1) is still in production. The designs on the hand are not that attractive these days. The reference manual was released 9/8/2004 and the flash or system memory back then was not that huge like we have it today. They have also no storage controler in-core. Also you don't want a HD in your automotive product. And if you don't need the PCI bus, you are going to remove it. So it is unlike they will run *full* Debian (now). Most likely they will cross compile the few application they need. Today one will pick a newer CPU. >> The specific GNU triplet for this arch is "powerpc-linux-gnuspe". Like >> the ARM EABI port (arm-linux-gnueabi) the naming seems unfortunate here; >> an architecture triplet such as "powerpcspe-linux-gnu" would have been >> far more appropriate. As a result, we end up adding an extra "ostable" >> entry instead of one in "cputable". > >This is just nitpicking, but in this case I think the GNU triplet is >appropriate for those two ports, as the matter of conflict is mostly ABI >dependent. > >thanks, >guillem Sebastian -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
