Kernel: Abstract FramebufferConsole away from contiguous physical range

Currently, Kernel::Graphics::FramebufferConsole is written assuming that
the underlying framebuffer memory exists in physically contiguous
memory. There are a bunch of framebuffer devices that would need to use
the components of FramebufferConsole (in particular access to the kernel
bitmap font rendering logic). To reduce code duplication, framebuffer
console has been split into two parts, the abstract
GenericFramebufferConsole class which does the rendering, and the
ContiguousFramebufferConsole class which contains all logic related to
managing the underling vm object.

Also, a new flush method has been added to the class, to support devices
that require an extra flush step to render.

1 files changed, 4 insertions, 4 deletions

diff --git a/Kernel/Graphics/Console/Console.h b/Kernel/Graphics/Console/Console.h
index 9c3b7ec350..181db2e07f 100644
--- a/Kernel/Graphics/Console/Console.h
+++ b/Kernel/Graphics/Console/Console.h
@@ -54,10 +54,10 @@ public:
     virtual void hide_cursor() = 0;
     virtual void show_cursor() = 0;
 
-    virtual void clear(size_t x, size_t y, size_t length) const = 0;
-    virtual void write(size_t x, size_t y, char ch, Color background, Color foreground, bool critical = false) const = 0;
-    virtual void write(size_t x, size_t y, char ch, bool critical = false) const = 0;
-    virtual void write(char ch, bool critical = false) const = 0;
+    virtual void clear(size_t x, size_t y, size_t length) = 0;
+    virtual void write(size_t x, size_t y, char ch, Color background, Color foreground, bool critical = false) = 0;
+    virtual void write(size_t x, size_t y, char ch, bool critical = false) = 0;
+    virtual void write(char ch, bool critical = false) = 0;
 
     virtual ~Console() { }