diff options
| author | Antonino A. Daplas | 2005-08-15 15:29:11 +0200 |
|---|---|---|
| committer | Linus Torvalds | 2005-08-15 18:59:39 +0200 |
| commit | 3edea4833a1efcd43e1dff082bc8001fdfe74b34 (patch) | |
| tree | 9c1fcbc1bf513123f9612153c40582d2ff464d07 /arch/ia64/kernel/acpi.c | |
| parent | [PATCH] intelfb: Do not ioremap entire graphics aperture (diff) | |
| download | kernel-qcow2-linux-3edea4833a1efcd43e1dff082bc8001fdfe74b34.tar.gz kernel-qcow2-linux-3edea4833a1efcd43e1dff082bc8001fdfe74b34.tar.xz kernel-qcow2-linux-3edea4833a1efcd43e1dff082bc8001fdfe74b34.zip | |
[PATCH] intelfb/fbdev: Save info->flags in a local variable
Reported by: Pavel Kysilka (Bugzilla Bug 5059)
The intelfb driver does not keep resolution set with fbset after
switching to anot console and back.
Steps to reproduce:
initial options: tty1,tty2 - 1024x768-60
1) tty1 - fbset after booting (1024x768-60)
2) tty1 - fbset 800x600-100
tty1: 800x600-100
3) swith to tty2, swith to tty1
tty1: 1024x768-60 (the same resolution as default from kernel booting)
This bug is caused by intelfb unintentionally destroying info->flags in
set_par(). Therefore the flag, FBINFO_MISC_USEREVENT used to notify
fbcon of a mode change was cleared causing the above problem. This bug
though is not intelfb specific, as other drivers may also be affected.
The fix is to save info->flags in a local variable before calling any
of the driver hooks. A more definitive fix (for post 2.6.13) is to
separate info->flags into one that is set by the driver and another that
is set by core fbdev/fbcon.
Signed-off-by: Antonino Daplas <adaplas@pol.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'arch/ia64/kernel/acpi.c')
0 files changed, 0 insertions, 0 deletions