1) I had problems with video turning green after 1 hour,
but later I tried on another machine and video worked
perfectly. I did not try the original machine with
a different slot or other reconfigurations.
2) I have never had problem with the audio, and
I use sound both directly off the card DMA (use
aumix on a mixer device to set record on the
video channel and then grab off of that dsp.
I never figured out how to do this automatically,
but it comes up at boottime on the video line
full volume/recording enabled).
3) Both internal DMA (/dev/dsp1) and soundcard
(TV audio out to /dev/dsp0) work, though only 1
channel. I use
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-12 snd-pcm-oss
options saa7134 video_nr=1 ts_nr=1 vbi_nr=1 radio_nr=1 card=2
mixer_nr=3 gbuffers=32 dsp_nr=1
pre-install saa7134 modprobe -k tuner;modprobe -k tda9887
(probably that tuner bit is wrong/unused)
If I changed from line1 or line2 to video,
I need to change the channel with v4lctl or xawtv
to get the sound to start coming out. Normally
there's no reason to change.
4) There is some conflict between the saa7134-0.10
code and the latest bttv code - I had to use an
earlier version of bttv to support my 2 cards at
the same time. Otherwise, lockups and other weirdness.
Stane Gruden wrote:
> Hi,
>
> Thanks to Barrie I managed to compile the kernel and install
> drivers for my FlyVideo 3000 with no problems at all. Of course,
> the problems with the card already mentioned in this list
> appeared, especially 'no sound problem' but sometimes video
> makes problems as well. Sometimes everything even works!
>
> I think all the workarounds mentioned in this list are not
> the right solution to these problems - the drivers' code
> will have to be altered. To do this, better documentation
> than that from Philips's site is needed. I am sure that
> existing drivers could only be written with such a documentation
> available. Could this documentation be publicly available?
> I am willing to dig into the code, but with no doc this is
> mission impossible.
>
> Something is wrong with the card
> initialization, otherwise the problems would always appear
> the same. Is there some way to just reset
> the card into a known state that could then be
> triggered via ioctl and start all over again in case the user
> sees that the card is not working properly?
>
> Is anyone at this moment doing something that would solve
> known problems?
>
> -- Stane.
>
>
>
> _______________________________________________
> Video4linux-list mailing list
> Video4linux-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/video4linux-list
--
Bill Eldridge
Radio Free Asia
bill@xxxxxxx
