From: Kevin O'Connor <kevin@koconnor.net>
To: "Alain Ribière" <alain_ribiere@yahoo.com>
Cc: "seabios@seabios.org" <seabios@seabios.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re : Re : [SeaBIOS] : Memory problem with Qemu/SeaBIOS
Date: Wed, 9 May 2012 21:19:45 -0400 [thread overview]
Message-ID: <20120510011945.GA24218@morn.localdomain> (raw)
In-Reply-To: <20120510004445.GA19059@morn.localdomain>
On Wed, May 09, 2012 at 08:44:45PM -0400, Kevin O'Connor wrote:
> On Wed, May 09, 2012 at 08:57:53AM -0700, Alain Ribière wrote:
> > I wonder what is the CDOS system at 0D4000... It seems a bit strange.
>
> Very odd. This is still controlled by seabios. Indeed, if I apply
> this (clearly incorrect) patch to seabios:
>
> diff --git a/src/shadow.c b/src/shadow.c
> index c0c8cc2..73c0670 100644
> --- a/src/shadow.c
> +++ b/src/shadow.c
[...]
Just for kicks, I tried a simple hack to try and reserve more memory
in the c/d/e-segments, and it seems to work for the image you posted.
Run:
python -c 'import sys; sys.stdout.write("\x55\xaa\xc8\xcb\x6e" + "\x00"*(100*1024 - 5))' > dummy.rom
and then add "-option-rom dummy.rom" to your qemu command line. (The
idea is to build a 100K dummy option rom that seabios will load and
mark as read-only memory.)
-Kevin
next prev parent reply other threads:[~2012-05-10 1:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 15:58 [Qemu-devel] : Memory problem with Qemu/SeaBIOS Alain Ribière
2012-05-08 0:55 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2012-05-08 16:47 ` [Qemu-devel] Re : " Alain Ribière
2012-05-08 22:06 ` Kevin O'Connor
2012-05-09 15:57 ` [Qemu-devel] Re : " Alain Ribière
2012-05-10 0:44 ` Kevin O'Connor
2012-05-10 1:19 ` Kevin O'Connor [this message]
2012-05-10 13:56 ` [Qemu-devel] Re : " Alain Ribière
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=20120510011945.GA24218@morn.localdomain \
--to=kevin@koconnor.net \
--cc=alain_ribiere@yahoo.com \
--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).