qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: vgabios + qemu: issues and plans.
Date: Thu, 06 May 2010 11:35:24 +0200	[thread overview]
Message-ID: <4BE28D5C.4060001@redhat.com> (raw)
In-Reply-To: <4855E2D8011C47A797DC2460DC9919F7@FSCPC>

   Hi,

>> First, I'd like to be able to load the vgabios via PCI ROM bar on all
>> pci vga cards (stdvga, vmware, soon qxl). The PCI ID in the bios has
>> to match the PCI ID of the card, so we'll need a bunch of vga bios
>> binaries, all identical except for the PCI ID. Or we need some kind of
>> binary patching. Otherwise seabios will not load them from the PCI ROM
>> bar.
>
> vgabios could be build multiple times with PCIBIOS set and VENDOR_ID and
> DEVICE_ID supplied from the Makefile like it's already done with
> VGABIOS_DATE.

Yes, something like this I have in mind.

Works for stdvga and qxl.  vmware fails as it has the memory at pci 
region 1 (region 0 has ioports) and it seems vgabios isn't prepared to 
handle that ...

Anyone knows what the best place to send patches to is? 
vgabios-developers list @ savannah looks pretty much dead.  It has one 
(!) message in 2009 which is an unanswered question.

Or is upstream dead anyway and we should just go with 
http://git.qemu.org/vgabios.git/ ?

cheers,
   Gerd

  reply	other threads:[~2010-05-06  9:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 13:38 [Qemu-devel] vgabios + qemu: issues and plans Gerd Hoffmann
2010-05-05 19:56 ` [Qemu-devel] " Sebastian Herbszt
2010-05-06  9:35   ` Gerd Hoffmann [this message]
2010-05-06 18:09     ` Sebastian Herbszt
2010-05-06 19:37       ` Gerd Hoffmann
2010-05-06 20:19         ` Sebastian Herbszt
2010-05-06 20:27           ` Gerd Hoffmann
2010-05-06 10:03 ` [Qemu-devel] " Isaku Yamahata
2010-05-06 11:08   ` Gerd Hoffmann
2010-05-06 18:23     ` [Qemu-devel] " Sebastian Herbszt

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=4BE28D5C.4060001@redhat.com \
    --to=kraxel@redhat.com \
    --cc=herbszt@gmx.de \
    --cc=qemu-devel@nongnu.org \
    /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).