I just compiled framebuffer support in, though, and when switching to a
console, it's initially corrupt (similar pretty impressionistic graphics
that look like they're in the correct video mode for the
framebuffer/console), but within a half a second the framebuffer fixes
Also with framebuffer in use, after a suspend and resume from X 4.1.0, the
mouse cursor is replaced by a large block. With regular text-mode
consoles, this doesn't happen. Switching away and back to X restores the
cursor properly. This may be completely X's fault though.
Allegedly it's supposed to be bad to run non-framebuffer X-servers with
framebuffer console, is this really not considered stable or am I
mistaken? If X isn't going to restore previous graphics modes, it doesn't
seem to matter what mode the console was in, framebuffer or not, it still
needs to be fixed regardless.
I'm presuming then that this is something the regular console driver needs
to deal with?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/