From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/3] update seabios to 1.8.2, add virtio-vga vgabios
Date: Wed, 17 Jun 2015 10:57:16 +0200 [thread overview]
Message-ID: <1434531436.5549.29.camel@redhat.com> (raw)
In-Reply-To: <55813190.4070207@msgid.tls.msk.ru>
On Mi, 2015-06-17 at 11:36 +0300, Michael Tokarev wrote:
> 17.06.2015 10:38, Gerd Hoffmann wrote:
> []
> > pc-bios/vgabios-cirrus.bin | Bin 37888 -> 38400 bytes
> > pc-bios/vgabios-qxl.bin | Bin 38400 -> 38400 bytes
> > pc-bios/vgabios-stdvga.bin | Bin 38400 -> 38400 bytes
> > pc-bios/vgabios-virtio.bin | Bin 0 -> 38400 bytes
> > pc-bios/vgabios-vmware.bin | Bin 38400 -> 38400 bytes
> > pc-bios/vgabios.bin | Bin 38400 -> 38400 bytes
>
> What's the diff. between stdvga, virtio and vmware vgabioses?
> Is it just the PCI vendor/device IDs with the same code?
Yes.
> Maybe it'd be better to have just one bios but patch the
> blob on load? With simple ROMs (without nested parts like
> for the pxe efi/bios combined ROMs) it should be easy.
"should be easy". Famous last words ;)
Don't feel like experimenting with it with the freeze just around the
corner. Also: why? Disk space? Save a few kb in the age of TB disks?
cheers,
Gerd
next prev parent reply other threads:[~2015-06-17 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 7:38 [Qemu-devel] [PULL 0/3] update seabios to 1.8.2, add virtio-vga vgabios Gerd Hoffmann
2015-06-17 7:38 ` [Qemu-devel] [PULL 1/3] update seabios submodule to release 1.8.2 Gerd Hoffmann
2015-06-17 7:38 ` [Qemu-devel] [PULL 2/3] tag our seabios builds Gerd Hoffmann
2015-06-17 7:38 ` [Qemu-devel] [PULL 3/3] update seabios and vgabios binaries Gerd Hoffmann
2015-06-17 8:36 ` [Qemu-devel] [PULL 0/3] update seabios to 1.8.2, add virtio-vga vgabios Michael Tokarev
2015-06-17 8:57 ` Gerd Hoffmann [this message]
2015-06-17 11:27 ` Peter Maydell
2015-06-17 11:44 ` Peter Maydell
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=1434531436.5549.29.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=mjt@tls.msk.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.