rivatv-devel Mailing List for rivatv (Page 2)
Status: Alpha
Brought to you by:
yvanoers
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(16) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(14) |
Feb
(28) |
Mar
(17) |
Apr
(9) |
May
(17) |
Jun
(8) |
Jul
(7) |
Aug
(3) |
Sep
|
Oct
(11) |
Nov
(14) |
Dec
(28) |
2002 |
Jan
(46) |
Feb
(63) |
Mar
(136) |
Apr
(183) |
May
(143) |
Jun
(105) |
Jul
(53) |
Aug
(85) |
Sep
(104) |
Oct
(124) |
Nov
(96) |
Dec
(62) |
2003 |
Jan
(90) |
Feb
(116) |
Mar
(143) |
Apr
(195) |
May
(107) |
Jun
(67) |
Jul
(50) |
Aug
(80) |
Sep
(27) |
Oct
(9) |
Nov
(36) |
Dec
(14) |
2004 |
Jan
(15) |
Feb
(34) |
Mar
(18) |
Apr
(18) |
May
(25) |
Jun
(2) |
Jul
(6) |
Aug
(8) |
Sep
(7) |
Oct
(3) |
Nov
(14) |
Dec
(16) |
2005 |
Jan
(12) |
Feb
(27) |
Mar
(5) |
Apr
(7) |
May
(7) |
Jun
(24) |
Jul
(2) |
Aug
(3) |
Sep
(12) |
Oct
(14) |
Nov
(15) |
Dec
(23) |
2006 |
Jan
(3) |
Feb
(25) |
Mar
(14) |
Apr
(12) |
May
(6) |
Jun
(2) |
Jul
|
Aug
(3) |
Sep
|
Oct
(15) |
Nov
(2) |
Dec
(13) |
2007 |
Jan
(12) |
Feb
|
Mar
(7) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(12) |
Oct
(3) |
Nov
|
Dec
(1) |
2008 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(5) |
Nov
(4) |
Dec
|
2011 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: rafael2k <ra...@ri...> - 2007-09-11 21:38:41
|
Hi Stefan, Thanks for the reply and commit ;) I'll keep looking at the problem this week. Do anyone here activelly uses the rivatv driver? What do people use to grab video to a file? thanks, rafael diniz Em Ter 11 Set 2007, Stefan Jahn escreveu: > Am Mo, 10.09.2007, 03:56, schrieb rafael2k: > > Hi Rafael, > > > I managed to compile rivatv (but w/ lots of unresolved symbols) w/ the > > patch > > attached. > > > > here are the unresolved symbols and warnings: > > I'll have a look at it. Thanks for supplying the patch. I'll try to > adjust the driver code for latest kernel... > > Cheers, Stefan. =2D-=20 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+= =2D+-+- Ci=EAncia da Computa=E7=E3o @ Unicamp R=E1dio Muda, radiolivre.org, TV Piolho, tvlivre.org, www.midiaindependente= =2Eorg Chave PGP: http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0x2FF86098 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+= =2D+-+- |
From: Stefan J. <st...@gr...> - 2007-09-11 16:34:24
|
Am So, 9.09.2007, 16:21, schrieb rafael2k: > hi all, hi! > i'l trying to make rivatv compile and works on 2.6.22.6. > > right now, the only thing i did is the little patch attached ;) > > I managed to compile and run rivatv on kernel 2.4.33.3 of slackware 11 ;) fixes for 2.6.22.6 are now in cvs... cheers, stefan. |
From: Stefan J. <st...@gr...> - 2007-09-11 05:38:39
|
Am Mo, 10.09.2007, 03:56, schrieb rafael2k: Hi Rafael, > I managed to compile rivatv (but w/ lots of unresolved symbols) w/ the > patch > attached. > > here are the unresolved symbols and warnings: I'll have a look at it. Thanks for supplying the patch. I'll try to adjust the driver code for latest kernel... Cheers, Stefan. |
From: rafael2k <ra...@ri...> - 2007-09-11 04:51:21
|
I managed to compile rivatv (but w/ lots of unresolved symbols) w/ the patch attached. here are the unresolved symbols and warnings: WARNING: /home/rafael2k/programs/system/rivatv/src/rivatv.o(.data+0x11d0): Section mismatch: reference to .init.text: (between 'driver_initdata' and 'riva_bit_data') WARNING: "video_device_release" [/home/rafael2k/programs/system/rivatv/src/rivatv.ko] undefined! WARNING: "video_register_device" [/home/rafael2k/programs/system/rivatv/src/rivatv.ko] undefined! WARNING: "video_device_alloc" [/home/rafael2k/programs/system/rivatv/src/rivatv.ko] undefined! WARNING: "video_unregister_device" [/home/rafael2k/programs/system/rivatv/src/rivatv.ko] undefined! WARNING: "video_devdata" [/home/rafael2k/programs/system/rivatv/src/rivatv.ko] undefined! this is w/out agp. w/ agp, i got some extras agp unresolved symbols ;) One question: Is there any way to use rivatv w/ the already build-in kernel driver for the video chip? bye, rafael diniz Em Dom 09 Set 2007, rafael2k escreveu: > hi all, > I added to the patch I just sent a small other fix. > patch attached. > > bye, > rafael diniz -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Ciência da Computação @ Unicamp Rádio Muda, radiolivre.org, TV Piolho, tvlivre.org, www.midiaindependente.org Chave PGP: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2FF86098 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- |
From: rafael2k <ra...@ri...> - 2007-09-10 17:47:44
|
hi all, I added to the patch I just sent a small other fix. patch attached. bye, rafael diniz -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Ciência da Computação @ Unicamp Rádio Muda, radiolivre.org, TV Piolho, tvlivre.org, www.midiaindependente.org Chave PGP: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2FF86098 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- |
From: rafael2k <ra...@ri...> - 2007-09-10 17:16:15
|
hi all, i'l trying to make rivatv compile and works on 2.6.22.6. right now, the only thing i did is the little patch attached ;) I managed to compile and run rivatv on kernel 2.4.33.3 of slackware 11 ;) anyone active in the project? bye, rafael diniz -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Ciência da Computação @ Unicamp Rádio Muda, radiolivre.org, TV Piolho, tvlivre.org, www.midiaindependente.org Chave PGP: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2FF86098 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- |
From: Hot B. <hot...@gm...> - 2007-06-06 15:21:00
|
Found this via slashdot - doesn't seem to offer grounds for optimism http://www.abclinuxu.cz/clanky/rozhovory/andy-ritger-nvidia?page=1 HB |
From: Jeffrey J. K. <riv...@ko...> - 2007-03-30 06:01:01
|
I got mplayer to work. My mistake was in the command line format. The command that worked for me was: mplayer tv:// -tv driver=v4l:device=/dev/video2:norm=NTSC:input=1:outfmt=YUY2:width=352:height=288 (this is different from the rivatv documentation) Interestingly, I don't get any kernel messages while mplayer is playing vs. the error messages I noted below (in my previous message) for tvtime. However, both mplayer and tvtime do send a 'dump' of kernel messages after ending the programs. Also, a better description of the jerkiness I encountered under tvtime is that still frames look fine but motion has a bit of a shakiness to it. I still can't get ffmpeg to work. I wonder whether this is a v4l vs. v4l2 problem. In any case, I seem to be making progress... Jeffrey J. Kosowsky wrote at about 01:12:09 -0400 on Friday, March 30, 2007: > OK -- I was able to get tvtime (but not mplayer) working by > configuring with the additional flag of: --enable-software-conversion. > > However, under tvtime, the video is still a bit jerky with > pauses/jerks about once every second. These jerks seem to correspond > 1-1 with the following (repeated) kernel messages: > Mar 30 00:52:43 kernel: bttv0: reset, reinitialize > Mar 30 00:52:43 kernel: bttv0: PLL can sleep, using XTAL (28636363). > Mar 30 00:52:44 kernel: bttv0: timeout: drop=6945 irq=147662/147674, risc=030b5094, bits: VSYNC HSYNC OFLOW FDSR > > Not really sure though why I get bttv issues since I thought bttv had > nothing to do with this card (and is only present on another separate > Winfast 2000XP Deluxe card). > > **Any ideas on how to eliminate the jitter and pauses? > > Also, I still can't get anything but a green screen under mplayer, > using all different permutation of the basic statement: > mplayer tv:// on:driver=v4l:device=/dev/video2:norm=NTSC:input=1:outfmt\ > =YUY2:width=352:height=288 > > **Any ideas on what I need to do to make mplayer work? > > Also, when I try using ffmpeg: > ffmpeg -vd /dev/video2 -r 15 -b 2048 -an -s 352x288 -t 10 video.mpg > I get the following error message: > QUERYCAP not implemented, probably V4L device but not supporting V4L2 > Could not find video grab device > > **What does this mean and how do I get ffmpeg to work? > > Finally, I have tried different values of agp= but not sure I see any > effect. > **What is the recommended value > > Jeffrey J. Kosowsky wrote at about 12:08:11 -0400 on Wednesday, March 28, 2007: > > I am able to compile the latest CVS version of rivatv under Kernel > > 2.6.20 (see my previous posts for some minor edits I needed to make) > > and it even recognizes by card (as long as I use the 'nv' driver) > > > > However, under both tvtime and mplayer, I only get a blank (green > > screen). > > > > Running tvtime -d /dev/video2 gives the following stream of errors (in > > addition to the green screen): > > videoinput: Can't free frame 0: Invalid argument > > videoinput: Can't free frame 1: Invalid argument > > videoinput: Can't free frame 2: Invalid argument > > videoinput: Can't free frame 3: Invalid argument > > videoinput: Can't wait for frame 0: Invalid argument > > videoinput: Can't wait for frame 1: Invalid argument > > videoinput: Can't wait for frame 2: Invalid argument > > videoinput: Can't wait for frame 3: Invalid argument > > .... (repeats forever) > > > > My kernel shows the following messages: > > rivatv: V4L: Requested IOCTL (0x80685600) not implemented > > rivatv: VIDIOCGCAP > > rivatv: V4L: Requested IOCTL (0x800476C6) not implemented > > rivatv: VIDIOCGCHAN > > rivatv: VIDIOCSCHAN: 0 > > rivatv: VIDIOCGCHAN > > rivatv: VIDIOCGAUDIO > > rivatv: VIDIOCGAUDIO > > rivatv: VIDIOCGCAP > > rivatv: VIDIOCGPICT > > rivatv: VIDIOCSPICT: BRI=32768 HUE=32768 COL=32768 CON=32768 WHI=32768 DEP=16 PAL=7 > > rivatv: VIDIOCSWIN: 704x480 @ (0,0) (key: 0x00000000) > > rivatv: VIDIOCGMBUF > > rivatv: MMAP buffer available in userspace (6480 kb) > > rivatv: VIDIOCGCHAN > > rivatv: VIDIOCSCHAN: 0 > > rivatv: VIDIOCGCHAN > > rivatv: VIDIOCGAUDIO > > rivatv: VIDIOCGPICT > > last message repeated 7 times > > rivatv: VIDIOCGAUDIO > > > > Then when I exit tvtime, I get the following kernel messages: > > rivatv: VIDIOCGAUDIO > > BUG: sleeping function called from invalid context at include/asm/semaphore.h:99 > > in_atomic():0, irqs_disabled():1 > > [<c0620025>] lock_kernel+0x1e/0x3d > > [<f8b4f8ce>] bit_riva_setsda+0x19/0xbc [rivatv] > > [<f89f9028>] i2c_start+0x22/0x3b [i2c_algo_bit] > > [<f89f962d>] bit_xfer+0x1d/0x488 [i2c_algo_bit] > > [<c041fb9c>] __wake_up_common+0x32/0x55 > > [<c0420a95>] __wake_up+0x32/0x43 > > [<f89cb1d5>] i2c_transfer+0x31/0x42 [i2c_core] > > [<f89cb63f>] i2c_smbus_xfer+0x3ad/0x47f [i2c_core] > > [<c04c42f4>] avc_has_perm+0x4e/0x58 > > [<f89cb7d0>] i2c_smbus_write_byte_data+0x38/0x3e [i2c_core] > > [<f8b77113>] saa7108e_write+0x1a/0x43 [saa7108e] > > [<f8b77cd2>] saa7108e_command+0x798/0x935 [saa7108e] > > [<c0462322>] free_pgd_range+0x108/0x195 > > [<c0437a42>] init_waitqueue_head+0x12/0x20 > > [<f8b4c1ac>] rivatv_decoder_output+0x52/0x6b [rivatv] > > [<f8b4c3d3>] rivatv_video_close+0x37/0xb8 [rivatv] > > [<c0473292>] __fput+0xba/0x170 > > [<c0470cf1>] filp_close+0x51/0x58 > > [<c0471c2c>] sys_close+0x70/0xa7 > > [<c0403f64>] syscall_call+0x7/0xb > > [<c0620033>] lock_kernel+0x2c/0x3d > > ======================= > > > > > > When I run: > > mplayer tv:// driver=v4l:device=/dev/video2:input=1:norm=NTSC:outfmt=YUV:width=352:height=288 > > > > I just get a blank green screen > > I don't get any error messages (other than: "Selected input hasn't go > > a tuner!) > > I also played with changing outfmt=UYVY and changing to input=0 or input=2. > > > > When I try: > > ffmpeg -vd /dev/video2 -r 15 -b 2048 -an -s 352x288 -t 10 video.mpg > > I just get the following error message: > > QUERYCAP not implemented, probably V4L device but not supporting V4L2 > > Could not find video grab device > > > > > > Any idea what I might be doing wrong here and how to fix???? > > > > --------------------------------------------------------------------------- > > > > Note that /proc/drivers/rivatv0 shows: > > nVidia Chip: GeForce4 Ti4x00 > > Model: Leadtek Winfast A250 TD GF4 Ti4600 MyViVo > > Architecture: NV20 (NV25) > > Access: Control [0xed000000-0xedffffff] > > FB [0xf0000000-0xf7ffffff] > > Interrupts: 0 out of 3945 (DMA: 0, Overlay: 742, Missing: 3203) > > Device: available > > VideoDecoder: Philips SAA7108E > > Tuner: unavailable > > AudioDecoder: unavailable > > AudioProcessor: unavailable > > IR chip: unavailable > > > > I have the following setup: > > *Hardware* > > ASUS p4pe motherboard > > Leadtek Winfast A250 TD GF4 Ti4600 MyViVo (fully supported by > > SAA7108E driver) > > Leadtek Winfast 2000XP Deluxe analog TV card > > pcHDTV HD-5500 digital TV card > > > > *Software* > > Fedora Core 6/Linux 2.4.20-1.2933 > > Latest CVS of rivatv edited to support kernel 2.4.20 (see previous post) > > (same problem also occurred under 2.4.19) > > xorg.conf nv driver |
From: Jeffrey J. K. <riv...@ko...> - 2007-03-30 05:12:35
|
OK -- I was able to get tvtime (but not mplayer) working by configuring with the additional flag of: --enable-software-conversion. However, under tvtime, the video is still a bit jerky with pauses/jerks about once every second. These jerks seem to correspond 1-1 with the following (repeated) kernel messages: Mar 30 00:52:43 kernel: bttv0: reset, reinitialize Mar 30 00:52:43 kernel: bttv0: PLL can sleep, using XTAL (28636363). Mar 30 00:52:44 kernel: bttv0: timeout: drop=6945 irq=147662/147674, risc=030b5094, bits: VSYNC HSYNC OFLOW FDSR Not really sure though why I get bttv issues since I thought bttv had nothing to do with this card (and is only present on another separate Winfast 2000XP Deluxe card). **Any ideas on how to eliminate the jitter and pauses? Also, I still can't get anything but a green screen under mplayer, using all different permutation of the basic statement: mplayer tv:// on:driver=v4l:device=/dev/video2:norm=NTSC:input=1:outfmt\ =YUY2:width=352:height=288 **Any ideas on what I need to do to make mplayer work? Also, when I try using ffmpeg: ffmpeg -vd /dev/video2 -r 15 -b 2048 -an -s 352x288 -t 10 video.mpg I get the following error message: QUERYCAP not implemented, probably V4L device but not supporting V4L2 Could not find video grab device **What does this mean and how do I get ffmpeg to work? Finally, I have tried different values of agp= but not sure I see any effect. **What is the recommended value Jeffrey J. Kosowsky wrote at about 12:08:11 -0400 on Wednesday, March 28, 2007: > I am able to compile the latest CVS version of rivatv under Kernel > 2.6.20 (see my previous posts for some minor edits I needed to make) > and it even recognizes by card (as long as I use the 'nv' driver) > > However, under both tvtime and mplayer, I only get a blank (green > screen). > > Running tvtime -d /dev/video2 gives the following stream of errors (in > addition to the green screen): > videoinput: Can't free frame 0: Invalid argument > videoinput: Can't free frame 1: Invalid argument > videoinput: Can't free frame 2: Invalid argument > videoinput: Can't free frame 3: Invalid argument > videoinput: Can't wait for frame 0: Invalid argument > videoinput: Can't wait for frame 1: Invalid argument > videoinput: Can't wait for frame 2: Invalid argument > videoinput: Can't wait for frame 3: Invalid argument > .... (repeats forever) > > My kernel shows the following messages: > rivatv: V4L: Requested IOCTL (0x80685600) not implemented > rivatv: VIDIOCGCAP > rivatv: V4L: Requested IOCTL (0x800476C6) not implemented > rivatv: VIDIOCGCHAN > rivatv: VIDIOCSCHAN: 0 > rivatv: VIDIOCGCHAN > rivatv: VIDIOCGAUDIO > rivatv: VIDIOCGAUDIO > rivatv: VIDIOCGCAP > rivatv: VIDIOCGPICT > rivatv: VIDIOCSPICT: BRI=32768 HUE=32768 COL=32768 CON=32768 WHI=32768 DEP=16 PAL=7 > rivatv: VIDIOCSWIN: 704x480 @ (0,0) (key: 0x00000000) > rivatv: VIDIOCGMBUF > rivatv: MMAP buffer available in userspace (6480 kb) > rivatv: VIDIOCGCHAN > rivatv: VIDIOCSCHAN: 0 > rivatv: VIDIOCGCHAN > rivatv: VIDIOCGAUDIO > rivatv: VIDIOCGPICT > last message repeated 7 times > rivatv: VIDIOCGAUDIO > > Then when I exit tvtime, I get the following kernel messages: > rivatv: VIDIOCGAUDIO > BUG: sleeping function called from invalid context at include/asm/semaphore.h:99 > in_atomic():0, irqs_disabled():1 > [<c0620025>] lock_kernel+0x1e/0x3d > [<f8b4f8ce>] bit_riva_setsda+0x19/0xbc [rivatv] > [<f89f9028>] i2c_start+0x22/0x3b [i2c_algo_bit] > [<f89f962d>] bit_xfer+0x1d/0x488 [i2c_algo_bit] > [<c041fb9c>] __wake_up_common+0x32/0x55 > [<c0420a95>] __wake_up+0x32/0x43 > [<f89cb1d5>] i2c_transfer+0x31/0x42 [i2c_core] > [<f89cb63f>] i2c_smbus_xfer+0x3ad/0x47f [i2c_core] > [<c04c42f4>] avc_has_perm+0x4e/0x58 > [<f89cb7d0>] i2c_smbus_write_byte_data+0x38/0x3e [i2c_core] > [<f8b77113>] saa7108e_write+0x1a/0x43 [saa7108e] > [<f8b77cd2>] saa7108e_command+0x798/0x935 [saa7108e] > [<c0462322>] free_pgd_range+0x108/0x195 > [<c0437a42>] init_waitqueue_head+0x12/0x20 > [<f8b4c1ac>] rivatv_decoder_output+0x52/0x6b [rivatv] > [<f8b4c3d3>] rivatv_video_close+0x37/0xb8 [rivatv] > [<c0473292>] __fput+0xba/0x170 > [<c0470cf1>] filp_close+0x51/0x58 > [<c0471c2c>] sys_close+0x70/0xa7 > [<c0403f64>] syscall_call+0x7/0xb > [<c0620033>] lock_kernel+0x2c/0x3d > ======================= > > > When I run: > mplayer tv:// driver=v4l:device=/dev/video2:input=1:norm=NTSC:outfmt=YUV:width=352:height=288 > > I just get a blank green screen > I don't get any error messages (other than: "Selected input hasn't go > a tuner!) > I also played with changing outfmt=UYVY and changing to input=0 or input=2. > > When I try: > ffmpeg -vd /dev/video2 -r 15 -b 2048 -an -s 352x288 -t 10 video.mpg > I just get the following error message: > QUERYCAP not implemented, probably V4L device but not supporting V4L2 > Could not find video grab device > > > Any idea what I might be doing wrong here and how to fix???? > > --------------------------------------------------------------------------- > > Note that /proc/drivers/rivatv0 shows: > nVidia Chip: GeForce4 Ti4x00 > Model: Leadtek Winfast A250 TD GF4 Ti4600 MyViVo > Architecture: NV20 (NV25) > Access: Control [0xed000000-0xedffffff] > FB [0xf0000000-0xf7ffffff] > Interrupts: 0 out of 3945 (DMA: 0, Overlay: 742, Missing: 3203) > Device: available > VideoDecoder: Philips SAA7108E > Tuner: unavailable > AudioDecoder: unavailable > AudioProcessor: unavailable > IR chip: unavailable > > I have the following setup: > *Hardware* > ASUS p4pe motherboard > Leadtek Winfast A250 TD GF4 Ti4600 MyViVo (fully supported by > SAA7108E driver) > Leadtek Winfast 2000XP Deluxe analog TV card > pcHDTV HD-5500 digital TV card > > *Software* > Fedora Core 6/Linux 2.4.20-1.2933 > Latest CVS of rivatv edited to support kernel 2.4.20 (see previous post) > (same problem also occurred under 2.4.19) > xorg.conf nv driver |
From: Stefan J. <st...@gr...> - 2007-03-28 17:20:02
|
Am Di, 27.03.2007, 07:25, schrieb Jeffrey J. Kosowsky: Hi! > Frustration! > I finally got rivatv to compile under FedoraCore 6/kernel 2.6.19 (see > the posts from January) but then was unable to use rivatv since my > brain-dead ASUS p4pe board hides the SMBus. > > This ASUS error was corrected (again) in 2.6.20. > But now, I can't compile rivatv anymore. > > I get the following errors: > > /home/me/rivatv/src/i2c-riva.c: In function 'rivatv_release_i2c': > /home/me/rivatv/src/i2c-riva.c:125: error: implicit declaration of > function 'i2c_bit_del_bus' > /home/me/rivatv/src/i2c-riva.c: At top level: > /home/me/rivatv/src/i2c-riva.c:477: error: 'driver_init' redeclared as > different kind of symbol include/linux/device.h:436: error: previous > declaration of 'driver_init' was here > > Indeed under kernel 2.6.20, in /include/linux/device.h, we have: > void driver_init(void); > while under kernel 2.6.19, the function is not defined in device.h > > Note in riva.c, we have > static struct __initdata i2c_riva_initdata driver_init = { > .algo = &riva_bit_data, > .bus0 = &i2c_riva_bus0, > .bus1 = &i2c_riva_bus1, > .bus2 = &i2c_riva_bus2, > .bus_init = bit_riva_init > }; > > Is device.h referring to a different driver_init function? > If so do we need to rename it? Fixed in CVS. Cheers, Stefan. |
From: Jeffrey J. K. <ri...@ko...> - 2007-03-28 16:08:20
|
I am able to compile the latest CVS version of rivatv under Kernel 2.6.20 (see my previous posts for some minor edits I needed to make) and it even recognizes by card (as long as I use the 'nv' driver) However, under both tvtime and mplayer, I only get a blank (green screen). Running tvtime -d /dev/video2 gives the following stream of errors (in addition to the green screen): videoinput: Can't free frame 0: Invalid argument videoinput: Can't free frame 1: Invalid argument videoinput: Can't free frame 2: Invalid argument videoinput: Can't free frame 3: Invalid argument videoinput: Can't wait for frame 0: Invalid argument videoinput: Can't wait for frame 1: Invalid argument videoinput: Can't wait for frame 2: Invalid argument videoinput: Can't wait for frame 3: Invalid argument .... (repeats forever) My kernel shows the following messages: rivatv: V4L: Requested IOCTL (0x80685600) not implemented rivatv: VIDIOCGCAP rivatv: V4L: Requested IOCTL (0x800476C6) not implemented rivatv: VIDIOCGCHAN rivatv: VIDIOCSCHAN: 0 rivatv: VIDIOCGCHAN rivatv: VIDIOCGAUDIO rivatv: VIDIOCGAUDIO rivatv: VIDIOCGCAP rivatv: VIDIOCGPICT rivatv: VIDIOCSPICT: BRI=32768 HUE=32768 COL=32768 CON=32768 WHI=32768 DEP=16 PAL=7 rivatv: VIDIOCSWIN: 704x480 @ (0,0) (key: 0x00000000) rivatv: VIDIOCGMBUF rivatv: MMAP buffer available in userspace (6480 kb) rivatv: VIDIOCGCHAN rivatv: VIDIOCSCHAN: 0 rivatv: VIDIOCGCHAN rivatv: VIDIOCGAUDIO rivatv: VIDIOCGPICT last message repeated 7 times rivatv: VIDIOCGAUDIO Then when I exit tvtime, I get the following kernel messages: rivatv: VIDIOCGAUDIO BUG: sleeping function called from invalid context at include/asm/semaphore.h:99 in_atomic():0, irqs_disabled():1 [<c0620025>] lock_kernel+0x1e/0x3d [<f8b4f8ce>] bit_riva_setsda+0x19/0xbc [rivatv] [<f89f9028>] i2c_start+0x22/0x3b [i2c_algo_bit] [<f89f962d>] bit_xfer+0x1d/0x488 [i2c_algo_bit] [<c041fb9c>] __wake_up_common+0x32/0x55 [<c0420a95>] __wake_up+0x32/0x43 [<f89cb1d5>] i2c_transfer+0x31/0x42 [i2c_core] [<f89cb63f>] i2c_smbus_xfer+0x3ad/0x47f [i2c_core] [<c04c42f4>] avc_has_perm+0x4e/0x58 [<f89cb7d0>] i2c_smbus_write_byte_data+0x38/0x3e [i2c_core] [<f8b77113>] saa7108e_write+0x1a/0x43 [saa7108e] [<f8b77cd2>] saa7108e_command+0x798/0x935 [saa7108e] [<c0462322>] free_pgd_range+0x108/0x195 [<c0437a42>] init_waitqueue_head+0x12/0x20 [<f8b4c1ac>] rivatv_decoder_output+0x52/0x6b [rivatv] [<f8b4c3d3>] rivatv_video_close+0x37/0xb8 [rivatv] [<c0473292>] __fput+0xba/0x170 [<c0470cf1>] filp_close+0x51/0x58 [<c0471c2c>] sys_close+0x70/0xa7 [<c0403f64>] syscall_call+0x7/0xb [<c0620033>] lock_kernel+0x2c/0x3d ======================= When I run: mplayer tv:// driver=v4l:device=/dev/video2:input=1:norm=NTSC:outfmt=YUV:width=352:height=288 I just get a blank green screen I don't get any error messages (other than: "Selected input hasn't go a tuner!) I also played with changing outfmt=UYVY and changing to input=0 or input=2. When I try: ffmpeg -vd /dev/video2 -r 15 -b 2048 -an -s 352x288 -t 10 video.mpg I just get the following error message: QUERYCAP not implemented, probably V4L device but not supporting V4L2 Could not find video grab device Any idea what I might be doing wrong here and how to fix???? --------------------------------------------------------------------------- Note that /proc/drivers/rivatv0 shows: nVidia Chip: GeForce4 Ti4x00 Model: Leadtek Winfast A250 TD GF4 Ti4600 MyViVo Architecture: NV20 (NV25) Access: Control [0xed000000-0xedffffff] FB [0xf0000000-0xf7ffffff] Interrupts: 0 out of 3945 (DMA: 0, Overlay: 742, Missing: 3203) Device: available VideoDecoder: Philips SAA7108E Tuner: unavailable AudioDecoder: unavailable AudioProcessor: unavailable IR chip: unavailable I have the following setup: *Hardware* ASUS p4pe motherboard Leadtek Winfast A250 TD GF4 Ti4600 MyViVo (fully supported by SAA7108E driver) Leadtek Winfast 2000XP Deluxe analog TV card pcHDTV HD-5500 digital TV card *Software* Fedora Core 6/Linux 2.4.20-1.2933 Latest CVS of rivatv edited to support kernel 2.4.20 (see previous post) (same problem also occurred under 2.4.19) xorg.conf nv driver |
From: Jeffrey J. K. <ri...@ko...> - 2007-03-28 14:41:39
|
Jeffrey J. Kosowsky wrote at about 01:25:32 -0400 on Tuesday, March 27, 2007: > Frustration! > I finally got rivatv to compile under FedoraCore 6/kernel 2.6.19 (see > the posts from January) but then was unable to use rivatv since my > brain-dead ASUS p4pe board hides the SMBus. > > This ASUS error was corrected (again) in 2.6.20. > But now, I can't compile rivatv anymore. > > I get the following errors: > > /home/me/rivatv/src/i2c-riva.c: In function 'rivatv_release_i2c': > /home/me/rivatv/src/i2c-riva.c:125: error: implicit declaration of function 'i2c_bit_del_bus' > /home/me/rivatv/src/i2c-riva.c: At top level: > /home/me/rivatv/src/i2c-riva.c:477: error: 'driver_init' redeclared as > different kind of symbol include/linux/device.h:436: error: previous > declaration of 'driver_init' was here > > Indeed under kernel 2.6.20, in /include/linux/device.h, we have: > void driver_init(void); > while under kernel 2.6.19, the function is not defined in device.h > > Note in riva.c, we have > static struct __initdata i2c_riva_initdata driver_init = { > .algo = &riva_bit_data, > .bus0 = &i2c_riva_bus0, > .bus1 = &i2c_riva_bus1, > .bus2 = &i2c_riva_bus2, > .bus_init = bit_riva_init > }; > > Is device.h referring to a different driver_init function? > If so do we need to rename it? > > Thanks OK, I was able fix the above plus one other compile error by editing src/i2c-riva.c as follows: Rename: i2c_riva_initdata driver_init to: i2c_riva_initdata driver_init2 (2 times) Rename: i2c_bit_del_bus to: i2c_del_adapter (3 times) If these are indeed 'valid' changes, would it be possible to add them to the latest CVS? |
From: Jeffrey J. K. <ri...@ko...> - 2007-03-27 05:25:43
|
Frustration! I finally got rivatv to compile under FedoraCore 6/kernel 2.6.19 (see the posts from January) but then was unable to use rivatv since my brain-dead ASUS p4pe board hides the SMBus. This ASUS error was corrected (again) in 2.6.20. But now, I can't compile rivatv anymore. I get the following errors: /home/me/rivatv/src/i2c-riva.c: In function 'rivatv_release_i2c': /home/me/rivatv/src/i2c-riva.c:125: error: implicit declaration of function 'i2c_bit_del_bus' /home/me/rivatv/src/i2c-riva.c: At top level: /home/me/rivatv/src/i2c-riva.c:477: error: 'driver_init' redeclared as different kind of symbol include/linux/device.h:436: error: previous declaration of 'driver_init' was here Indeed under kernel 2.6.20, in /include/linux/device.h, we have: void driver_init(void); while under kernel 2.6.19, the function is not defined in device.h Note in riva.c, we have static struct __initdata i2c_riva_initdata driver_init = { .algo = &riva_bit_data, .bus0 = &i2c_riva_bus0, .bus1 = &i2c_riva_bus1, .bus2 = &i2c_riva_bus2, .bus_init = bit_riva_init }; Is device.h referring to a different driver_init function? If so do we need to rename it? Thanks |
From: Yuri v. O. <yva...@xs...> - 2007-03-06 21:08:27
|
Hi, The project is not dead. A better description would be 'in a coma'. As for the Personal Cinema cards, I believe there is still an issue with the decoders on them. All I can promise you (and everybody else), is better times will come, but I can not say when. (I should be careful not to turn the project into a religion :) Regards, Yuri On Tue, 6 Mar 2007, tekwyzrd wrote: > I have a nVidia FX5700 based Personal Cinema video card and have been > checking periodically for any developments. Now I see that RivaTV is > being removed from the Gentoo repository due to incompatibility with the > new linux kernels. > I also see that there has been no new version for nearly a year and no sign > of progress. Is this project dead? > > If so, is there ANY way to make use of the card's tv tuner under linux > or am I stuck with a card that will always be only half functional? > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Rivatv-help mailing list > Riv...@li... > https://lists.sourceforge.net/lists/listinfo/rivatv-help > > |
From: Brian A. S. <lav...@sp...> - 2007-01-22 03:28:38
|
> > No. > >> thanks >> >> ps. in short i can't install anything..... Call your Linux distribution vendor and tell them you think that default installs should come with kernel header files. Unmodified, preferably. Send us the output of command: "cat /etc/issue" You probably just need to "rpm -vhi kernel-source-foo.rpm" ~BAS >> > > You're right, you can't. Get your kernel headers, as the error message > says above, and you're off to a start. Read up on how to get them, for > your particular distro, using google or your distro's website.. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > rivatv-devel mailing list > riv...@li... > https://lists.sourceforge.net/lists/listinfo/rivatv-devel > l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ "...from back in the heady days when "helpdesk" meant nothing, "diskquota" meant everything, and lives could be bought and sold for a couple of pages of laser printout - and frequently were." |
From: Brad B. <li...@l8...> - 2007-01-21 23:22:23
|
On Sat, 20 Jan 2007 18:47:42 -0800 (PST) harry champ <ahy...@ya...> wrote: > hi, > > I'm new to linux and all i know is how to install linux on a pc > > how do you configure/install the tv driver for v7100 so tv can be > watched? > > I followed every instruction but nothing happened. > > 1st step was ./configure as written in FAQ and this was the result: > > linux:/home/ssc/Desktop/rivatv-0.8.5 # ./configure > Checking for configured kernel headers... not found > *** ERROR: > *** In order to build RivaTV you need a set of kernel headers properly > *** configured for the kernel you intend to use RivaTV with. > linux:/home/ssc/Desktop/rivatv-0.8.5 # > > 2nd step was make and this is the output: Why on earth would you proceed with the second step, when it *clearly* says ERROR:..? > > linux:/home/ssc/Desktop/rivatv-0.8.5 # make > make: *** No targets specified and no makefile found. Stop. > linux:/home/ssc/Desktop/rivatv-0.8.5 # > > is there no package where in a double click of a mouse and it will > install like mac/windows? > No. > thanks > > ps. in short i can't install anything..... > You're right, you can't. Get your kernel headers, as the error message says above, and you're off to a start. Read up on how to get them, for your particular distro, using google or your distro's website.. |
From: harry c. <ahy...@ya...> - 2007-01-21 02:47:53
|
hi, I'm new to linux and all i know is how to install linux on a pc how do you configure/install the tv driver for v7100 so tv can be watched? I followed every instruction but nothing happened. 1st step was ./configure as written in FAQ and this was the result: linux:/home/ssc/Desktop/rivatv-0.8.5 # ./configure Checking for configured kernel headers... not found *** ERROR: *** In order to build RivaTV you need a set of kernel headers properly *** configured for the kernel you intend to use RivaTV with. linux:/home/ssc/Desktop/rivatv-0.8.5 # 2nd step was make and this is the output: linux:/home/ssc/Desktop/rivatv-0.8.5 # make make: *** No targets specified and no makefile found. Stop. linux:/home/ssc/Desktop/rivatv-0.8.5 # is there no package where in a double click of a mouse and it will install like mac/windows? thanks ps. in short i can't install anything..... Harrison Champ 詹栢 --------------------------------- Don't be flakey. Get Yahoo! Mail for Mobile and always stay connected to friends. |
From: Daniel W. <dtw...@ya...> - 2007-01-19 03:43:11
|
Hi, I tried installing rivatv on my machine under linux ubuntu 6.10 Edgy and got the following message in my var/log/messages: Linux video capture interface: v1.00 rivatv: Video4Linux driver for NVIDIA cards rivatv: MMX processor extension enabled rivatv: nVidia card found - rivatv0 rivatv: Unknown MSI board: card not in database rivatv: PCI identifiers: 10DE 0141 1462 9791 rivatv: Attempting to load most common decoder (SAA7108E) i2c_adapter i2c-2: SMBus Quick command not supported, can't probe for chips i2c_adapter i2c-3: SMBus Quick command not supported, can't probe for chips i2c_adapter i2c-4: SMBus Quick command not supported, can't probe for chips ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 50 rivatv: cannot reserve MMIO region at 0xc8000000 rivatv: 0xc8000000 - 0xcbffffff is reserved by nvidia allocation failed: out of vmalloc space - use vmalloc=<size> to increase size. rivatv: cannot ioremap FB base at 0xc0000000 I'm pretty sure that my video capture card is not supported by rivatv. The decoder chip is SAA7115HL. My card is listed in Linux as NV43 GeForce 6600. I'd like to try and develop my own driver but I've never written one before and have no idea of where to begin. Could you give me some pointers to get me started? I'm fairly new to Linux but have a computer programming/engineering background. thanks. dan -- I'm not lazy; I'm economical with my effort. |
From: Vincent C. <vc...@ho...> - 2007-01-13 09:15:53
|
Hi I've just installed RivaTV CVS 2006-04-29 under Gentoo Linux (2.6.18-gentoo-r6), AMD Athlon XP. My PC has an ASUS V9520 Video Suite with VIVO. I could succesfully get a video picture in mlplayer but only under certain conditions. I'm using Xorg-x11-7.1 and and the open source "nv" driver. I first compiled rivatv with --disable-asm because I got compile error messages such as: "Invalid operands for 'shl'". It then compiled without any error using GCC 4.1.1-r3." Next I had to run the following mplayer command: $ mplayer -tv noaudio:driver=v4l:norm=pal:input=1:outfmt=YUY2:width=352:height=288 -quiet tv:// for mplayer (1.0-pre8) command line syntax has changed (use tv:// instead of -tv on). When I first ran mplayer I got a green image whatever I connected to the video IN. When I ran mplayer from the console I get it filled with messages like this: ioctl mcapture failed: Invalid argument ioctl mcapture failed: Invalid argument ioctl mcapture failed: Invalid argument ... Here was dmesg output: rivatv: Video4Linux driver for NVIDIA cards rivatv: MMX processor extension enabled rivatv: nVidia card found - rivatv0 rivatv: Identified your board as Asus V9520 Video Suite rivatv: Attempting to load module saa7108e rivatv: MTRR successfully enabled rivatv: PCI nVidia NV30 card detected (GeForce FX 5200 [0x322], 128MB @ 0xD0000000) rivatv: I2C adapter driver for NVIDIA cards rivatv: video decoder chip registered rivatv: procfs file registered for rivatv0 video_device_create_file error: -17 rivatv: allocated YUV capture buffer (812 kb) rivatv: AGPGART: no AGP bridge available rivatv: Hash table layout: 4kB (9 bits) @ 0xDC710000 rivatv: No additional driver detected rivatv: PFIFO and PGRAPH disabled, enabling... rivatv: Setting up instance RAM for DMA rivatv: DMA transfers disabled rivatv: PMEDIA, PVIDEO and PFB disabled, enabling... rivatv: successfully requested IRQ 10 rivatv: Video4Linux device driver registered NVRM: The NVIDIA probe routine was not called for 1 device(s). NVRM: This can occur when a driver such as rivafb, nvidiafb or NVRM: rivatv was loaded and obtained ownership of the NVIDIA NVRM: device(s). NVRM: Try unloading the rivafb, nvidiafb or rivatv kernel module NVRM: (and/or reconfigure your kernel without rivafb/nvidiafb NVRM: support), then try loading the NVIDIA kernel module again. NVRM: No NVIDIA graphics adapter probed! rivatv: V4L: Requested IOCTL (0xC02C563A) not implemented rivatv: V4L: Requested IOCTL (0x4014563C) not implemented rivatv: V4L: Requested IOCTL (0x80685600) not implemented rivatv: allocated 6480 kb MMAP buffer space rivatv: MMAP buffer available in user space (6480 kb) rivatv: capture palette changed: <invalid> -> YUV422 rivatv: decoder output set to default UYVY rivatv: V4L: Requested IOCTL (0x80685600) not implemented NVRM messages are caused by proprietary module but I can't explain why it tried to load although I did setup Xorg to run with the open source driver. I then loaded rivatv module with dma=1 and got none of these error messages: ioctl mcapture failed: Invalid argument rivatv: V4L: Requested IOCTL (0xC02C563A) not implemented rivatv: V4L: Requested IOCTL (0x4014563C) not implemented rivatv: V4L: Requested IOCTL (0x80685600) not implemented however the PC became awfully slow (still responding though) and it didn't solve the green picture problem. I recompiled rivatv with --enable-agp and --enable-software-conversion. I loaded rivatv with argument agp=1 only and it worked. I still get error messages like these: video_device_create_file error: -17 rivatv: V4L: Requested IOCTL (0xC02C563A) not implemented rivatv: V4L: Requested IOCTL (0x4014563C) not implemented rivatv: V4L: Requested IOCTL (0x80685600) not implemented but they don't seem to prevent rivatv from working. I have a connector box with a cable. The box provides 4 connectors, Input and Output with composite and S-Video each. Run $ mplayer -tv on:driver=v4l:norm=PAL:input=0:outfmt=YUY2:width=352:height=288 when using the composite input. Run $ mplayer -tv on:driver=v4l:norm=PAL:input=1:outfmt=YUY2:width=352:height=288 when using the S-Video input. I never had success using DMA though. I have created an ebuild for Gentoo, which I'll be posting soon in Gentoo forums, for those who are interrested. Note I've also had to create a patch for rivatv-0.8.6 that I've zipped. Thanks a lot in advance for such a good work, guys :-) . Vince C. _________________________________________________________________ A la recherche d'un ami d'enfance ? Peut-être est-il dans la liste d'amis de vos amis ! http://spaces.live.com/default.aspx?page=Ed01&ss=True |
From: Vincent C. <vc...@ho...> - 2007-01-13 09:14:54
|
Hi I've just installed RivaTV CVS 2006-04-29 under Gentoo Linux (2.6.18-gentoo-r6), AMD Athlon XP. My PC has an ASUS V9520 Video Suite with VIVO. I could succesfully get a video picture in mlplayer but only under certain conditions. I'm using Xorg-x11-7.1 and and the open source "nv" driver. I first compiled rivatv with --disable-asm because I got compile error messages such as: "Invalid operands for 'shl'". It then compiled without any error using GCC 4.1.1-r3." Next I had to run the following mplayer command: $ mplayer -tv noaudio:driver=v4l:norm=pal:input=1:outfmt=YUY2:width=352:height=288 -quiet tv:// for mplayer (1.0-pre8) command line syntax has changed (use tv:// instead of -tv on). When I first ran mplayer I got a green image whatever I connected to the video IN. When I ran mplayer from the console I get it filled with messages like this: ioctl mcapture failed: Invalid argument ioctl mcapture failed: Invalid argument ioctl mcapture failed: Invalid argument ... Here was dmesg output: rivatv: Video4Linux driver for NVIDIA cards rivatv: MMX processor extension enabled rivatv: nVidia card found - rivatv0 rivatv: Identified your board as Asus V9520 Video Suite rivatv: Attempting to load module saa7108e rivatv: MTRR successfully enabled rivatv: PCI nVidia NV30 card detected (GeForce FX 5200 [0x322], 128MB @ 0xD0000000) rivatv: I2C adapter driver for NVIDIA cards rivatv: video decoder chip registered rivatv: procfs file registered for rivatv0 video_device_create_file error: -17 rivatv: allocated YUV capture buffer (812 kb) rivatv: AGPGART: no AGP bridge available rivatv: Hash table layout: 4kB (9 bits) @ 0xDC710000 rivatv: No additional driver detected rivatv: PFIFO and PGRAPH disabled, enabling... rivatv: Setting up instance RAM for DMA rivatv: DMA transfers disabled rivatv: PMEDIA, PVIDEO and PFB disabled, enabling... rivatv: successfully requested IRQ 10 rivatv: Video4Linux device driver registered NVRM: The NVIDIA probe routine was not called for 1 device(s). NVRM: This can occur when a driver such as rivafb, nvidiafb or NVRM: rivatv was loaded and obtained ownership of the NVIDIA NVRM: device(s). NVRM: Try unloading the rivafb, nvidiafb or rivatv kernel module NVRM: (and/or reconfigure your kernel without rivafb/nvidiafb NVRM: support), then try loading the NVIDIA kernel module again. NVRM: No NVIDIA graphics adapter probed! rivatv: V4L: Requested IOCTL (0xC02C563A) not implemented rivatv: V4L: Requested IOCTL (0x4014563C) not implemented rivatv: V4L: Requested IOCTL (0x80685600) not implemented rivatv: allocated 6480 kb MMAP buffer space rivatv: MMAP buffer available in user space (6480 kb) rivatv: capture palette changed: <invalid> -> YUV422 rivatv: decoder output set to default UYVY rivatv: V4L: Requested IOCTL (0x80685600) not implemented NVRM messages are caused by proprietary module but I can't explain why it tried to load although I did setup Xorg to run with the open source driver. I then loaded rivatv module with dma=1 and got none of these error messages: ioctl mcapture failed: Invalid argument rivatv: V4L: Requested IOCTL (0xC02C563A) not implemented rivatv: V4L: Requested IOCTL (0x4014563C) not implemented rivatv: V4L: Requested IOCTL (0x80685600) not implemented however the PC became awfully slow (still responding though) and it didn't solve the green picture problem. I recompiled rivatv with --enable-agp and --enable-software-conversion. I loaded rivatv with argument agp=1 only and it worked. I still get error messages like these: video_device_create_file error: -17 rivatv: V4L: Requested IOCTL (0xC02C563A) not implemented rivatv: V4L: Requested IOCTL (0x4014563C) not implemented rivatv: V4L: Requested IOCTL (0x80685600) not implemented but they don't seem to prevent rivatv from working. I have a connector box with a cable. The box provides 4 connectors, Input and Output with composite and S-Video each. Run $ mplayer -tv on:driver=v4l:norm=PAL:input=0:outfmt=YUY2:width=352:height=288 when using the composite input. Run $ mplayer -tv on:driver=v4l:norm=PAL:input=1:outfmt=YUY2:width=352:height=288 when using the S-Video input. I never had success using DMA though. I have created an ebuild for Gentoo, which I'll be posting soon in Gentoo forums, for those who are interrested. Note I've also had to create a patch for rivatv-0.8.6 that I've zipped. Thanks a lot in advance for such a good work, guys :-) . Vince C. _________________________________________________________________ A la recherche d'un ami d'enfance ? Peut-être est-il dans la liste d'amis de vos amis ! http://spaces.live.com/default.aspx?page=Ed01&ss=True |
From: Dirk T. <dth...@gm...> - 2007-01-09 12:25:46
|
On Tue, Jan 09, 2007 at 09:29:24AM +0100, Yuri van Oers wrote: > On Tue, 9 Jan 2007, Dirk Thierbach wrote: >> Yuri van Oers wrote: >>> configure fixes. Except for one Section mismatch I don't get, >> Do you mean the section mismatch mentioned by Jeffrey doesn't happen on >> your system, or do you mean it does happen on your system, but you don't >> understand the reason? > The latter, it happens on my system, but I don't know why. Online browsing of the kernel source shows that there at least from 2.6.17 on (maybe earlier) there is a macro DEFINE_SPINLOCK, and declarations like static spinlock_t floppy_lock = SPIN_LOCK_UNLOCKED; have been changed to static DEFINE_SPINLOCK(floppy_lock); verified for drivers/block/floppy.c in this case (which is unlikely to change, except than to keep up with structural changes in the kernel). It also shows that already in 2.6.17, they were doing fancy stuff with sections for the spinlocks, but it looks like the first style would still work there. I'd suggest to inspect floppy.c in 2.6.19, also to inspect include/linux/spinlock.h and friends, and to change static spinlock_t riva_reg_lock = SPIN_LOCK_UNLOCKED; to static DEFINE_SPINLOCK(riva_reg_lock); in i2c-riva.c (if still appropriate). Maybe that will solve the problem. On a different point, --- rivatv/configure 2005-10-16 12:01:03.000000000 +0200 +++ /home/dirk/cvs/rivatv/configure 2007-01-09 08:45:22.000000000 +0100 @@ -79,6 +79,9 @@ fi UTS_RELEASE="`awk '/UTS_RELEASE/ {print $3}' $kernel/include/linux/version.h | sed -e 's/\\"//g' | sed -n '$p'`" +if test "$UTS_RELEASE" = ""; then + UTS_RELEASE="`awk '/UTS_RELEASE/ {print $3}' $kernel/include/linux/utsre lease.h | sed -e 's/\\"//g' | sed -n '$p'`" +fi # Mandrake / RedHat specific NUM_RELEASE=`cat $kernel/include/linux/version.h | grep -c UTS_RELEASE` if test `expr $NUM_RELEASE` -gt 1; then if test "$kernel_dirs_given" != "yes"; then UTS_RELEASE="`uname -r`" fi fi wouldn't it make more sense first to test for the existence of $kernel/include/linux/utsrelease.h, get UTS_RELEASE from there if possible, else attempt to get it from $kernel/include/linux/version.h, if it still cannot be found and kernel_dirs_given is false, get the version from 'uname -r', and otherwise output an error message? I also noticed you haven't fixed the %4,%5,%6 permutation in rivatv_soft_scale. Should I do that? That's at least something that's not depended on the kernel :-) Are you tracking the changes in your modified source tree? (Or is it already a branch in the CVS?) - Dirk |
From: Yuri v. O. <yva...@xs...> - 2007-01-09 08:29:35
|
On Tue, 9 Jan 2007, Dirk Thierbach wrote: > Yuri van Oers wrote: > > After receiving several cries of despair ;) and finally making the time to > > do something about it, I've updated the RivaTV CVS with compile and > > configure fixes. Except for one Section mismatch I don't get, > > Do you mean the section mismatch mentioned by Jeffrey doesn't happen on > your system, or do you mean it does happen on your system, but you don't > understand the reason? The latter, it happens on my system, but I don't know why. > > it compiles cleanly. > > Cool. > > While we're at it, do you remember the reason rivatv has to track the > bttv modules? Are there any changes that are needed to make the tuner > modules work with rivatv? > > I am asking because when doing some googling, I noticed that > e.g. tuner.c has been split up in newer kernels into tuner-core.c and > other files, etc. > > It really seems to be a hassle to have to keep up with those changes, > so it might be easier (if possible) to to convinve the kernel > developers to accept the changes into the mainstream kernel. I don't recall the exact reason for including bttv, but I believe it was a matter of convenience, not a fork. In any case I agree with you that it's a hassle to keep up with bttv. That's one of the reasons RivaTV as it is right now will become deprecated, rather sooner than later. > > I have not tested it, since I'm running a newer NVIDIA driver to be able > > to (try and) build the "next level" for rivatv - and I'm too lazy to > > downgrade. > > Did you already test the i2c interface? Does it indeed implement the > SMBus quick command, or was the error mentioned by Jeffrey related to > the NVidia drivers? I'm unsure whether Jeffrey's error came from RivaTV or NVIDIA, but up until now I haven't had problems with the NVIDIA I2C interface. Regards, Yuri |
From: Dirk T. <dth...@gm...> - 2007-01-09 07:43:26
|
Yuri van Oers wrote: > After receiving several cries of despair ;) and finally making the time to > do something about it, I've updated the RivaTV CVS with compile and > configure fixes. Except for one Section mismatch I don't get, Do you mean the section mismatch mentioned by Jeffrey doesn't happen on your system, or do you mean it does happen on your system, but you don't understand the reason? > it compiles cleanly. Cool. While we're at it, do you remember the reason rivatv has to track the bttv modules? Are there any changes that are needed to make the tuner modules work with rivatv? I am asking because when doing some googling, I noticed that e.g. tuner.c has been split up in newer kernels into tuner-core.c and other files, etc. It really seems to be a hassle to have to keep up with those changes, so it might be easier (if possible) to to convinve the kernel developers to accept the changes into the mainstream kernel. > I have not tested it, since I'm running a newer NVIDIA driver to be able > to (try and) build the "next level" for rivatv - and I'm too lazy to > downgrade. Did you already test the i2c interface? Does it indeed implement the SMBus quick command, or was the error mentioned by Jeffrey related to the NVidia drivers? - Dirk |
From: Yuri v. O. <yva...@xs...> - 2007-01-08 21:38:12
|
Hi, After receiving several cries of despair ;) and finally making the time to do something about it, I've updated the RivaTV CVS with compile and configure fixes. Except for one Section mismatch I don't get, it compiles cleanly. At least on my 2.6.19 vanilla kernel. I have not tested it, since I'm running a newer NVIDIA driver to be able to (try and) build the "next level" for rivatv - and I'm too lazy to downgrade. So please test and send any trouble you have to the appropriate list. Thanks to Dirk Thierbach for lending a hand! Regards, Yuri |
From: Dirk T. <dth...@gm...> - 2007-01-07 09:17:03
|
On Sun, Dec 24, 2006 at 02:58:02AM -0500, Jeffrey J. Kosowsky wrote: > [It finally compiles] Great. Please make a patch with diff -uwr (or the corresponding cvs function) against the current cvs and send it to me (directly, not via the list). To avoid another iteration since I cannot test it, please make sure your patch covers the following points: > [no more include/linux/config.h file in 2.6.19] Yuk. I suppose you just replaced it with autoconf.h. Please make sure this is bracketed with #ifdef's for the kernel release, as in #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 19) #include <linux/config.h> #else #include <linux/autoconf.h> #endif just to make sure it doesn't break anything on older kernels that possibly did something else with config.h. > ["videodev.h"] > Apparently, this definition has been moved to: > media/v4l2-dev.h > > (on both vanilla and redhat kernels) > > I solved this (temporarily at least), by adding > #include <media/v4l2-dev.h> > to the file rivatv.h I suppose when looking for the change, you came across information in which kernel release the change happened. So bracket that in the same way as above. > Third: > ../rivatv/src/v4l-riva.c: In function 'rivatv_check_resource': > ../rivatv/src/v4l-riva.c:2540: warning: format '%08lx' expects type 'long unsigned int', but argument 2 has type 'resource_size_t' > ../rivatv/src/v4l-riva.c:2540: warning: format '%08lx' expects type 'long unsigned int', but argument 3 has type 'resource_size_t' > {standard input}: Assembler messages: > {standard input}:2938: Error: suffix or operands invalid for `shl' > > The error "expects type 'long unsigned int', but ... type > 'resource_size_t'" appears to be a casting error where the function > printk expects resourc_size_t to be cast to (unsigned long int). As this is only for the debugging, the quick fix is as you say to just insert casts to (long unsigned) in the argument list. This may still display nonsense on systems where the resource_size_t is actually bigger, but I don't care at the moment. It's easy enough to figure out from the error message that the size is wrong. > Now for the assembler error. I haven't done assembler since the intel > 8085, so I am going to be guessing a bit here. It seems that the > problem is in the shll instructions (lines 1254 and 1255 of > v4l-riva.c). The problem seems to be due to the fact that the shift is > being performed input variables whose size is not known (?). I am also guessing, but maybe it's a 64bit thing -- on 32bit intel systems, the code should be work. But I had to delve into the GNU assembler intracacies myself to find out. > I can get the problem to go away by first 'mov'ing the variables to > a register. It's outside the loop, so that should be ok. src_offset gets only added in the initialization, so one can use a temporary register. src_pitch gets added inside the loop, but shifting it inside a register and the writing back should be ok and work in all cases, as far as I can judge. > I assume that the "right" way is to somehow declare/cast the right > types to the assembler (but I couldn't figure this out...) If it's a 64bit thing, one would need to make sure that a 64bit shift in memory actually exists as an opcode. But as I said, I'd have to figure all that out myself -- I've never looked into 64bit programming. > However, I think there may be another problem too in the code logic > (nothing to do with compilation). Unless I am missing something, the > ordering of the variables referenced in the assembler code, doesn't > seem to match the order of the input variables to the > function. Specifically, %4, %5, and %6 seem to be wrong -- or at least > the inline comments don't match the ordering in the function > definition. (e.g., the comment for %5 says "src_pitch" when it seems > like %5=src_offset) Good catch. I think it's Stefan's code, and it's used only for NV3 and NV4 architecures (quite old cards) anyway, so maybe it never got tested. Since Stefan seems to be busy elsewhere, I'd say that for my understanding of the code, the comments are correct, and %4,%5,%6 should be adjusted. To be sure, let's add a comment describing the change and that testing is needed. > Fourth: > WARNING: .../rivatv/src/rivatv.o - Section mismatch: reference to .init.text: from .data between 'driver_init' (at offset 0x1210) and 'riva_reg_lock' > > Not sure what this is... The problem seems to be with the spinlock "riva_reg_lock" in i2c-riva.c. Maybe the way newer kernel handle spinlocks has changed, and it's now no longer ok to have statically initialized spinlocks (though this is quite usual in older kernels). Have a look at your kernel source, look for some files that use a "static spinlock_t" declaration, and see how they handle it. If something like static spinlock_t my_spinlock = SPIN_LOCK_UNLOCKED; is no longer permitted, and has for example been replaced by a macro call, again try to figure out the kernel version that made this change necessary, and bracket as above. If the spinlock isn't initialized properly, the i2c code may possibly not work. - Dirk |