On Tuesday 09 December 2003 10:19 pm, Rex Young wrote:
> > Lets compare notes. What gcc version are you using? Do you use the
> > kernel i2c modules, or the ebuild (if so, which version)? Would you
> > mind posting the ivtv section of your /etc/modules.conf?
>
> gcc version:  I think it updated to 3.2.3-r3 a few days ago.

I know there was a problem with 3.2.1 and ivtv, but 3.2.2 has been 
blessed by the devs. I'm also running 3.2.3 and was starting to wonder 
if this wasn't part of the problem.

> i2c: kernel; I had no idea there was an ebuild

i2c 2.8.0+ needs you to make a small modification to the Makefile. Do 
you have any i2c errors in your logs when you access /dev/video0?

> modules.conf:  I haven't touched it.  For now I use a script I wrote
> to load the modules.  I just thought it would be easier to edit that
> to adapt to changes until I think the box is ready for every-day use.
> When I do work on it, I would be happy to share it.

The Gentoo-ish way of handling the ivtv options would be to create 
/etc/modules.d/ivtv, drop your configs in there, then run 
modules-update. Here's what I'm using:

# WinTV PVR 350
alias char-major-81 videodev
alias char-major-81-0 ivtv
alias /dev/v4l ivtv
options ivtv debug=1 
options tuner type=21
options msp3400 once=1 simple=1
options saa7115 
add below ivtv msp3400 saa7115 saa7127 tuner
post-install ivtv /usr/local/bin/test_ioctl -d /dev/video0 -u 0x3000 -p4
post-install ivtv /usr/local/bin/test_ioctl -d /dev/video16 -u 0x3000
post-install ivtv /usr/local/bin/test_ioctl -d /dev/video32 -u 0x3000


Dave


--
[EMAIL PROTECTED] mailing list

Reply via email to