I am becoming frustrated, as no developer seems to read this list.
My subscription to mplayer-devel still waits for approval by the list
moderator.
I created a Bugzilla entry, but again nobody seems to care.
Is there anything else I can do to get the bugfix into SVN ?
---------- Weitergeleitete Nachricht ----------
Betreff: bug in configure script prevents ivtv cvidix driver from building
Datum: Dienstag, 30. Juni 2009
Von: Martin Dauskardt <md001@xxxxxx>
An: mplayer-users@xxxxxxxxxxxx
mplayer has three ivtv-related output drivers:
1. ivtv
This one is for using the hardware decoder (/dev/video16) of the PVR350 card
and works only with older ivtv drivers. Since 2.6.22 ivtv is in the kernel
and this driver is obsolete.
2. v4l2
This is for for using the hardware decoder of the PVR350 card with kernel >=
2.6.22
3. cvidix:ivtv
This is a totally different output driver and has nothing to do with the first
one, except it is also namend "ivtv". The cvidix subdriver "ivtv" uses the
YUV device (/dev/video48) of the PVR350, similar to a graphics card.
Unfortunately the mplayer configure script checks for a wrong dependency:
test "$_vidix_drivers" || _vidix_drivers="cyberblade ivtv mach64 mga
mga_crtc2 nvidia pm2 pm3 radeon rage128 s3 sh_veu sis unichrome"
test $_ivtv = "yes" || _vidix_drivers=`echo $_vidix_drivers | sed s/ivtv//`
The second check means that in case the first driver ("ivtv") is disabled, the
cvidix ivtv subdriver will also be removed from the list of drivers. This is
wrong!
The second test line should be removed without replacement.
-------------------------------------------------------
_______________________________________________
MPlayer-users mailing list
MPlayer-users@xxxxxxxxxxxx
https://lists.mplayerhq.hu/mailman/listinfo/mplayer-users
