From: Paul Smith <paul@mad-scientist.us>
To: linuxppc-embedded@ozlabs.org
Subject: 2.6.25: include/asm-ppc vs. include/asm-powerpc
Date: Thu, 28 Aug 2008 09:07:44 -0400 [thread overview]
Message-ID: <1219928864.16802.69.camel@homebase.localnet> (raw)
I know that arch/ppc is obsolete in 2.6.26 and deprecated for earlier
releases. However, I have a port to a custom PPC-based board that was
originally done for 2.6.14 in arch/ppc, and I've ported it to our
current "standard" kernel of 26.25 and it works (anyway it boots etc.)
I absolutely do not have time now, and not for a few months, to convert
over to live in arch/powerpc (BTW, if anyone has any pointers to docs on
ways to make that transition I'm very interested).
My problem is this: I'm having trouble building some of our externel
kernel modules because they can't find various kernel header files.
Looking at the kernel's include directory I see that include/asm is
symlinked to include/asm-ppc which is what I would expect for ARCH=ppc,
and the same way it used to work in 2.6.14.
However, looking in the include/asm-ppc directory I see that many of the
files that used to be there are not there anymore... although they do
appear in include/asm-powerpc. In particular I'm interested in
ppc_asm.h which used to exist in both asm-ppc64 AND in asm-ppc, but now
only exists in asm-powerpc. What's the approved way to include this
header if asm points to asm-ppc?
In general it seems like lots of headers that used to be in both asm
directories now appear in only asm-powerpc; I don't really see how this
is supposed to work. Any tips on this would be most welcome.
Thanks!
next reply other threads:[~2008-08-28 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 13:07 Paul Smith [this message]
2008-08-28 13:53 ` 2.6.25: include/asm-ppc vs. include/asm-powerpc Arnd Bergmann
2008-08-28 14:30 ` Paul Smith
2008-08-28 14:38 ` Josh Boyer
2008-08-28 14:42 ` Arnd Bergmann
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=1219928864.16802.69.camel@homebase.localnet \
--to=paul@mad-scientist.us \
--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