Lives In A Box wrote:
Mark Adams wrote:
Most users of DirectFB with unichrome graphics have concluded that the
VIA framebuffer does not work very well. That is the reason that
there is a framebuffer driver in DirectFB's CVS. This has quite a
complicated history but provides all the functions needed for good
performance with DirectFB. However, it may well lack some things
necessary for the CN400 chipset.
In a later email, Hans-Erik.Floryd implies he has successfully used
the DirectFB version of viafb with the CN400 so you might like to try
his patch.
I've tested the patch (thanks Hans-Erik.Floryd), and while it does seem
to detect the hardware, I can't seem to get a working framebuffer on my
monitor (I've not tried it with the TV out yet to see if thats working,
as I wont be using that). I'm going to try an earlier Kernel and then a
later one..maybe I'm just that unlucky! It also seems to barf if you
compile it in and try and start with a viafb console.
I use kernel 2.6.13 with viafb compiled as a module. It doesn't seem to
like being built in or started via the kernel arguments. Loading it
after the kernel is up and running works ok (although the screen is
initalised to white, but this is cleared as it updates).
I also found that I couldn't load the vesafb modules first and then the
viafb, as the viafb module had problems allocating memory. So currently
I boot with no framebuffer, and then load viafb via /etc/modules.autoload.d
/Hans-Erik
If you can get that to work, it'll be a lot easier than trying to
support ypan etc. in VIA's code. Even when you've done that, you
won't have everything you need because I don't think VIA's own driver
supports the WAITFORVSYNC ioctl either.
Ypan is/appears to be in their code already (untested), but only when
acceleration is used. In their software handling side (viafb noaccel=0
which is the default, when theres no actual acceleration to the basic
functions) it does nothing from what I can see - I imagine this is
because they don't support it, or expect you to use the accelerated
version. WAITFORVSYNC appears to be missing, but I imagine I could add
that if I really had to. The main problem with their driver is that the
HW acceleration doesnt seem to work (well for me anyway) I just get a
corrupt console. But it does compile in, and brings me a nice shiny
console that works fine with directfb, unless you want double buffering.
Mark
It's nice to know there are people around who want to help..the via
forums are almost completely useless!
LiaB
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
