Messages in this thread | | | Date | Thu, 6 Oct 2011 15:30:19 -0700 | Subject | MODULE_LICENSE("GPL") not working for me | From | Stephen Williams <> |
| |
I have some large drivers for use in embedded arm systems, and I want them to be GPL, because I want to use some symbols exported as GPL, and also because I just wanna. But it is not working for me. I've attached my Makefile. I'm building from outside the kernel tree, but that should be OK. (right?) I'm using the following script to actually build:
SE0=/home/u/wing/steve/picturel/SE0 CROSS_COMPILE=/opt/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- export CROSS_COMPILE make KERNELDIR=$SE0/linux-2.6.33-quatro ARCH=arm modules
But no matter what I do, when I try to load my module, I get errors line this:
# insmod ./vidfor2.ko vidfor: module license 'unspecified' taints kernel. Disabling lock debugging due to kernel taint vidfor: Unknown symbol driver_remove_file vidfor: Unknown symbol driver_create_file insmod: can't insert './vidfor2.ko': unknown symbol in module or invalid parameter
I have a MODULE_LICENSE("GPL"); line in the "linux.c" source file, and the pertinent parts of the makefile are here:
OBJ := linux.o ops.o console.o sysfs.o ident_tables.o LIBOBJ := vidforio.o init.o format.o video.o isr.o version.o
ifneq ($(KERNELRELEASE),)
EXTRA_CFLAGS += -I$(M)/../libvidforio obj-m += vidfor.o vidfor-objs := $(OBJ) $(patsubst %,../libvidforio/%,$(LIBOBJ))
else [...]
What's the trick for getting the MODULE_LICENSE successfully stamped into my generated .ko file?
I've googled the list and the internet in general, and found as many relevant examples as I could in the kernel source, but I'm at wit's end. I'm not subscribed, so please CC responses, although I will check back often.
-- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." [unhandled content-type:application/octet-stream] | |