All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juliana Su <js084@bucknell.edu>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: insmod: unresolved symbol XIo_In32/XIo_Out32
Date: Sat, 12 Jul 2008 15:22:18 -0400	[thread overview]
Message-ID: <4879046A.1020508@bucknell.edu> (raw)
In-Reply-To: <20080711210514.GB18239@secretlab.ca>

Hi again,

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? 
Thanks again for your help!


-Juliana


Grant Likely wrote:
> On Fri, Jul 11, 2008 at 03:11:06PM -0400, Juliana Su wrote:
>   
>> Hi,
>>
>> Thanks for your reply! I am new to creating loadable kernel modules, so  
>> I hope you do not mind some more questions... How can I get the XIo_*  
>> helper routines to compile into the kernel or export them with  
>> EXPORT_SYMBOL( )? In my c file (my driver file from which I create the  
>> object file), I made sure to include xio.h, which is where XIo_In32 and  
>> XIo_Out32 are defined (see below section from xio.h).
>>     
>
> Add an EXPORT_SYMBOL() line to the location where the io accessors are
> implemented.  However, you'd probably be better just to replace xio.h
> implementation with macros that just map them to the in_be32() and
> out_be32() macros.
>
> g.
>
>   

  reply	other threads:[~2008-07-12 19:22 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 [this message]
2008-07-13  7:30         ` Joachim Foerster

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=4879046A.1020508@bucknell.edu \
    --to=js084@bucknell.edu \
    --cc=grant.likely@secretlab.ca \
    --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 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.