LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-embedded@ozlabs.org
Cc: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Subject: Re: ARCH=ppc vs ARCH=powerpc
Date: Mon, 9 Jul 2007 02:34:14 +0200	[thread overview]
Message-ID: <200707090234.14851.arnd@arndb.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0707061706140.4792@mtfhpc.demon.co.uk>

On Friday 06 July 2007, Mark Fortescue wrote:
> 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.

The one thing that is holding up the transition to arch/powerpc is lack
of people with access to the respective boards. If you have one board
that you care about, it would be good if you look into getting it moved
over. Tell us if you have problems doing so. It shouldn't be all that
hard any more, and if it is, maybe some documentation is missing.

> 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).

You should simply install the headers with ARCH=powerc, even when the
kernel is built with ARCH=ppc. From the user space point of view, there
is only one set of headers.

	Arnd <><

  reply	other threads:[~2007-07-09  0:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 16:21 ARCH=ppc vs ARCH=powerpc Mark Fortescue
2007-07-09  0:34 ` Arnd Bergmann [this message]
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=200707090234.14851.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mark@mtfhpc.demon.co.uk \
    /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