summaryrefslogtreecommitdiff
path: root/drivers/block
diff options
context:
space:
mode:
authorDave Jones <davej@redhat.com>2006-09-10 21:12:20 -0400
committerDave Jones <davej@redhat.com>2006-09-10 21:12:20 -0400
commitedf03fb0575cbee2595a63374b17dc0921f2094a (patch)
treeb9964afc71abc0a6a786a0641380440a5bc8fe34 /drivers/block
parent08da3f413f6aa3eb48cfc5331c68e57393167fe5 (diff)
downloadlinux-stable-edf03fb0575cbee2595a63374b17dc0921f2094a.tar.gz
linux-stable-edf03fb0575cbee2595a63374b17dc0921f2094a.tar.bz2
linux-stable-edf03fb0575cbee2595a63374b17dc0921f2094a.zip
[AGPGART] Rework AGPv3 modesetting fallback.
Sometimes the logic to handle AGPx8->AGPx4 fallback failed, as can be seen in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=197346 The failures occured if the bridge was in AGPx8 mode, but the user hadn't specified a mode in their X config. We weren't setting the mode to the highest mode capable by the video card+bridge (as we do in the AGPv2 case), which was leading to all kinds of mayhem including us believing that after falling back from AGPx8, that we couldn't do x4 mode (which is disastrous in AGPv3, as those are the only two modes possible). Signed-off-by: Dave Jones <davej@redhat.com>
Diffstat (limited to 'drivers/block')
0 files changed, 0 insertions, 0 deletions