summaryrefslogtreecommitdiff
path: root/linux-core/nv04_mc.c
diff options
context:
space:
mode:
authorJesse Barnes <jbarnes@nietzche.virtuousgeek.org>2007-12-07 14:24:45 -0800
committerJesse Barnes <jbarnes@nietzche.virtuousgeek.org>2007-12-07 14:24:45 -0800
commitbfc29606e4a818897eebca46a5e23bbe7bc3ce25 (patch)
treebdd4e239dc27e97b3e8083b20d2efe6147b86c19 /linux-core/nv04_mc.c
parentf1a99ddc14ebca303f20b6c23bd289fc887243ae (diff)
Fix pipe<->plane mapping vs. vblank handling (again)
If drmMinor >= 6, the intel DDX driver will enable vblank events on both pipes. If drmMinor >= 10 on pre-965 chipsets, the intel DDX driver will swap the pipe<->plane mapping to allow for framebuffer compression on laptop screens. This means the secondary vblank counter (corresponding to pipe B) will be incremented when vblank interrupts occur. Now Mesa waits for vblank events on whichever plane has a greater portion of the displayed window. So it will happly ask to wait for the primary counter even though that one won't increment. So we can fix this in either the DDX driver, Mesa or the kernel (though I thought we already had several times). Since current (and previous) userspace assumes it's talking about a pipe == plane situation and now uses planes when talking to the kernel, we should probably just hide the mapping details there (indeed they already are hidden there for vblank swaps), which this patch does. So as far as userland is concerned, whether we call things planes or pipes is irrelevant, as long as kernel developers understand that userland hands them planes and they have to figure out which pipe that corresponds to (which will typically be the same on 965+ hardware and reversed on pre-965 mobile chips).
Diffstat (limited to 'linux-core/nv04_mc.c')
0 files changed, 0 insertions, 0 deletions