> I may be wrong, however, the 150 doesn't have a saa7127, and the 350 > doesn't have a cx25340. Therefore, you only need one parameter for each. > > (I only have 2 150s, so am not sure on this)
You're right in that assumption. That is the whole issue. I have two parameters for both the cx25840 and the saa7127 so that I can disable their initialization for one card and enable them for the other. In my case, I have the 350 first, then the 150, so I do: options saa7127 i2c_enable=1,-1 to make sure it initializes on the 350 but NOT the 150 and options cx25840 i2c_enable=-1,1 for the same reason. I want to note, though, that interestingly, as I was playing with it today, I swapped the cards back so that the 350 gets initialized first now instead of the 150 (previously the only way I could get it to work right was to have the 150 first), and got it to work with 0.3.2h again, but this time by only having: alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv options saa7127 i2c_enable=1,-1 options cx25840 no_black_magic=1 Last time, when I had the 150 load first, I had it the other way around, where I specified i2c_enable=1,-1 for the cx25840, and just commented out the saa7127 line. I can't remember if I tried this current setup with the newer driver versions or not. I'll try to play with it again tomorrow and post my results. This still doesn't negate the problem, though. Unless I'm mistaken, each value in the i2c_enable corresponds to each card, right? So I should be using two numbers like I am. So why isn't it listening to the second number? ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
