qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 16-bit (and 8-bit) emulation
Date: Sun, 15 Apr 2007 14:31:52 +0100	[thread overview]
Message-ID: <200704151431.52913.paul@codesourcery.com> (raw)
In-Reply-To: <462220E9.1090904@bandsman.co.uk>

> > My point is that pretty much anything that runs on a 286 should also run
> > on any subsequent x86 processor. If you want to test 16-bit x86
> > software/systems you don't need an actual 286. A 386 is just as good for
> > almost all purposes.
>
> How does that address my issue?

You wanted a 286 so that you could test 16-bit x86 code. You can already do 
that with current qemu. How you generate that 16-bit x86 code is a completely 
unrelated (and offtopic) problem.

Paul

  reply	other threads:[~2007-04-15 13:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15 10:08 [Qemu-devel] Report Nigel Horne
2007-04-15 11:33 ` [Qemu-devel] 16-bit (and 8-bit) emulation Stuart Brady
2007-04-15 11:42   ` Paul Brook
2007-04-15 12:08   ` Nigel Horne
2007-04-15 12:35     ` Paul Brook
2007-04-15 12:43       ` Nigel Horne
2007-04-15 12:54         ` Paul Brook
2007-04-15 12:56           ` Nigel Horne
2007-04-15 13:31             ` Paul Brook [this message]
2007-04-15 13:46               ` Nigel Horne
2007-04-15 13:51                 ` Paul Brook
2007-04-15 13:54                   ` Nigel Horne
2007-04-15 19:55                 ` Natalia Portillo
2007-04-16 23:35                   ` Derek Fawcus
2007-04-16 23:57                     ` Natalia Portillo
2007-04-15 12:40     ` Andreas Schwab
2007-04-15 12:46       ` Nigel Horne
2007-04-15 13:30         ` Andreas Schwab
2007-04-17 13:55     ` Todd T. Fries
2007-04-15 12:46 ` [Qemu-devel] Report Thiemo Seufer
2007-04-15 14:08   ` Nigel Horne
2007-04-15 16:37     ` Thiemo Seufer

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=200704151431.52913.paul@codesourcery.com \
    --to=paul@codesourcery.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).