From: Hetz Ben Hamo <hetzbh@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] NEC PC-9821
Date: Fri, 14 Oct 2005 23:55:00 +0200 [thread overview]
Message-ID: <41e41e7a0510141455m52dd88e2xa9a4105c30917e54@mail.gmail.com> (raw)
In-Reply-To: <20051014.154505.68095539.imp@bsdimp.com>
Not really. I think you'll need a BIOS for it which is copyrighted and
not freely distributable, and I think some specs are different, but I
didn't see any patches floating around.
Hetz
On 10/14/05, M. Warner Losh <imp@bsdimp.com> wrote:
> Has anybody made qemu emulate the NEC PC-9821 family of computer
> products from NEC, also known as Japanese PC?
>
> Warner
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
next prev parent reply other threads:[~2005-10-14 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 21:45 [Qemu-devel] NEC PC-9821 M. Warner Losh
2005-10-14 21:55 ` Hetz Ben Hamo [this message]
2005-10-14 22:26 ` M. Warner Losh
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=41e41e7a0510141455m52dd88e2xa9a4105c30917e54@mail.gmail.com \
--to=hetzbh@gmail.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).