> In any case, vl.c's saving arrangements do save the buffer in
> phys_ram_base - but that isn't what the guest sees in the VGA memory
It doesn't matter what the guest physical mappings (if any) are.
> area. The guest sees the vga memory-mapped IO registers (whose
> meaning _is_ generally saved
andrzej zaborowski writes ("Re: [Qemu-devel] [PATCH] ioemu/qemu vga: save and
restore vram buffer (revised)"):
> On a second look there's something else I don't understand. The vram
> window is in RAM in stdvga, it's inside phys_ram_base, and the entire
> ch
Hi,
On 12/12/2007, Ian Jackson <[EMAIL PROTECTED]> wrote:
> The first one (stdvga-save-vram-update.patch) is against current
> xen-unstable tip (which now includes my previous version) and should
> be applied there.
>
> The second (stdvga-save-vram-take2.patch) is a fresh diff against the
> same q
andrzej zaborowski writes ("Re: [Qemu-devel] [PATCH] ioemu/qemu vga: save and
restore vram buffer"):
> On 10/12/2007, Ian Jackson <[EMAIL PROTECTED]> wrote:
> > I have reinterpreted the `is_vbe' byte, which is related to
> > CONFIG_BOCHS_VBE, as a general
On 10/12/2007, Ian Jackson <[EMAIL PROTECTED]> wrote:
> The existing stdvga driver from xen-unstable tools/ioemu/hw/vga* does
> not save the emulated VGA memory contents. The symptoms include video
> malfunction after restore, including black screen (which can often be
> fixed by asking the guest
The existing stdvga driver from xen-unstable tools/ioemu/hw/vga* does
not save the emulated VGA memory contents. The symptoms include video
malfunction after restore, including black screen (which can often be
fixed by asking the guest to redraw) but also missing font setup etc.
The attached patch
