False Start, 5 yard penalty, repeat 1st down...
SO, I took out the old bttv card and put in the PVR-500... I
downloaded the latest ivtv driver (0.3.2z) and tried to compile it. I
got this:
/home/tom/tmp/ivtv-0.3.2z/driver/msp3400.c:131: error: parse error before "int"
/home/tom/tmp/ivtv-0.3.2z/driver/msp3400.c:131: warning: type defaults to `int' in declaration of `module_param'
/home/tom/tmp/ivtv-0.3.2z/driver/msp3400.c:131: warning: function declaration isn't a prototype
/home/tom/tmp/ivtv-0.3.2z/driver/msp3400.c:131: warning: data definition has no type or storage class
....
I
have found many people online that have had this issue, yet I can't
find the solution to the issue. Nobody's responding on the #ivtv-dev
IRC channel either.
Well, time to try emailing the dev list.
Update: - I manually forced all the code to use the "old" way of doing module_param calls, and it seems to be OK now. Stay tuned.
Update:
- I spent most of the day working on that, and it turns out that my
manual code changes caused most of my problems. Right now, I have
s-video input working on both inputs but the audio is just crackly.
Unfortunately, I took a crack at getting the HD3000 cards working and
it didn't work at all :( I'll get it working eventually.
Update:
- I just had to use some different settings for the audio. Here are the
current settings (run in a script) that I use to get my PVR-500 working
(with ivtv driver version 0.3.2z):
modprobe -v tveeprom
modprobe -v cx25840
modprobe -v wm8775
modprobe -v msp3400
modprobe -v tuner
modprobe -v ivtv
sleep 1
ivtvctl -d /dev/video2 -p 0 -u 0x3000 -q 1
ivtvctl -d /dev/video4 -p 0 -u 0x3000 -q 1
I
have no idea if the "sleep 1" is needed, but that's where I left off. I
also don't know why /dev/video2 and /dev/video4 turn out to be the
right ones to use, but it's working, so I'm not messing with it.
Oh,
and, with this IVTV version, you have to change ALL the recording
profiles for PVR cards to record 720x480 because this driver version
doesn't support horizontal scaling.
otherwise, things are
working like a charm (except for the VBI information that shows up as 3
or 4 squiggly lines at the top of the video, which is supposedly normal
because TV overscan usually hides it).