Hello Don
The -1 in the i2c_enable option will skip a found cx25840.
My opinion is, to not specify any -1. Maybe the default array
is -1,-1,-1,-1...
Only specify the that many of 1 for all cx25840 in your system.
Excerpt from my previous mail:
#dmesg|egrep "cx25840|Initialized"
ivtv: Initialized WinTV PVR 350, card #0
cx25840: starting probe for adapter ivtv i2c driver #0 (0x10005) <---
didn't find one
cx25840: starting probe for adapter ivtv i2c driver #1 (0x10005)
cx25840: detecting cx25840 client on address 0x88
<- found first one, look at the first value of i2c_enable to enable or not
With-1 it will skip (we don't want that!) and the next message will appear:
cx25840: client id: cx25840_i2c_id 0, skipped
With 1 it provides the following message, which is OK:
cx25840: cx25843-23 found. Initializing...
cx25840: requesting /lib/modules/HcwMakoA.ROM
cx25840: firmware loaded
ivtv: i2c attach [client=cx25840[50],ok]
<-- correctly attached
cx25840: decoder set norm PAL
cx25840: decoder set input (6)
cx25840: now setting Tuner input
cx25840: set audio input (0)
cx25840: decoder set norm PAL
ivtv: Initialized WinTV PVR 150, card #1
cx25840: starting probe for adapter ivtv i2c driver #2 (0x10005)
cx25840: detecting cx25840 client on address 0x88
<- found second one, look at the second value of i2c_enable to enable or
not
cx25840: cx25843-23 found. Initializing...
cx25840: requesting /lib/modules/HcwMakoA.ROM
cx25840: firmware loaded
ivtv: i2c attach [client=cx25840[50],ok]
<- correctly attached
cx25840: decoder set norm PAL
cx25840: decoder set input (6)
cx25840: now setting Tuner input
cx25840: set audio input (0)
cx25840: decoder set norm PAL
ivtv: Initialized WinTV PVR 150, card #2
----- Original Message -----
From: "Don Brown" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, July 15, 2005 9:53 PM
Subject: Re: [ivtv-devel] First tuner on PVR-500 not working
On Fri, 15 Jul 2005 15:37:39 -0400, Tyler Trafford wrote
Don Brown wrote:
> > I used to have to same problem with my pvr350 and pvr500. Try
> > changing from 'options cx25840 i2c_enable=-1,1,1' to 'options
> > cx25840
> > i2c_enable=1,1'.
> Okay, so I'm trying to understand the i2c_enable option and I'm afraid
> I don't understand. I thought the docs said to disable it for 250s and
> 350s, and to enable it for 150's and 500s.
That count only includes 150s (and by extension 500s x2) and 350s.
I believe the option isn't needed for the cx25840 module anymore.
I tried (using ivtv 0.3.6w) removing the option completely, and then none
of
my tuners worked. (currently use i2c_enable=-1,-1,1,1), which makes the
first
2 tuners work, but neither on the 500.
I have a 250, 350, and a 500 all in the same server, recognized and
discovered
in that order, my options should be:
i2c_enable=-1,1,1
which would disable it for the 350, but enable it for the 2 tuners on the
500
and the flags need to be reversed for saa7217, right? and identical on
the
saa7115, giving me:
options saa7115 i2c_enable=-1,1,1
options saa7127 i2c_enable=1,-1,-1
options cs25840 i2c_enable=-1,1,1
I think.
Don
Sound right?
Don
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
