4 commits

Author	SHA1	Message	Date
Liav A	e301af8352	Everywhere: Purge all support and usage of framebuffer devices ... Long live the DisplayConnector object!	2022-05-05 20:55:57 +02:00
Liav A	4ff6150f1b	WindowServer: Use FB_IOCTL_FLUSH_HEAD to flush a framebuffer if possible ... This ioctl is more appropriate when the hardware supports flushing of the entire framebuffer, so we use that instead of the previous default FB_IOCTL_FLUSH_HEAD_BUFFERS ioctl.	2022-05-05 20:55:57 +02:00
Liav A	d9a2706079	DisplaySettings+WindowServer: Add support for display connector devices	2022-05-05 20:55:57 +02:00
kleines Filmröllchen	0acffa5ef4	WindowServer: Introduce the ScreenBackend concept ... The ScreenBackend is a thin wrapper around the actual screen hardware connection. It contains all the variables specific to that hardware and abstracts away operations that deal with controlling the hardware. The standard ScreenBackend implementor is HardwareScreenBackend, which contains all the existing frame buffer & ioctl handling code of Screen. I took this opportunity to introduce ErrorOr wherever sensible.	2022-04-21 13:41:55 +02:00