Gerd Hoffmann 995b30179b hw/display: add ramfb, a simple boot framebuffer living in guest ram ... The boot framebuffer is expected to be configured by the firmware, so it uses fw_cfg as interface. Initialization goes as follows: (1) Check whenever etc/ramfb is present. (2) Allocate framebuffer from RAM. (3) Fill struct RAMFBCfg, write it to etc/ramfb. Done. You can write stuff to the framebuffer now, and it should appear automagically on the screen. Note that this isn't very efficient because it does a full display update on each refresh. No dirty tracking. Dirty tracking would have to be active for the whole ram slot, so that wouldn't be very efficient either. For a boot display which is active for a short time only this isn't a big deal. As permanent guest display something better should be used (if possible). This is the ramfb core code. Some windup is needed for display devices which want have a ramfb boot display. Signed-off-by: Gerd Hoffmann <kraxel@redhat.com> Tested-by: Laszlo Ersek <lersek@redhat.com> Message-id: 20180613122948.18149-2-kraxel@redhat.com Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>		2018-06-18 11:22:15 +02:00
..
bcm2835_fb.h	hw: Do not include "exec/address-spaces.h" if it is not necessary	2018-06-01 14:15:10 +02:00
bochs-vbe.h	vga: move bochs vbe defines to header file	2018-05-24 10:42:13 +02:00
dpcd.h	Clean up decorations and whitespace around header guards	2016-07-12 16:20:46 +02:00
ramfb.h	hw/display: add ramfb, a simple boot framebuffer living in guest ram	2018-06-18 11:22:15 +02:00
vga.h	hw/display/vga: extract public API from i386/pc to "hw/display/vga.h"	2017-12-18 17:07:02 +03:00
xlnx_dp.h	aux: Rename aux.[ch] to auxbus.[ch] for the benefit of Windows	2016-07-07 13:47:01 +01:00