On Fri, Jul 16, 2010 at 2:15 PM, Mulyadi Santosa
<mulyadi.santosa@xxxxxxxxx> wrote:
> Hi...
>
> On Fri, Jul 16, 2010 at 21:53, Bob Beers <bob.beers@xxxxxxxxx> wrote:
>> How do I figure out where to fix it?
>
> Could it be due to custom linker script used in your driver code?
Hmmm, It looks lilke a pretty standard Makefile:
-----------------------8<-------------------
CC=gcc
VER=`uname -r`
SRCREF?=/lib/modules/$(VER)/build
INSTALLDIR=/lib/modules/$(VER)/kernel/net
obj-m = sbe2t3e3.o
sbe2t3e3-objs = ossiRelease.o linux_sbe2t3e3.o linux_sysdep.o
linux_sbe2t3e3_device.o if_sbe2T3E3_CPLD.o if_sbe2T3E3_intr.o
if_sbe2T3E3_ctrl.o if_sbe2T3E3_IO.o if_sbe2T3E3_21143.o
if_sbe2T3E3_Exar7250.o if_sbe2T3E3.o if_sbe2T3E3_Exar7300.o
build:
make -C $(SRCREF) M=`pwd`
build-sparse:
make C=1 -C $(SRCREF) M=`pwd`
install:
-mkdir -p $(INSTALLDIR)
cp sbe2t3e3.ko $(INSTALLDIR)
clean:
rm -rf *.ko *.o *.mod.c
-----------------------8<-------------------
Where might this custom linker script be lurking?
Thanks,
-Bob Beers
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
