From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from anchor-post-36.mail.demon.net (anchor-post-36.mail.demon.net [194.217.242.86]) by ozlabs.org (Postfix) with ESMTP id 8375ADE044 for ; Sat, 7 Jul 2007 05:08:04 +1000 (EST) Received: from mtfhpc.demon.co.uk ([83.104.139.140]) by anchor-post-36.mail.demon.net with esmtp (Exim 4.42) id 1I6qYd-0004nN-KQ for linuxppc-embedded@ozlabs.org; Fri, 06 Jul 2007 16:21:23 +0000 Received: from localhost (mark@localhost) by mtfhpc.demon.co.uk (8.9.3/8.9.3) with ESMTP id RAA04820 for ; Fri, 6 Jul 2007 17:21:22 +0100 Date: Fri, 6 Jul 2007 17:21:21 +0100 (BST) From: Mark Fortescue To: linuxppc-embedded@ozlabs.org Subject: ARCH=ppc vs ARCH=powerpc Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, I have noticed and read a few comments regarding the demise of ARCH=ppc. Having two PowerPC arcitectures and only supprting one of them makes little sense. Is it not time to migrate (where required) the remaining code from arch/ppc to arch/powerpc and asm-ppc to asm-powerpc. There are not many files left that are unique to ARCH=ppc so it should not take too long. For me, the requirement is to keep support for the cards indicated in arch/ppc/config/xxx_defconfig (as I have one that I might what to use with linux) in the same way as they are supported in ARCH=ppc. I have just made some tweeks to get ARCH=ppc building for me but I still need to sort out what is required to get around *** Error: Headers not exportable for this architecture (ppc). Regards Mark Fortescue.