From: Gianni Tedesco <gianni@scaramanga.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] BIOS checksums?
Date: Mon, 21 Jun 2004 15:33:50 +0100 [thread overview]
Message-ID: <1087828431.9477.347.camel@sherbert> (raw)
In-Reply-To: <20040621142926.40693.qmail@web60201.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
On Mon, 2004-06-21 at 07:29 -0700, Piotr Krysik wrote:
> Are you talking about using proprietary closed-source BIOS-es of real
> PC? They are usually very hardware-depended.
>
> In fact I started a project to use QEMU to monitor interactions
> between guest OS and real hardware (similar to "PCI Host/Proxy" by
> Gianni Tedesco, but not limited to PCI hardware). At this point I have
> prof of concept prototype that successfully boots proprietary BIOS of
> my PC up to the point of testing the RAM.
Sounds very interesting, are you doing this just generically by just
hooking up virtual i/o ports to real ones? I guess to get a BIOS running
it takes more than that?
Doesn't the BIOS use the PMC config space to query DRAM bank layout? If
so that shouldn't be too difficult to modify hw/pci.c to do the right
thing(tm)....
--
// Gianni Tedesco (gianni at scaramanga dot co dot uk)
lynx --source www.scaramanga.co.uk/scaramanga.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-21 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 15:04 [Qemu-devel] BIOS checksums? Hetz Ben Hamo
2004-06-21 14:29 ` Piotr Krysik
2004-06-21 14:33 ` Gianni Tedesco [this message]
2004-06-21 22:10 ` Piotr Krysik
2004-06-22 17:35 ` Gianni Tedesco
2004-06-22 23:31 ` Piotr Krysik
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=1087828431.9477.347.camel@sherbert \
--to=gianni@scaramanga.co.uk \
--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.