Thanks again for the reply Tyler, On Wed, 23 Feb 2005 10:01:40 -0500, Tyler Trafford <[EMAIL PROTECTED]> wrote: > lewis shobbrook <[EMAIL PROTECTED]> wrote: > > I've found some strange anomolies with the current 0.3.2d & e drivers. > > When cardtype=1 is passed dmesg lists ivtv showing the card as > > pvr-150. > > E.g. modprobe ivtv cardtype=1 ivtv_std=2 tuner=38 > > When specifying cardtype=2 ivtv lists the device as a pvr-250. > > Ah, those directions must not have been updated when the 150 was > added. You want cardtype=2.
Ah ha.. > > When using the 0.3.2d the pvr-250mce functions with both cardtype=1 & > > cardtype=2 settings with a variety of tuners, but without audio. > > Audio came alive for a brief period using cardtype=1 ivtv_std=2 > > tuner=52, I cahnged the setting to cardtype=1 ivtv_std=2 tuner=38 and > > the audio persisted. I then tried mythTV which hung after 2-3 secs of > > TV. I unloaded and reloaded the drivers to reset the myth "freeze" > > That seems to happen if mythTV is unable to tune. I had it working at one stage without audio, I think something has changed in the mifration to 0.17 > > however, reloading the ivtv module using identical parameters resulted > > in the loss of the audio(which I have been unable to retrieve even > > with a reboot). It appears that an audio function on the card is > > flapping somehow. I suspect as the card is relatively new,that the > > cards architecture is slightly different than previous pvr-250mce > > releases. > > Clearly the drivers has the capcity to "drive"; the inconsitency of > > the results from the tests I've thrown at it are confusing. > > Something I've noticed when switching tuners, or module versions, or > firmware- often you need to shutdown your machine to make sure the old > settings are really cleared from the card. I sometimes disconnect > power when I want to make sure. It turns out that I needed to modprobe wm8775 alone prior to inserting ivtv. If I do this first most tuner combinations work for both NTSC/PAL & cardtypes 1&2. I have noted a firmware lock-up when using cardtype=2 from a fresh start. Feb 24 09:47:54 luigi kernel: ivtv: 1000 ms time out waiting for firmware Feb 24 09:47:54 luigi kernel: ivtv: Failed api call 0x000000d2 with result 0xfffffff0 Feb 24 09:47:55 luigi kernel: ivtv: i2c client addr: 0x40 not found! Feb 24 09:47:55 luigi kernel: ivtv: i2c client addr: 0x40 not found! Feb 24 09:47:59 luigi kernel: ivtv: No Free Mailbox for cmd 0x000000c7 after 100 tries! Feb 24 09:47:59 luigi kernel: ivtv: Mailbox[0] 0x000000d3 flags 0x00000003 Feb 24 09:47:59 luigi kernel: ivtv: Mailbox[1] 0x000000c9 flags 0x00000003 Feb 24 09:47:59 luigi kernel: ivtv: Mailbox[2] 0x000000d6 flags 0x00000003 Feb 24 09:47:59 luigi kernel: ivtv: Firmware UNRESPONSIVE when trying cmd 0x000000c7!!! I can recover from this by reinserting ivtv using cardtype=1. Cardtype=2 can also produce ivtv: i2c client addr: 0x40 & 0x21 not found! errors (still works though?) When using cardtype=1 I get... i2c_adapter i2c-0: I2C level transfers not supported & cx25840: I2C write failed, length 3, ret -38 (again it still works) Cheers & thanks again, Lew ------------------------------------------------------- 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_id=6595&alloc_id=14396&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
