Liav A 8554952690 Kernel + WindowServer: Re-define the interface to framebuffer devices ... We create a base class called GenericFramebufferDevice, which defines all the virtual functions that must be implemented by a FramebufferDevice. Then, we make the VirtIO FramebufferDevice and other FramebufferDevice implementations inherit from it. The most important consequence of rearranging the classes is that we now have one IOCTL method, so all drivers should be committed to not override the IOCTL method or make their own IOCTLs of FramebufferDevice. All graphical IOCTLs are known to all FramebufferDevices, and it's up to the specific implementation whether to support them or discard them (so we require extensive usage of KResult and KResultOr, together with virtual characteristic functions). As a result, the interface is much cleaner and understandable to read.		2021-10-27 07:57:44 +03:00
..
Console.cpp	Kernel + WindowServer: Re-define the interface to framebuffer devices	2021-10-27 07:57:44 +03:00
Console.h	Kernel/Graphics: Merge VirtIO GraphicsAdapter and VirtIO GPU code	2021-10-27 07:57:44 +03:00
FramebufferDevice.cpp	Kernel + WindowServer: Re-define the interface to framebuffer devices	2021-10-27 07:57:44 +03:00
FramebufferDevice.h	Kernel + WindowServer: Re-define the interface to framebuffer devices	2021-10-27 07:57:44 +03:00
GraphicsAdapter.cpp	Kernel/Graphics: Re-order parameters in VirtIO GraphicsAdapter methods	2021-10-27 07:57:44 +03:00
GraphicsAdapter.h	Kernel/Graphics: Rename GraphicsDevice => GenericGraphicsAdapter	2021-10-27 07:57:44 +03:00
Protocol.h	Kernel/Graphics: Merge VirtIO GraphicsAdapter and VirtIO GPU code	2021-10-27 07:57:44 +03:00