Liav A 883b0f1390 Kernel/Graphics: Restore VirtIO GPU framebuffer console functionality ... This has been done in multiple ways: - Each time we modeset the resolution via the VirtIOGPU DisplayConnector we ensure that the framebuffer is updated with the new resolution. - Each time the cursor is updated we ensure that the framebuffer console is marked dirty so the IO Work Queue task which is scheduled to check if it is dirty, will flush the surface. - We only initialize a framebuffer console after we ensure that at the very least a DisplayConnector has being set with a known resolution. - We only call GenericFramebufferConsole::enable() when enabling the console after the important variables of the console (m_width, m_pitch and m_height) have been set.		2022-12-31 05:13:21 -07:00
..
Console.cpp	Kernel/Graphics: Restore VirtIO GPU framebuffer console functionality	2022-12-31 05:13:21 -07:00
Console.h	Kernel/Graphics: Restore VirtIO GPU framebuffer console functionality	2022-12-31 05:13:21 -07:00
DisplayConnector.cpp	Kernel/Graphics: Restore VirtIO GPU framebuffer console functionality	2022-12-31 05:13:21 -07:00
DisplayConnector.h	Kernel/Graphics: Restore VirtIO GPU framebuffer console functionality	2022-12-31 05:13:21 -07:00
GPU3DDevice.cpp	Kernel/Graphics: Propagate errors properly around in the VirtIO driver	2022-12-19 10:19:57 +00:00
GPU3DDevice.h	Kernel/Graphics: Increase VirtIO GPU transfer buffer size to 4MiB	2022-12-26 09:39:20 +01:00
GraphicsAdapter.cpp	Kernel/Graphics: Restore VirtIO GPU framebuffer console functionality	2022-12-31 05:13:21 -07:00
GraphicsAdapter.h	Kernel/Graphics: Propagate errors properly around in the VirtIO driver	2022-12-19 10:19:57 +00:00
Protocol.h	Everywhere: Prefix 'TYPEDEF_DISTINCT_ORDERED_ID' with 'AK_'	2022-07-22 23:09:43 +01:00