I have the latest cvs of directfb snapshots. Hardware is Epia M10000 and
viafb
seems to be correctly installed. Using VGA out. Fusion and debug options
are
enabled. No cle266 acceleration with libcle266. fb.modes is a copy
DirectFB.
Also I have busybox running.
However, df_xine --no-hwosd <MPEG2-filename> plays perfectly on the screen
(%95 CPU usage). Here is the output:
It seems to be hardware OSD is broken.
It's not really broken, it's just that it doesn't support the unichrome
hardware.
The reason is that df_xine finds that the video layer is capable of being
positioned below the primary layer and that the primary supports an alpha
channel. It therefore concludes that the primary is suitable for use as a
hardware OSD and moves the video plane behind it. Unfortunately, on the
unichrome hardware, the alphachannel of the primary is inverted when you use
it this way. This means that it must be configured with the special AiRGB
pixel format. df_xine however sets it to ARGB so everything that's supposed
to be transparent becomes opaque and vice versa. Hence you see a black
screen.
You can hack it if you like: search for 'Check for hardware subpicture' in
context.c and change the pixelformat it asks for to AiRGB. It should then
work on the unichrome.
Mark
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
