[vdr] Re: Softdevice 0.0.7pre2 crash w/ DFB, CLE266

[Nicolas Huillard <nhuillard@ghs.fr>]

Stefan Lucke wrote:

> On Sonntag, 1. August 2004 16:24, Nicolas Huillard wrote:
>
> > Nicolas Huillard wrote:
> >
> >
> > > Next step : I'l try today's CVS DirectFB version...
> > > I think you use CVS HEAD from 200404, isn't it ?
> > After a cvs update and a lot of compile, it finally works (ie. does not 
> > throw an exception at startup).
> > I still have a few things to do (make sure DirectFB is good, reboot, 
> > wonder why softdevice asks to press a remote key at startup, find the 
> > best resolution/pixel format, wonder why some channels are so jerky, etc.)
>
> Some time (between 0.0.6 and 0.0.7pre1) dfb-out got its own remote so
> learning keys for this one should be ok.
While we're at it : I press keys on the remote, but nothing happens. I 
just have to wait for some timeout (10 seconds or so).
What exactly is expected here ?
The messages I have on the screen are in french : did you translate 
them, ot are the translations standard VDR ones ?

> Normal pixel-format should be
> I420 except you got "wrong colors ", then choose YV12. When stretchblit
> works accellerated then you could choose YUY2 which results in alpha
> blended OSD (works with matrox).
I420 is right, YV12 has wrong colors, and YUY2 won't stay selected on 
the menu : when I press "right", YUY2 appears and is replaced by YV12.
The following message appears on STDOUT :

(!!!)  *** ONCE [only copying/scaling blits supported for YUV in 
software] *** [../../../../src/gfx/generic/generic.c:3907 in gAcquire()]

> From the log (epia):
> [dfb] Accellerated Functions: FillRectange DrawRectange DrawLine FillTriangle Blit StretchBlit All
> stretchblit should work too, but actually it doesn't :-).
I420 gives a full transparent OSD, which is not always readable. What I 
understand is that semi-transparent OSD should be acheived with YUY2, 
that you can see on your Matrox, but I can't have on the EPIA ?

> In a way oddities go on with this board. When using "mode = 1280x1024" via directfbrc then
> it is running at full screen video. With "mode = 1024x768" OSD is as expected larger but
> video area is only in the upper left part of the screen (768x576 ??).
I got it working at 720x576, and the TV output is quite OK (I still have 
to connect it to a good TV, not the spare tiny one).

> OT: My opinion on these M10000 boards is, they are noisy, runreliable in networking
> (if networking works it depends on some magic if they try netboot or local
> disk boot, bios setting have no influence on that). So keep your fingers ....
Noisy : I removed the original heatsink + fan, and replaced it with a 
Zalman ZM-NB47J (north-bridge passive cooler), with a 8cm low-speed fan 
on top. This is much less noisy. I still have to publish photos of the 
hardware somewhere...
Unreliable : the ethernet port IS unreliable at initialisation. It works 
correctly after that. I think I didn't ever experienced problems before 
I stated tweaking with the video (no frame-buffer driver at all ~ no 
ethernet problems)

--
NH