LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Stevens <jsteve17@yahoo.com>
To: linuxppc-embedded@ozlabs.org
Subject: Compilation Error
Date: Tue, 11 Oct 2005 12:51:18 -0700 (PDT)	[thread overview]
Message-ID: <20051011195118.26463.qmail@web33413.mail.mud.yahoo.com> (raw)

I am trying to cross compile one of our drivers at
work to run on both an AMCC 440SP platform (Luan2),
and an MPC8540 platform (MPC8540ADS).  I am using the
ELDK compilers (ppc_4xx-gcc and ppc_85xx-gcc), and the
kernel.org 2.6.13 source.  I was getting warnings
about implicit declarations for both dma_cache_wback
and dma_cache_inv.  I went ahead and replaced them
with clean_dcache_range and invalidate_dcache_range
(since that is what they are #defined to), and
included cache.h.  So then I was able to get through
the compilation without the implicit declaration
warnings, but now when it does MODPOST, I get warnings
about clean_dcache_range and invalidate_dcache_range
being undefined!  This driver was originally written
for x86 platforms where dma_cache_wback and
dma_cache_inv both are #defined to inline funtions
within io.h.  Has anyone else seen this?  I'm sure
it's most likely an include issue, but I'm not sure
what else to include.  I have tried dma-mapping.h and
cache.h?  Any help would be greatly appreciated. 
Also, if this is the wrong place for this post, what
is the correct place for this question?

Thanks,
   Jeff Stevens


	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

             reply	other threads:[~2005-10-11 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11 19:51 Jeff Stevens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-23 11:53 Compilation Error Prabhat_Singh
2005-07-25  7:16 Compilation error Susheel Raj

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=20051011195118.26463.qmail@web33413.mail.mud.yahoo.com \
    --to=jsteve17@yahoo.com \
    --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