Hi,
I'm trying to get directfb running with a commell LV667 board (via
cn400 chipset), and am not having much success at the moment. I'm
running gentoo linux with kernel 2.6.14-rc4. I've tried a lot of
framebuffer drivers (infact, i've tried all the drivers I could find on
the net - -epia, patcher2k, viafb, and the directfb ones) and I can't
find one that works. Most of them don't work or refuse to provide a fb*
device. The only one that gives me anything close is the offical viafb
(linux-fbdev-kernel-src_20050726.tgz which I assume is the latest
version). With that driver, I get an fb0 device. But DirectFB wouldnt
use that, because it doesnt specify the accelerator ID, so I hardcoded
that (its kind of in viafb, but commented out and the wrong number!) and
had some success (~ only runs df_dok). The problem is it doesnt have
virtual yres + panning for the double/triple buffered used in the other
examples (and I will need atleast double buffering).
Upon further inspection, the viafb driver has hardware acceleration
defaulted to OFF. I've read previous emails on this list that say that
isnt important as DirectFB doesnt use that, and that appears to be 100%
correct, but studying the viafb source code, I can see that without
acceleration, the driver has no code for virtual yres + panning (in
fact, the function is there, but it appears to do nothing, most likely
why I'm having trouble with DirectFB). With acceleration, the virtual
yres and panning code appear to be there (with some code which imho
looks incorrect from a first glance), so I tried passing accel=1 to the
viafb module to get acceleration working but all I get is a scrambled
screen (using fbcon for the console) so I suspect theres a problem with
the hw acceleration in the driver, hence why its defaulted to off.
Running without fbcon (ie, so I get an accelerated fb0 device, but it
doesnt scramble my console) doesnt help any, as I get a messed up
DirectFB screen. I've also tried dropping back to an earlier kernel,
which someone suggested on the list which in my case didnt help.
I know this isnt really a DirectFB problem, but I have the viafb +
directfb working (kind of) all I need to do is sort out the ypan problem
and hopefully that would be enough, but I can't see an easy way to do
that. I see that acceleration is ON by default on the cle266 driver in
the DirectFB cvs (but that source code and the viafb source code are
poles apart, the offical viafb source is very hardcoded and messy -
sorry if someone on heres been working on it for via!). I'm just
wondering if anyone out there is working on the same thing or someone
who worked on the cle266 driver has some advice. I've spent quite a lot
of time playing with this, and I think it's a real shame that the via
support for linux is terrible. DirectFB is such a great idea..and not
only that, it's very well executed (I'm very impressed with the achived
speeds for this onboard chipset) and it's perfect for these particular
boards.
The good news is that DirectFB seems to be accelerating the graphics
functions fine and is surprisingly fast - great job everyone on DirectFB
and the drivers...Is there somewhere to send the df_dok output for my
board? Is it useful to anyone? I've tested it with hw and sw and theres
a major gulf between the two, although stretchblit with colourkey
appears to be the only function not accelerated???.
Fingers Crossed,
Lives In A Box
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
