From: Jan Kiszka <jan.kiszka@siemens.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: Kevin O'Connor <kevin@koconnor.net>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Seabios dislikes -M isapc
Date: Mon, 08 Feb 2010 20:09:17 +0100 [thread overview]
Message-ID: <4B70615D.2080406@siemens.com> (raw)
In-Reply-To: <8D0A564F20EB4421B2CC199C47C63EA6@FSCPC>
Sebastian Herbszt wrote:
> Jan Kiszka wrote:
>> Hi,
>>
>> Seabios seems to have some assumptions built in that break when -M isapc
>> is selected. Is this supposed to work or is isapc about to die?
>
> SeaBIOS doesn't POST if the F-segment is not writeable [1]. A possible, but IMO
> wrong fix was posted on the list [2].
>
> [1] http://lists.gnu.org/archive/html/qemu-devel/2009-11/msg01188.html
> [2] http://lists.gnu.org/archive/html/qemu-devel/2009-12/msg00445.html
>
Indeed, [2] makes it work again.
But taking away IO_MEM_ROM really looks like a lazy workaround. I don't
know how much Seabios needs to write - can't it use normal RAM for this?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-02-08 19:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 10:17 [Qemu-devel] Seabios dislikes -M isapc Jan Kiszka
2010-02-08 18:38 ` [Qemu-devel] " Sebastian Herbszt
2010-02-08 19:09 ` Jan Kiszka [this message]
2010-02-09 0:51 ` Kevin O'Connor
2010-02-09 20:47 ` Sebastian Herbszt
2010-02-09 19:45 ` [Qemu-devel] " Andreas Färber
2010-02-09 19:50 ` Anthony Liguori
2010-02-09 20:36 ` Natalia Portillo
2010-02-09 21:05 ` Anthony Liguori
2010-02-09 21:36 ` Natalia Portillo
2010-02-09 21:41 ` Anthony Liguori
2010-02-09 22:41 ` malc
2010-02-09 23:25 ` Aurelien Jarno
2010-02-09 23:28 ` malc
2010-02-10 0:00 ` Anthony Liguori
2010-02-10 0:27 ` malc
2010-02-10 0:31 ` Anthony Liguori
2010-02-11 23:51 ` Jamie Lokier
2010-02-12 2:44 ` Anthony Liguori
2010-02-09 23:27 ` Natalia Portillo
2010-02-09 23:30 ` malc
2010-02-09 22:37 ` malc
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=4B70615D.2080406@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=herbszt@gmx.de \
--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 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.