summaryrefslogtreecommitdiffstats
path: root/src/mesa/drivers/dri/i965/intel_screen.c
diff options
context:
space:
mode:
authorKenneth Graunke <kenneth@whitecape.org>2014-02-10 16:48:14 -0800
committerKenneth Graunke <kenneth@whitecape.org>2014-02-19 15:43:22 -0800
commit4af8c95783acb632befa40c5bfc7fc58b62873d0 (patch)
treead83e21f405157538f95e5869e7ef158dd221d8e /src/mesa/drivers/dri/i965/intel_screen.c
parent51145a24f7938a4d5575d8d9aa4f8afa369d836b (diff)
downloadexternal_mesa3d-4af8c95783acb632befa40c5bfc7fc58b62873d0.zip
external_mesa3d-4af8c95783acb632befa40c5bfc7fc58b62873d0.tar.gz
external_mesa3d-4af8c95783acb632befa40c5bfc7fc58b62873d0.tar.bz2
i965: Update physical width/height munging for 2x IMS MSAA.
I can't find any documentation to explain what ought to be done here, so I simply guessed based on the pattern I observed in the 4x/8x cases. It appears to work, but it could be totally wrong. I was able to find the Sandybridge PRM quote from the comments in the latest documentation: Shared Functions > 3D Sampler > Multisampled Surface Behavior. However, it only mentions 4x MSAA - not even 8x. After a substantial amount more digging, I was able to find a second page (incorrectly tagged) which confirmed the formulas in our code for 8x MSAA. However, that page didn't mention 2x MSAA at all. Signed-off-by: Kenneth Graunke <kenneth@whitecape.org> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
Diffstat (limited to 'src/mesa/drivers/dri/i965/intel_screen.c')
0 files changed, 0 insertions, 0 deletions