aboutsummaryrefslogtreecommitdiff
path: root/arch/alpha/kernel/err_titan.c
diff options
context:
space:
mode:
authorStefan Bader <stefan.bader@canonical.com>2009-04-30 15:08:44 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2009-05-02 15:36:10 -0700
commitb175dc09285b36200a83b78baf167905181fb4e5 (patch)
treea361d51f7fe880feccfcf365cfed1fe549970a8a /arch/alpha/kernel/err_titan.c
parentae3abae64f177586be55b04a7fb7047a34b21a3e (diff)
vgacon: return the upper half of 512 character fonts
Uwe Geuder noted that he gets random bitmaps on a text console if he tried to type extended characters (like the e acute). For him everything above unicode 0xa0 was corrupted. After some digging there seems to be a little culprit in vgacon since the beginning of ages (well git). The function vgacon_font_get will store the number of characters correctly in font->charcount but then calls to vgacon_do_font_op(..., 0, 0). Which means only the lower 256 characters are actually stored to the fontdata. The rest is left untouched. So the next time that saved data is used, the garbled font appears. This happens on every switch between text consoles. Addresses https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355057 Signed-off-by: Stefan Bader <stefan.bader@canonical.com> Tested-by: Uwe Geuder <ubuntuLp-ugeuder@sneakemail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/alpha/kernel/err_titan.c')
0 files changed, 0 insertions, 0 deletions