mirror of
https://github.com/RGBCube/serenity
synced 2025-05-31 17:18:11 +00:00
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.
This commit is contained in:
parent
cf1c8eb778
commit
34e9fa4d3b
14 changed files with 141 additions and 87 deletions
|
@ -38,7 +38,7 @@ public:
|
|||
|
||||
private:
|
||||
// ^File
|
||||
virtual const char* class_name() const { return "FramebufferDevice"; }
|
||||
virtual const char* class_name() const override { return "FramebufferDevice"; }
|
||||
|
||||
virtual bool can_read(const FileDescription&, size_t) const override final { return true; }
|
||||
virtual bool can_write(const FileDescription&, size_t) const override final { return true; }
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue