linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joachim Foerster <mls.JOFT@gmx.de>
To: Juliana Su <js084@bucknell.edu>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: insmod: unresolved symbol XIo_In32/XIo_Out32
Date: Sun, 13 Jul 2008 09:30:15 +0200	[thread overview]
Message-ID: <1215934215.2770.8.camel@md40100b.ft> (raw)
In-Reply-To: <4879046A.1020508@bucknell.edu>

Hi,

On Sat, 2008-07-12 at 15:22 -0400, Juliana Su wrote:
> Ok, so I tried mapping to in_be32( ) and out_be32( ) by changing:
> 
> #define XIo_In32(InputPtr) (*(volatile u32 *)(InputPtr)); SYNCHRONIZE_IO; 
> to
> #define XIo_In32(InputPtr) in_be32(InputPtr)
> 
> and
> 
> #define XIo_Out32(OutputPtr, Value) \
>    { (*(volatile u32 *)(OutputPtr) = Value); SYNCHRONIZE_IO; }
> to
> #define XIo_Out32(OutputPtr, Value) out_be32(OutputPtr, Value)
> 
> I made sure to include asm-ppc/io.h, too. However, I still get the same 
> unresolved symbol error message... Did I do the mapping correctly? 

Hmmm, as Grant already said, you need to replace the _implementation_
(the actual function) by macros. You replaced a #define with another
#define - and a #define is not a symbol (for the compiler, only for
cpp). So - without knowing anything about your MontaVista Linux sources
- I think that the #defines you replaced are _not_ used, instead there
have to be some function _definition_ (in xio.h) you need to replace.

As an example: Xilinx also has a xio.h in their git tree. There one
would have to replace lines 167..173 in
http://git.xilinx.com/cgi-bin/gitweb.cgi?p=linux-2.6-xlnx.git;a=blob;f=drivers/xilinx_common/xio.h;h=7b22a677bbf7769d8698d37397f2174a2cd7e2b2;hb=HEAD

 Joachim

      reply	other threads:[~2008-07-13  7:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11 14:26 insmod: unresolved symbol XIo_In32/XIo_Out32 Juliana Su
2008-07-11 18:31 ` Grant Likely
2008-07-11 19:11   ` Juliana Su
2008-07-11 21:05     ` Grant Likely
2008-07-12 19:22       ` Juliana Su
2008-07-13  7:30         ` Joachim Foerster [this message]

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=1215934215.2770.8.camel@md40100b.ft \
    --to=mls.joft@gmx.de \
    --cc=js084@bucknell.edu \
    --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;
as well as URLs for NNTP newsgroup(s).