All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-embedded@ozlabs.org, paul@mad-scientist.us
Subject: Re: 2.6.25: include/asm-ppc vs. include/asm-powerpc
Date: Thu, 28 Aug 2008 16:42:26 +0200	[thread overview]
Message-ID: <200808281642.26647.arnd@arndb.de> (raw)
In-Reply-To: <1219933848.16802.96.camel@homebase.localnet>

On Thursday 28 August 2008, Paul Smith wrote:
> On Thu, 2008-08-28 at 15:53 +0200, Arnd Bergmann wrote:
> > The easiest solution should be to just include all your modules in
> > the kernel source as patches, rather than building them externally.
> > 
> > That will give you access to all the headers you need.
> 
> It doesn't matter whether I build my code in the kernel as patches, or
> not.  The problem is not that I don't have the headers handy, it's that
> they simply don't exist in asm-ppc anymore, not even in the linux source
> tree.

The trick that arch/ppc uses is to create a symlink arch/ppc/include/asm
pointing to include/asm-powerpc and then passing "-Iinclude
 -Iarch/ppc/include" to the compiler. This will make gcc look for
headers in asm-ppc first, and then in asm-powerpc.

It should also work with external modules if you build them in the
recommended way (see http://lwn.net/Articles/80250/), but as I said,
the easiest way is to just build all modules as part of the regular
kernel build. It should be evident that building kernel code actually
works and gets the right header files for all existing modules, so
it should work just like that for any drivers you add to the kernel.

	Arnd <><

  parent reply	other threads:[~2008-08-28 14:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 13:07 2.6.25: include/asm-ppc vs. include/asm-powerpc Paul Smith
2008-08-28 13:53 ` Arnd Bergmann
2008-08-28 14:30   ` Paul Smith
2008-08-28 14:38     ` Josh Boyer
2008-08-28 14:42     ` Arnd Bergmann [this message]
2008-08-28 16:01       ` Paul Smith
2008-08-28 18:07       ` Paul Smith
2008-08-28 14:48     ` Roland Dreier
2008-08-28 13:56 ` Darcy Watkins

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=200808281642.26647.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=paul@mad-scientist.us \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.