Bug detailed description:
Bisect shows 6f916ffec7767eeab62132eb6575043969104c81 is the first bad commit.
Author: Michel Daenzer <email@example.com>
AuthorDate: Sun Dec 18 18:29:39 2011 +0200
Commit: Keith Packard <firstname.lastname@example.org>
CommitDate: Mon Dec 19 22:31:01 2011 -0800
dri2: Always re-generate front buffer information when asked for it.
Otherwise we might keep stale cached information, e.g. after the driver
performed page flipping.
This is part of the fix for
Signed-off-by: Michel DÃ¤nzer <email@example.com>
Reviewed-by: Ville SyrjÃ¤lÃ¤ <firstname.lastname@example.org>
Reviewed-by: Mario Kleiner <email@example.com>
Signed-off-by: Keith Packard <firstname.lastname@example.org>
1. start X
2. ./oglconform -z -s -suite all -v 2 -test drawbuffer basic.allCases
Not sure what's going on, and I probably won't be able to investigate anytime soon. Feel free to revert.
Chris, any idea?
On q35 with an up-to-date build:
$ ./oglconform -z -s -suite all -v 2 -test drawbuffer basic.allCases
Intel Conformance passed.
Total Passed : 32
Total Failed : 0
Total Not run: 0
Something amiss (or implicit?) in the reproduction steps?
Created attachment 58577 [details] [review]
Skip invalidation unless the WindowPixmap changes
Mesa should also be intelligent enough to squash this change as well, the logic is all there to not swap if the texture matches.
any action plan, Chris, Ian?
Created attachment 63858 [details] [review]
Flush pending writes to FakeFront
Please confirm that this is seen on an SNB or newer platform.
I don't think it impacts new platforms. Closing as won't fix.