Hi,
Yes, as you said I have more than one source in "/usr/src". I had
specified the exact source in the MakeFile. Following is the Makefile
of the Geode v4l2 driver source. Is there any problem with CFLAGS
declared here ?
CC=gcc
CFLAGS += -D__KERNEL__ -DMODULE
CFLAGS += -DCYGNUS -Dlinux -DOS_LINUX -DLINUX -Wall -O2 -I./durango
-I./tvlib -I./VidLib
CFLAGS += -DSIGNAL_USER
CFLAGS += -DFREQ_IS_CHANNEL
#CFLAGS += -DSIGMA_DIRECT
#CFLAGS += -DCYGNUS_PAL_TUNER
CFLAGS += -DXPRESSROM
CFLAGS += -DUSE_SYSTEM_I2C
#CFLAGS += -DNO_DECODER
#CFLAGS += -DEXCLUDE_TUNER
CFLAGS += -DVBI_IN_FB
#CFLAGS += -DDEFAULT_OVERLAY_ALWAYS_ON
#CFLAGS += -DDEBUG
#CFLAGS += -DWEBMEDIA_COMPAT
LDLIBS=
# Point to your Linux source directory here
LINUXDIR = /usr/src/linux-2.4.20 // First it was just "/usr/src" then
// I appended linux-2.4.20 at the end
all: libs geode_v.o Makefile Durango.o tvlib.o testapps
ioctl_geode_v.h Makefile geodedrv.o
libs:
make -C VidLib
modules: geode_v
clean:
rm -f *.o *tags* .*.o.flags raw.txt core errs tags testapp
vbitest
make -C VidLib clean
captest: captest.c
vbitest: vbitest.c
obj-m := geode_v.o
list-multi := geode_v.o
geode-objs := geodedrv.o vbi.o tvlib.o VidLib/VidLib.o
Durango.o kthread.o
obj-$(CONFIG_GEODE) += geode.o
# Extract lists of the multi-part drivers.
# The 'int-*' lists are the intermediate files used to build the
multi's.
multi-m := $(filter $(list-multi), $(obj-m))
int-m := $(sort $(foreach m, $(multi-m), $($(basename
$(m))-objs)))
# Files that are both resident and modular: remove from modular.
obj-m := $(filter-out $(obj-y), $(obj-m))
int-m := $(filter-out $(int-y), $(int-m))
include $(LINUXDIR)/Rules.make
#fastdep:
geode_v.o: $(geode-objs)
$(LD) $(LD_RFLAG) -r -o $@ $(geode-objs)
Durango.o: durango.c
$(CC) -c durango.c -Idurango -o Durango.o -DOS_LINUX
tvlib.o:tvlib.c
$(CC) -c tvlib.c -Itvlib -O -DOS_LINUX -DLINUX -DCYGNUS
-DTV_OS_LINUX_2_4 -Wall -o tvlib.o $(CFLAGS)
testapps: testapp.c vbitest.c
$(CC) testapp.c -o testapp
$(CC) vbitest.c -o vbitest
$(CC) dumpimg2video.c -o dumpimg2video
$(CC) capture.c -o capture
#geode_v.o: $(GEODE_V_OBJS)
# $(LD) -r -o $@ $(GEODE_V_OBJS)
#
devices:
./make_dev
# installing and uninstalling the geode v4l2 driver
INCLUDE_DIR := /usr/include/linux
KERNEL_VERSION := `uname -r`
MODULES_DIR := $(shell \
test -d "$(INSTALL_MOD_PATH)/lib/modules/$(KERNEL_VERSION)/kernel" &&
\
echo
"$(INSTALL_MOD_PATH)/lib/modules/$(KERNEL_VERSION)/kernel/drivers/media/video"
|| \
echo "$(INSTALL_MOD_PATH)/lib/modules/$(KERNEL_VERSION)/misc" )
install:
mv -v $(INCLUDE_DIR)/ioctl_geode_v.h \
$(INCLUDE_DIR)/ioctl_geode_v.h.old; \
cp -v ./ioctl_geode_v.h $(INCLUDE_DIR); \
mv -v $(MODULES_DIR)/$(obj-m) $(MODULES_DIR)/$(obj-m).old; \
mkdir -p $(MODULES_DIR); \
cp -v $(obj-m) $(MODULES_DIR);
/sbin/depmod -a
uninstall:
mv -v $(INCLUDE_DIR)/ioctl_geode_v.h.old
$(INCLUDE_DIR)/ioctl_geode_v.h; \
mv -v $(MODULES_DIR)/$(obj-m).old $(MODULES_DIR)/$(obj-m); \
/sbin/depmod -a
---------------------------------------------------------------------
Durango is a graphics/video software support package designed to
assist in the development of display drivers and embedded
applications. The core of this package is source code that performs
most of the graphics related functionality for the National
Semiconductor Geode family of products.
Can I test this driver in desktop linux ?
With Regards,
S.Suriya Mohan.
On Wed, 12 Nov 2003 H.-J. Koch wrote :
>
> > What is the implicit declaration is all about ? The relevant
header
> > files are included. Still warnings ? This leads to error.
> > With Regards,
> > S.Suriya Mohan.
>
>If the compiler complains about "implicit declarations" you probably
>include the wrong header files. Maybe some kind of version mismatch.
>If you have sources for several kernels on your computer, do you
>include the headers of the right kernel ?
>
>Hans
>
>
>
>--
>video4linux-list mailing list
>Unsubscribe
mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
>https://www.redhat.com/mailman/listinfo/video4linux-list
There is no substitution for hard work.
Information is wealth.
