On Thu, Jul 18, 2002 at 07:44:27PM +0200, Denis Oliver Kropp wrote: > Thanks, I will apply the patch. It's a nice workaround for the dual head > framebuffer device problem.
So what about using some private value instead of FB_ACELE_MATROX_MGAG400? I was thinking of something like #define FOO_MATROX_CRTC2 (~0) Shouldn't clash with anything :) Then just set mrv->accelerator = FB_ACCEL_MATROX_MGAG400 and bail out before the bes functions are registered. I can whip up a patch if you want. Just tell me what to call FOO_MATROX_CRTC2 and where to put it (gfxcard.h maybe?). > I'm very unhappy about the current solution > of the matroxfb driver. I don't want to divide my 32mb fixed into 16mb and > 8mb (why 8?). No idea. 1280x1024x32bit is 5MB so it's that plus some scroll buffer. Fortunately it's placed at offset 24MB so there is at least some useable offscreen memory. > The best would be to have multi head support in DirectFB and > open and map both devices, but it would require a lot of work. I had the idea of representing the CRTC2 as another layer in DirectFB. Actually I got as far as duplicating most if not all of the fbdev.c stuff and getting it to compile. Didn't get anything working on it though. -- Ville Syrj�l� [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
