From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Kevin O'Connor <kevin@koconnor.net>,
seabios <seabios@seabios.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [SeaBIOS] solaris x86 in qemu? [bisected]
Date: Mon, 17 Jun 2013 08:13:17 +0200 [thread overview]
Message-ID: <51BEA8FD.1010707@redhat.com> (raw)
In-Reply-To: <51BB2528.8070002@msgid.tls.msk.ru>
Hi,
> Can I use current seabios with old qemu which does not provide
> the separate ACPI tables? For example, does current bios contain
> these tables too, so they're both separate and embedded?
Yes. The i440fx acpi tables are compiled in and will be used as
fallback in case qemu doesn't provide acpi tables.
> And the reverse, can I use old bios with new qemu which do provide
> the separate tables?
Yes. Old seabios will simply ignore the qemu-provides tables and use
the compiled-in ones. That is limited to the 'pc' machine type though,
q35 will not work this way. q35 needs other tables and this was the
reason to let qemu provide the tables in the first place.
cheers,
Gerd
next prev parent reply other threads:[~2013-06-17 6:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 7:51 [Qemu-devel] solaris x86 in qemu? Michael Tokarev
2013-06-13 20:32 ` [Qemu-devel] solaris x86 in qemu? [bisected] Michael Tokarev
2013-06-13 23:47 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2013-06-14 6:10 ` Michael Tokarev
2013-06-14 12:36 ` Gerd Hoffmann
2013-06-14 14:14 ` Michael Tokarev
2013-06-15 1:40 ` Kevin O'Connor
2013-06-17 6:13 ` Gerd Hoffmann [this message]
2013-06-16 10:07 ` Michael Tokarev
2013-06-16 15:30 ` Kevin O'Connor
2013-06-17 7:40 ` Laszlo Ersek
2013-06-13 21:44 ` [Qemu-devel] solaris x86 in qemu? Brad Smith
2013-06-14 5:42 ` Michael Tokarev
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=51BEA8FD.1010707@redhat.com \
--to=kraxel@redhat.com \
--cc=kevin@koconnor.net \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).