| commit | d5bfbaca39e9a700cabf4266247c93edeaf846de | |
| author | Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> | |
| Fri, 25 Jun 2021 16:35:53 +0000 (25 17:35 +0100) | ||
| committer | Philippe Mathieu-Daudé <f4bug@amsat.org> | |
| Fri, 2 Jul 2021 15:35:08 +0000 (2 17:35 +0200) | ||
| tree | 81ed5f38500c0507b366eb2ec1cc678b8c32965b | treesnapshot (tar.gz zip) |
| parent | 11984b18bb0b237440af18edb702f85aa8277efe | commitdiff |
g364fb: use RAM memory region for framebuffer
Since the migration stream is already broken, we can use this opportunity to
change the framebuffer so that it is migrated as a RAM memory region rather
than as an array of bytes.
In particular this helps the output of the analyze-migration.py tool which
no longer contains a huge array representing the framebuffer contents.
Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20210625163554.14879-2-mark.cave-ayland@ilande.co.uk>
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Since the migration stream is already broken, we can use this opportunity to
change the framebuffer so that it is migrated as a RAM memory region rather
than as an array of bytes.
In particular this helps the output of the analyze-migration.py tool which
no longer contains a huge array representing the framebuffer contents.
Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20210625163554.14879-2-mark.cave-ayland@ilande.co.uk>
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
| hw/display/g364fb.c | diffblobblamehistory |