Re: xaa vs. WriteImage()

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Mar 7, 2008, at 13:03, Marc Aurele La France wrote:

> On Wed, 5 Mar 2008, Michael Lorenz wrote:
>>>> Otherwise, teaching the framebuffer layer to cope with a tiled  
>>>> framebuffer might be necessary in the long run, any pointers  
>>>> where to start?
>
>>> By design, this is a driver issue, as it is responsible for  
>>> providing VRAM access to the rest of the server.
>
>> Really. Now /that/ was helpful. Guess I'm on my own here.
>
> Not really.  This sounds like the kind of thing that is right up  
> the mibank screen wrapper's alley, assuming the tiles are all the  
> same size.

They are, always 64KB, depending on colour depth they're 512x128,  
256x128 or 128x128 pixels.

> mibank can interoperate with any other screen wrapper (including  
> XAA), except shadowfb, because the later is not a true screen wrapper.
>
> An example of the use of mibank can be found in ATIPreInit() and  
> ATIScreenInit().  Mine, that is;  not X.Org's lobotomised  
> imitations of same.

That sounds like it's what I need, thanks!

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBR9GKRspnzkX8Yg2nAQK9fwf/bNN+ZV299AWKn2PFcLi67H82tH6JoSTd
Ykhwgnai7fw8iMhY9wPIK3nbYkWaEE88CdQ8ZzEyYVGcPix+XDydo+kbs5xSPvNr
+t+YHWabiyopbq3YjE1QXUzh6xNwknMRSuGo6iEzWSUhQfxpwzPNwXePZK7+PDdw
1OhKu9QpI8jxLqQOoH5BYTteK8leuVx15E+m1hXhIgFbrdnIgzF7bSnD5SkJwqou
QEnXXGY+A1Tx60RfrZssFDSA1+TnINKN55jJFRBWCC5DYRitFpRdXVqfyZdPU4dt
aW5qVAPk8NJl2/+Ck5tJrjvoBqo8dxl7MCGjBqkDRMFS/To2XKYBYQ==
=kP5V
-----END PGP SIGNATURE-----