Re: [microblaze-uclinux] Problem using insmod

[Alfred Grünewald <info@xxxxxxxxxxxxxx>]

Hi John,

Alfred Grünewald wrote:

>> module, but when I try to
>> load it I get the following:
> /> insmod xilinx_gpio
>> Using /lib/modules/2.4.24-uc0/kernel/drivers/char/xilinx_gpio.o
>> insmod: unresolved symbol misc_deregister
>> insmod: unresolved symbol kmalloc
>> insmod: unresolved symbol XAssert
>> insmod: unresolved symbol XAssertStatus
>> insmod: unresolved symbol misc_register
>> insmod: unresolved symbol printk

John Williams wrote:

>First of all, in the kernel config where you enable loadable modules,
>use the settings below:

>[*] Enable loadable module support
>[ ]   Set version information on all module symbols
>[ ]   Kernel module loader

>Also, try applying the attach patch, from the linux-2.4.x directory,
>with "patch -p0 < jw-modules.patch"

>Try this and let me know.

In menuconfig I cleared my settings of  [] Set version .. and [] Kernel
modul loader and applied the patch.
Loading of the gpio module now works fine!

Thanks for the fast help!

Cheers

Alfred

----- Original Message -----
From: "John Williams" <jwilliams@itee.uq.edu.au>
To: <microblaze-uclinux@itee.uq.edu.au>
Sent: Wednesday, July 14, 2004 12:07 PM
Subject: Re: [microblaze-uclinux] Problem using insmod


Hi Alfred,

Alfred Grünewald wrote:

> I applied your patch for module loading and defined gpio as loadable
> module, but when I try to
> load it I get the following:
>
> /> insmod xilinx_gpio
> Using /lib/modules/2.4.24-uc0/kernel/drivers/char/xilinx_gpio.o
> insmod: unresolved symbol misc_deregister
> insmod: unresolved symbol kmalloc
> insmod: unresolved symbol XAssert
> insmod: unresolved symbol XAssertStatus
> insmod: unresolved symbol misc_register
> insmod: unresolved symbol printk

First of all, in the kernel config where you enable loadable modules,
use the settings below:

[*] Enable loadable module support
[ ]   Set version information on all module symbols
[ ]   Kernel module loader

Also, try applying the attach patch, from the linux-2.4.x directory,
with "patch -p0 < jw-modules.patch"

Try this and let me know.

Cheers,

John



----------------------------------------------------------------------------
----


> Index: arch/microblaze/xilinx_ocp/xbasic_types.c
> ===================================================================
> RCS file:
/var/cvs/uClinux-2.4.x/arch/microblaze/xilinx_ocp/xbasic_types.c,v
> retrieving revision 1.1
> diff -u -b -B -w -p -r1.1 xbasic_types.c
> --- arch/microblaze/xilinx_ocp/xbasic_types.c 6 Aug 2003 00:34:47 -0000
1.1
> +++ arch/microblaze/xilinx_ocp/xbasic_types.c 14 Jul 2004 09:57:02 -0000
> @@ -65,6 +65,9 @@
>   */
>  unsigned int XAssertStatus;
>
> +EXPORT_SYMBOL_NOVERS(XAssertStatus);
> +EXPORT_SYMBOL_NOVERS(XAssert);
> +
>  /**
>   * This variable allows the assert functionality to be changed for
testing
>   * such that it does not wait infinitely. Use the debugger to disable the
>

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/