Hi

> From: "Thomas Pundt" <[EMAIL PROTECTED]>
> Sent: Thursday, November 07, 2002 9:14 AM
> Subject: Re: terratec cinergy 400
>
> > the last one I tried was a clean 2.5.46 using gcc-3.2 +
> > http://bytesex.org/patches/2.5/patch-2.5.46-kraxel.gz applied
> > (though I'm not sure, if it is needed); I then had to patch
> > linux/drivers/media/video/Makefile and add video-buf.o to the
> > target saa7134, otherwise it would complain if trying to load
> > as module. 

   Interestingly, 0.2.1 compiles fine. (media/video/Makefile patched as above, 
kraxel patch not applied). 

   When I insmod it, I do however get a couple dozen unresolved symbols. The 
first few of these are:

saa7134.o: unresolved symbol videobuf_queue_cancel
saa7134.o: unresolved symbol videobuf_read_stop
saa7134.o: unresolved symbol i2c_master_send
saa7134.o: unresolved symbol videobuf_streamon
saa7134.o: unresolved symbol videobuf_iolock
saa7134.o: unresolved symbol videobuf_dma_pci_map
saa7134.o: unresolved symbol videobuf_querybuf
saa7134.o: unresolved symbol videobuf_dqbuf
saa7134.o: unresolved symbol videobuf_mmap_setup
saa7134.o: unresolved symbol videobuf_queue_init

> > And yes, saa7134 appears in kernel configuration dialog.

   Great, I must have looked in the wrong place (assumed multimedia/ 
Video4Linux). Where in the kernel configuration would I find it ?

   Hope it's not too 'newbie' to ask around for this. Basically I want my 
tuner to work, and then perhaps get it to work from Kylix.


        -Henrik



--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@;redhat.com?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/video4linux-list

Reply via email to