summaryrefslogtreecommitdiff
path: root/src/socket-proxy
diff options
context:
space:
mode:
authorJan Engelhardt <jengelh@inai.de>2015-02-24 17:49:02 +0100
committerDavid Herrmann <dh.herrmann@gmail.com>2015-03-06 15:00:40 +0100
commita52750d1483ff139df33149afc0b675531e9cd79 (patch)
tree21dc1d719865329d66884ebb33ea3f9035f1760c /src/socket-proxy
parent9d10cbee89ca7f82d29b9cb27bef11e23e3803ba (diff)
vconsole: match on vtcon events, not fbcon ones
I observe that upon loading of framebuffer drivers, I do not get the desired system font, but the kernel-level defaults (usually lib/fonts/font_8x16.c, but your mileage may vary depending on kernel config and boot options). The fbcon driver may be loaded at a time way before the first framebuffer device is active, such that the vconsole setup helper runs too early. The existing rule is non-fitting. The going live of the fbcon kernel component does not indicate the proper time at which to load the visuals, which really ought to be done when a new vtcon object comes into existence. (The font table is a per-vtcon property.)
Diffstat (limited to 'src/socket-proxy')
0 files changed, 0 insertions, 0 deletions