From: malc <av1474@comtv.ru>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] Seabios dislikes -M isapc
Date: Wed, 10 Feb 2010 03:27:43 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.00.1002100325070.18215@linmac> (raw)
In-Reply-To: <4B71F72D.8090703@codemonkey.ws>
On Tue, 9 Feb 2010, Anthony Liguori wrote:
> On 02/09/2010 05:25 PM, Aurelien Jarno wrote:
> > On Wed, Feb 10, 2010 at 01:41:01AM +0300, malc wrote:
> >
> > > On Tue, 9 Feb 2010, 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).
> > > >
> > > News to me that OS/2 worked.. I don't quite remember which version
> > > someone (you?) asked me to try on IRC a few years back, but it definitely
> > > didn't work.
> > >
> > >
> > I have got OS/2 warp working under QEMU a few years ago. I couldn't give
> > more details though, I just remember it was working nicely.
> >
>
> The problem with isapc is that it uses a different chipset (or rather, doesn't
> use a PCI chipset). I think the current thinking with target-i386 config
> files is that while you should be able to customize the system, some of the
> core bits would always be there. For instance, the PCI chipset, the APIC,
> etc. These things are very tied to a platform.
APIC is almost as good as useless without ACPI and we have a switch to
disable that.
>
> Firmware is really hard to implement if you have to deal with supporting
> multiple chipsets.
>
> Also, if we don't have a workload that actually needs isapc, that suggests
> that there's no real way to test that isapc doesn't have non-ISA things creep
> into it.
>
> Given that, I'm inclined to suggest that we mark isapc as deprecated, give
> people some time to comment on it, and then provided that we still don't think
> it's necessary, change isapc to simply use isa devices while still using a PCI
> chipset.
Not to comment, to give hard evidence that something is working with isapc
and doesn't otherwise, in which case it must stay.
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2010-02-10 0:27 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
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 [this message]
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=alpine.LNX.2.00.1002100325070.18215@linmac \
--to=av1474@comtv.ru \
--cc=anthony@codemonkey.ws \
--cc=aurelien@aurel32.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).