Es schrieb Jan Eisner: > > > If you have the v4l2-api-2.4.19.diff applied, you should take the > > saa7134-0.1.11 stuff. > I did not do this, but the second variant, > -- applied to the kernel 2.4.19 > This is not what is suggested on www.bytesex.org. > I am not able to translate kernel 2.4.20, > should I upgrade also my gcc 3.x.y from RH8.0 ? > As far I know you should be able to compile with what you have. > > > > More interesting should be to use the patch from Jan. 17 for the 2.4.20 > > kernel and the saa7134-0.2.6-0 from the snapshots directory (Feb. 18). > I did > On 2.4.19? > > Make sure to rename/replace the duplicated modules in .../media/video to > > get the new ones in v4l2 loaded. > I did not make this, is it a mistake? > When should I do this? Before you modprobe -d -k the modules. This is only for 2.4.20, because the kernelpatch and the saa7134 are out of sync at the moment. This way you can make sure to have the latest code, when reporting problems. Read the Changes in saa7134-0.2.6. As far I know the FlyVideo 2000 has the saa7130 too. It's status is discussed below under 'SAA7134 xawtv flakey?'. On http://www.manli.com.hk/tv-tuner.html is written they use Philips or 'equivalent' chipsets, maybe some unexpected is there. > or is it the sequece like > this. Yes. Hermann --
