On Sat, 20 Dec 2003 09:08:50 -0800 (PST) Alex Deucher <[EMAIL PROTECTED]> wrote:
> as I recall the savage hardware needs a tiled framebuffer for the 3d > engine, but 2d engine can use linear or tile. Most drivers use linear, > so that's probably what the savage driver did originally, now that it > has 3D support you need to get 2d working in tile mode for both to > work. there may just be some place some where in the setup or accel > code where the driver forgot to switch it back to one or the other. We had a similar problem with the 2D driver on the savage-1_0_0-branch. Accelerated stuff worked just fine for me but direct frame buffer access was broken. It turned out to be quite simple to fix. However, this fix didn't work for Maximo, so I suspect that on Savage4 either 2D acceleration is broken with tiling or tiling works differently and direct frame buffer was still broken. Maximo, you can find out which of the above is true by disabling 2D acceleration and see if direct fb access works. Maybe disabling 2D accel would be a workaround until we fix the real problem. Felix > > Alex ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, Kühling (_____\Ä/____/ /_____/ /________) just not everything [EMAIL PROTECTED] \___/ \___/ U at the same time. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
