Mine too is labelled as NTSC. Interestingly enough there are a set of resistors that look as though they might indicate the version of the FlyVideo card. You can find these resistors in a row, just above the SAA7130/4 chip.
The nine positions are labelled GP1 .. GP9
I have 4.7k resistors (marked 472) in positions 1,3,5,8,9.
These resistors appear to be connected to part of the GPIO port on the SAA713x chip and so should be readable by the driver. Maybe if other people could report on their settings, we could make the driver smart enough to select the correct tuner (for the FV2k at least)
Philip
Shaun Jackman wrote:
Yes, on the side of the box there's the equivalent of a paper-based radio button, with TV Standard: NTSC(USA) selected, and Options: Remote Control selected. The name of the product is the LifeView FlyVIDEO2000. Can the tuner be changed on the fly? If so, that can be selected by v4lctl. I don't mind setting the tuner type on boot up. I'm not even sure the audio_clock change is necessary. I'll test that. It's only in there because that's the value the Windows driver was using (slurped with a PCI peek). The GPIO value is actually what I think made the difference to my audio. Any idea why?
Cheers, Shaun
On Thu March 27, 2003 00h34, you wrote:
Shaun Jackman <[EMAIL PROTECTED]> writes:
That will surely break for other users. Looks like there are- .audio_clock = 0x00200000, - .tuner_type = TUNER_LG_PAL_NEW_TAPC,
+ .audio_clock = 0x00187de7, // sdj
+ .tuner_type = TUNER_LG_NTSC_NEW_TAPC, // sdj
different pieces of hardware with the same label printed on it.
Either different revisions of the card or they sell different cards
in different countries (probably depending on the tv norm used). We need more than one entry for the flyvideo 2000 I guess.
As you mention NTSC in the subject: Is your card explicitly labeled as NTSC version?
-- video4linux-list mailing list Unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/video4linux-list
