From: Andreas Bollhalder <bolle@geodb.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Writing to ROM-Range 0xC800-EFFF
Date: Tue, 26 Jul 2005 16:41:32 +0200 [thread overview]
Message-ID: <42E64B9C.8080202@geodb.org> (raw)
In-Reply-To: <20050725153925.GA24463@jbrown.mylinuxbox.org>
Hello Jim
Thank you for the tips. I will have a look into it. Would be nice if
QEMU could allow us to enable write access to the BIOS memory range
(shadow RAM) which isn't in use.
Andreas
Jim C. Brown wrote:
> On Tue, Jul 19, 2005 at 08:00:21PM +0200, Andreas Bollhalder wrote:
>
>>Hello
>>
>>What does I need to change in the source code of QEMU that it would be
>>possible to enable write access to the ROM adresses from 0xC800 up to
>>0xEFFF ? For instance, "UMBPCI.SYS"
>>(http://www.uwe-sieber.de/umbpci_e.html) can made this range
>>accessible for direct access if no BIOS-ROM is using it. The original
>>chipset which QEMU emulate (Intel 440FX) does allow this, but in QEMU,
>>it won't work.
>>
>>Any ideas ?
>>
>>Andreas
>>
>
>
> I'd recommend looking at i440fx_init() in hw/pci.c as a starting point.
>
> Also see if you can modify the constant IO_MEM_ROM.
>
next prev parent reply other threads:[~2005-07-26 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 17:11 [Qemu-devel] qemu/slirp bootp.c bootp.h ip_icmp.h libslirp.h Fabrice Bellard
2005-06-05 18:00 ` Andreas Bollhalder
2005-06-06 1:02 ` [Qemu-devel] " Ronald
2005-06-07 16:48 ` Andreas Bollhalder
2005-07-19 18:00 ` [Qemu-devel] Writing to ROM-Range 0xC800-EFFF Andreas Bollhalder
2005-07-25 15:39 ` Jim C. Brown
2005-07-26 14:41 ` Andreas Bollhalder [this message]
2006-02-08 19:33 ` [Qemu-devel] QEMU freeze with "Servicing hardware INT=0x08" Andreas Bollhalder
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=42E64B9C.8080202@geodb.org \
--to=bolle@geodb.org \
--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).