On Friday 26 January 2007 13:56, Nicolas Huillard wrote:
> Laz a écrit :
> >>Is there anything in DirectFB which has chagned drastically for the
> >>Unichrome driver?
> >
> > Sorted it: I had pixelformat=ARGB instead of AiRGB in
> > /etc/directfbrc. Looks like a check for the pixel format has been
> > added when setting DLOP_ALPHACHANNEL! Not sure quite when I added
> > that, or whether I even need it now!
>
> In my case, ARGB works and AiRGB leads to no video on the screen,
> except when the OSD is openned (softdevice 0.3.1).
> IIRC, this is softdevice change. Not DirectFB.
>
> Here's my /etc/directfbrc :
>
> mode=720x576
> depth=32
> pixelformat=ARGB
> sync
> unichrome-revision=3
> no-vt
>
> What is this "sync" option (setting or unsetting it doesn't change the
> field parity artifacts on TV.
man directfbrc:
[no-]sync
Flushes all disk buffers before initializing DirectFB. This can
be useful if you working with experimental device drivers and
expect crashes. The default is not to sync.
It's whether it syncs the disk buffers before initialising DirectFB and
has nothing to do with the actual output.
Here's my /etc/directfbrc:
mode=720x576
depth=32
pixelformat=AiRGB
disable-module=lirc
disable-module=joystick
disable-module=cle266
disable-module=linux_input
no-vt
unichrome-revision=17
Won't be able to see if I actually have any video until I get home,
though!
Cheers,
Laz
_______________________________________________
Softdevice-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/softdevice-devel
