Messages in this thread | | | Subject | RE: module name is KBUILD_MODNAME | Date | Wed, 21 Jul 2004 10:05:33 +0200 | From | "Idan Spektor" <> |
| |
Here is the makefile I am using to create the .ko object. Please notice that I compile my objects by myself in a different makefile and only then use the kbuild infrastructure. If kbuild is adding the name as part of the module object and not the header object then that might be the problem. However, it is difficult for me to use the kbuild infrastructure for the whole build as it contains many files in different directories.
makefile:
ifeq ($(KERNELRELEASE),)
PWD := /home/idan/my_module KDIR := /usr/src/linux-$(shell uname -r)/
default: $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
else
obj-m := my_module.o my_module-objs := my_module_main.o
$(PWD)/my_module_main.o: echo do nothing
endif
idan
-----Original Message----- From: sam@ravnborg.org [mailto:sam@ravnborg.org] Sent: Tuesday, July 20, 2004 9:17 PM To: Idan Spektor Cc: linux-kernel@vger.kernel.org Subject: Re: module name is KBUILD_MODNAME
On Tue, Jul 20, 2004 at 05:36:01PM +0200, Idan Spektor wrote: > Hi All, > I am migrating my loadable module to work with the 2.6 kernel. > I have actually managed to make everything working except for > one thing. When I am loading my module (using the new > modprobe), its name, as appearing in lsmod, is KBUILD_MODNAME instead > of the module's real name. What am I missing? Is there > a define for the module's name that I should add somewhere?
For a start could you post the Makefile you use to build the module? I assume you use the kbuild infrastructure?
Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |