qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefan Weil <weil@mail.berlios.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Standard vga breakage
Date: Mon, 16 Nov 2009 13:12:48 -0600	[thread overview]
Message-ID: <4B01A430.1080107@codemonkey.ws> (raw)
In-Reply-To: <4B0061B2.2070207@mail.berlios.de>

Stefan Weil wrote:
> malc schrieb:
>   
>> On Sun, 15 Nov 2009, Gleb Natapov wrote:
>>
>>     
>>> On Sun, Nov 15, 2009 at 06:22:40PM +0300, malc wrote:
>>>       
>>>> On Sun, 15 Nov 2009, Blue Swirl wrote:
>>>>
>>>>         
>>>>> On Sun, Nov 15, 2009 at 3:25 AM, malc <av1474@comtv.ru> wrote:
>>>>>           
>>>>>> debian-503-i386-netinst.iso when booted on a machine with `-vga
>>>>>> std' just
>>>>>> shows black screen (after bios' setup screen)
>>>>>>             
>>>>> Just some observations:
>>>>> - if you press enter, installer starts and Linux is able to fix the
>>>>> display
>>>>> - the screen is fine with -bios pcbios.bin, so the issue is related
>>>>> to SeaBIOS
>>>>>           
>>>> Yes i forgot to mention that -bios works, also worth noting is that
>>>> before
>>>> the commit that fixed cirrus -bios hack also made it work.
>>>>         
>
>
> Here is a summary of my analysis of this problem:
>
> Graphics mode memory (ram 0xe0000000 ...) is not mapped
> in QEMU address space (which results in unassigned
> memory writes) for standard pci vga (-vga std), so users
> don't get vga display output with grub (in graphical mode),
> debian installer (in graphical mode) or similar boot software.
>   

0xe00... is the VBE mapping.  The VGABIOS assumes this mapping exists 
when using VBE.  Cirrus doesn't support VBE so it wouldn't be exposed there.

Does the following help:

diff --git a/hw/vga-pci.c b/hw/vga-pci.c
index 479ffb1..e273b8b 100644
--- a/hw/vga-pci.c
+++ b/hw/vga-pci.c
@@ -107,6 +107,12 @@ static int pci_vga_initfn(PCIDevice *dev)
                          PCI_BASE_ADDRESS_MEM_PREFETCH, vga_map);
      }
 
+#ifdef CONFIG_BOCHS_VBE
+    /* XXX: use optimized standard vga accesses */
+    cpu_register_physical_memory(VBE_DISPI_LFB_PHYSICAL_ADDRESS,
+                                 vga_ram_size, s->vga.vram_offset);
+#endif
+
      /* ROM BIOS */
      rom_add_vga(VGABIOS_FILENAME);
      return 0;

Regards,

Anthony Liguori

  parent reply	other threads:[~2009-11-16 19:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15  1:25 [Qemu-devel] Standard vga breakage malc
2009-11-15 10:20 ` Blue Swirl
2009-11-15 15:22   ` malc
2009-11-15 15:28     ` Gleb Natapov
2009-11-15 15:40       ` malc
2009-11-15 20:16         ` Stefan Weil
2009-11-15 20:37           ` Blue Swirl
2009-11-15 21:21           ` malc
2009-11-15 21:35             ` Blue Swirl
2009-11-16 18:21             ` Stefan Weil
2009-11-16 19:12           ` Anthony Liguori [this message]
2009-11-16 20:11             ` [Qemu-devel] [PATCH] vga-pci: Fix access to linear framebuffer Stefan Weil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B01A430.1080107@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=blauwirbel@gmail.com \
    --cc=gleb@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).