From: Mark Fortescue <mark@mtfhpc.demon.co.uk>
To: linuxppc-embedded@ozlabs.org
Subject: ARCH=ppc vs ARCH=powerpc
Date: Fri, 6 Jul 2007 17:21:21 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0707061706140.4792@mtfhpc.demon.co.uk> (raw)
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.
next reply other threads:[~2007-07-06 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 16:21 Mark Fortescue [this message]
2007-07-09 0:34 ` ARCH=ppc vs ARCH=powerpc Arnd Bergmann
2007-07-09 3:37 ` Josh Boyer
2007-07-09 14:33 ` Mark Fortescue
2007-07-09 3:38 ` Josh Boyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.61.0707061706140.4792@mtfhpc.demon.co.uk \
--to=mark@mtfhpc.demon.co.uk \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox