Re: a problem of kernel-module version mismatch.

On Thursday 08 June 2006 15:52, Ming Liu wrote:

quoted

The easiest way is usually to put the driver in your source tree
and compile everything together. That also makes it easier to
distribute the complete source tree to your users.

=20
Sorry that I am a novice in Linux. I don't know how can I put the driver =

in=20

my source tree and compile everything together. It looks like that there =

is=20

no option in the menuconfig to choose a specially customed peripheral. So=

 I=20

think I only can include the customed peripheral as a module. Could you=20
please say in a detail on how to do that?=20

The most simple way would be to put it into linux/drivers/misc and add it
to the Makefile in there.

quoted

quoted

insmod: unresolved symbol XIo_In32
insmod: unresolved symbol XIO_Out32

that looks like part of your module is missing. Try to find where thses
functions are defined in there and why that isn't compiled.

=20
It's very strange because I have checked the source. In the header file o=

f=20

xio.h, there are the following sentences,
=20
/************************** Function Prototypes=20
******************************/
=20
/* The following functions allow the software to be transportable across
=A0* processors which may use memory mapped I/O or I/O which is mapped in=

to a

=A0* seperate address space such as X86. =A0The functions are better suit=

ed for

=A0* debugging and are therefore the default implementation. Macros can=20
instead
=A0* be used if USE_IO_MACROS is defined.
=A0*/
#ifndef USE_IO_MACROS

The comment tells you that you either need to implement these functions
youself or #define USE_IO_MACROS in the code before this.

/* Functions */
Xuint8 XIo_In8(XIo_Address InAddress);
Xuint16 XIo_In16(XIo_Address InAddress);
Xuint32 XIo_In32(XIo_Address InAddress);
=20
void XIo_Out8(XIo_Address OutAddress, Xuint8 Value);
void XIo_Out16(XIo_Address OutAddress, Xuint16 Value);
void XIo_Out32(XIo_Address OutAddress, Xuint32 Value);
=20
#else
=20
/* The following macros allow optimized I/O operations for memory mapped=

=20

I/O
=A0* Note that the SYNCHRONIZE_IO may be moved by the compiler during
=A0* optimization.
=A0*/
=20
#define XIo_In8(InputPtr) =A0(*(volatile Xuint8 =A0*)(InputPtr));=20
SYNCHRONIZE_IO;
#define XIo_In16(InputPtr) (*(volatile Xuint16 *)(InputPtr));=20
SYNCHRONIZE_IO;
#define XIo_In32(InputPtr) (*(volatile Xuint32 *)(InputPtr));=20
SYNCHRONIZE_IO;
=20
#define XIo_Out8(OutputPtr, Value) =A0\
=A0 =A0 { (*(volatile Xuint8 =A0*)(OutputPtr) =3D Value); SYNCHRONIZE_IO;=

 }

#define XIo_Out16(OutputPtr, Value) \
=A0 =A0 { (*(volatile Xuint16 *)(OutputPtr) =3D Value); SYNCHRONIZE_IO; }
#define XIo_Out32(OutputPtr, Value) \
=A0 =A0 { (*(volatile Xuint32 *)(OutputPtr) =3D Value); SYNCHRONIZE_IO; }
=20
#endif

These macros are probably broken on powerpc.

=20
I think these are the defination of XIo_In32 and XIo_Out32. Also, during=

=20

the compilation, there is no error to complain that "XIo_In32 or XIo_Out3=

2=20

undeclared".=20
=20

I would suggest you remove that part of the header file completely, and
replace it with:

#define XIo_In32(p) in_le32(x)
#define XIO_Out32(p,v) out_le32(p, v)

	Arnd <><