From: Anthony Liguori <anthony@codemonkey.ws>
To: Natalia Portillo <claunia@claunia.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Seabios dislikes -M isapc
Date: Tue, 09 Feb 2010 15:41:55 -0600 [thread overview]
Message-ID: <4B71D6A3.6000902@codemonkey.ws> (raw)
In-Reply-To: <7DDDDCA5-2F86-4644-B7B3-A714AEDA56CA@claunia.com>
On 02/09/2010 03:36 PM, Natalia Portillo wrote:
> Xenix is currently working (when copied from real hardware).
> As well Interactive UNIX and some other non-DOS from 8086 and 286 era.
>
> I'm not really sure that operating systems (specially the 8086 ones
> that do mmu functions in software) will be happy with the PCI bus
> present.
>
> Same for first 386 operating systems (OS/2 2, UNIX, Xenix, so on).
>
> I don't think it is so bad forking the BIOS, letting the ISA one only
> for bug fixes, and the PCI one for new features.
> Even the ISA BIOS can be code cleaned, there is no SMBIOS or ACPI in
> ISA hardware.
I doubt anyone is going to want to actually maintain an ISA BIOS solely
to support these OSes.
But at any rate, I'd like to see someone actually confirm that something
works with isapc and not with pc.
>
> Or, use bochs bios, that we know is working (at least for now) for
> isapc, and seabios for pcipc.
>
> There are a lot of ways to do that, but I think that simply forgetting
> about isapc and deleting it is not a bugfix, but a big big bug.
If nothing actually requires isapc, then I don't see how removing it is
a bug. Heck, if we just alias isapc to pc, then I doubt anyone would
actually notice :-)
Regards,
ANthony Liguori
next prev parent reply other threads:[~2010-02-09 21:42 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
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 [this message]
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=4B71D6A3.6000902@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=claunia@claunia.com \
--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).