diff options
author | Adam Jackson <ajax@redhat.com> | 2012-09-26 16:21:25 -0400 |
---|---|---|
committer | Adam Jackson <ajax@redhat.com> | 2012-09-26 16:21:25 -0400 |
commit | 104e3e067a7dcac143cb672fe42d56396ba6087b (patch) | |
tree | 5c04f7fd5efa325a359022494269c4140c0a5a79 /src/atipcirename.h | |
parent | 5eb7fec958bc6ba8a1a2b0be4916cac818866e1c (diff) |
Don't gratuitously disable Render when ShadowFBing
There's no reason to do this, and I am at a loss to explain why that was
ever done. The first instance of this logic comes from xfree86 (over 11
years ago!):
http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/drivers/ati/atiscreen.c.diff?r1=1.15&r2=1.16
Now, cfb never had Render support, so that might make some sense if
there was an intermediate uncommitted state where the driver used fb for
direct but cfb for shadowed. But that's really the only plausible
explanation I can think of.
Signed-off-by: Adam Jackson <ajax@redhat.com>
Diffstat (limited to 'src/atipcirename.h')
0 files changed, 0 insertions, 0 deletions