From: "Sebastian Herbszt" <herbszt@gmx.de>
To: Gleb Natapov <gleb@qumranet.com>
Cc: bochs-developers@lists.sourceforge.net,
Kevin O'Connor <kevin@koconnor.net>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [Bochs-developers] BIOS, ACPI, CMOS and Windows EvenID: 4
Date: Sun, 24 Aug 2008 23:29:30 +0200 [thread overview]
Message-ID: <013101c90630$aa6c9750$0201a8c0@zeug> (raw)
In-Reply-To: 20080823162253.GB1999@minantech.com
Gleb Natapov wrote:
>> I am not sure writing arbitrary values to those registers is such a good idea. Some OS,
>> driver or application could rely on the information stored there.
> Currently nothing is written to memory configuration registers at all,
> so if there is an application that depend on this values to be correct
> it will be broken today too.
The 440fx supports 8MB-1GB of memory. The default value for the DRBx
registers is 01 (8MB). Bochs doesn't set the default value tho nor does the
rombios set the correct one, so those registers stay with 0 values.
If we set DRB0 and DRB1 to the CMOS values and keep DRB2 till DRB7 set
to 0 we violate the assumption that DRB7 contains the top of memory value.
In the all 0 case this is still somewhat valid.
>> Hard coding the hole start to 0xe0000000, like you did in your first patch, looks like the
>> easiest solution tho.
> Yes, and I think it is good enough. What is the procedure of pushing the
> patch into bochs tree?
Post it on the bochs patch tracker at sf
http://sourceforge.net/tracker/?atid=312580&group_id=12580&func=browse
- Sebastian
next prev parent reply other threads:[~2008-08-24 21:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 13:15 [Qemu-devel] BIOS, ACPI, CMOS and Windows EvenID: 4 Gleb Natapov
2008-08-20 23:23 ` [Qemu-devel] Re: [Bochs-developers] " Sebastian Herbszt
2008-08-21 5:34 ` Gleb Natapov
2008-08-21 11:45 ` Kevin O'Connor
2008-08-21 14:14 ` Gleb Natapov
2008-08-21 22:37 ` Sebastian Herbszt
2008-08-23 16:22 ` Gleb Natapov
2008-08-24 21:29 ` Sebastian Herbszt [this message]
2008-08-25 4:41 ` [Qemu-devel] " Stanislav Shwartsman
2008-08-21 22:47 ` [Qemu-devel] " Sebastian Herbszt
2008-08-24 15:45 ` Kevin O'Connor
2008-08-25 6:38 ` Gleb Natapov
2008-08-25 13:57 ` [Qemu-devel] " Stanislav Shwartsman
2008-08-25 14:00 ` [Qemu-devel] " Gleb Natapov
2008-08-31 19:34 ` Sebastian Herbszt
2008-08-31 20:04 ` Gleb Natapov
2008-08-31 21:19 ` [Qemu-devel] " Stanislav Shwartsman
2008-09-11 22:09 ` [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='013101c90630$aa6c9750$0201a8c0@zeug' \
--to=herbszt@gmx.de \
--cc=bochs-developers@lists.sourceforge.net \
--cc=gleb@qumranet.com \
--cc=kevin@koconnor.net \
--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).