summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorFrancisco Jerez2010-08-22 17:37:24 +0200
committerGreg Kroah-Hartman2010-09-04 02:29:03 +0200
commit9fc2b2d0cf743008d8f6be6293278f4ef61f09f3 (patch)
treedf7c30660be493aa9844da45f02c06097936f5b9 /MAINTAINERS
parentLinux 2.6.36-rc3 (diff)
downloadkernel-qcow2-linux-9fc2b2d0cf743008d8f6be6293278f4ef61f09f3.tar.gz
kernel-qcow2-linux-9fc2b2d0cf743008d8f6be6293278f4ef61f09f3.tar.xz
kernel-qcow2-linux-9fc2b2d0cf743008d8f6be6293278f4ef61f09f3.zip
vt: Fix console corruption on driver hand-over.
After 02f0777a0d6560eb995aade34a1b82f95c0452da "vc_origin" is no longer reset to the screen buffer before calling the con_init() hook of the new console driver. If the old driver wasn't using a fixed scanout buffer (e.g. the case of vgacon) "vc_origin" may be a pointer to a VRAM location, and its contents aren't guaranteed to be preserved after calling con_deinit() on the old driver and con_init() on the new driver, i.e. the subsequent console resize may fill the framebuffer with garbage. It can be reproduced in the transition from vgacon to the nouveau framebuffer driver: in that case the legacy VGA aperture "vc_origin" points to becomes unreadable after fbcon_init(). This patch reverts the mentioned commit. To avoid the problem it intended to fix, stop using "vc_scr_end" in vc_do_resize() to calculate how many rows we have to copy (actually the code looks simpler this way without the help of "vc_scr_end"). Signed-off-by: Francisco Jerez <currojerez@riseup.net> Cc: qiaochong <qiaochong@loongson.cn> Cc: Greg Kroah-Hartman <gregkh@suse.de> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Alan Cox <alan@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions