I didn't quite realise what the above commit tells us (forgot to check
when that commit was in the source, and whether it was included in
2.1.1: Answer.. it was)
commit f3168e3b0c5664a322ca6bb1c81fc94844cb30ab
Author: Eric Anholt <[EMAIL PROTECTED]>
Date: Wed May 2 14:08:30 2007 -0700
Disable non-working GTT decoding on i830, and fix map/unmap of GTT.
commit a4f1a7872f6f959bb4bc6568face710bee3589de
Author: Eric Anholt <[EMAIL PROTECTED]>
Date: Mon Apr 30 17:13:09 2007 -0700
Allow physical-memory allocations within stolen memory.
So, eeejay, I'm not entirely surprised there was a regression at the
a4f1... commit, the more interesting question.. was it fixed again later
with f3168... (and broken again at some later point?)
--
screen artifacts after resume, part row of pixels in error (945GM)
https://bugs.launchpad.net/bugs/91966
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
