qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: LWATCDR <lwatcdr@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Porting Qemu to Plan 9
Date: Mon, 18 Sep 2006 12:15:17 -0400	[thread overview]
Message-ID: <8c38cea40609180915y709c567fy3ab7590b5622d0a3@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 514 bytes --]

I am just talking off the top of my head but doesn't Plan9 Support Posix?
If it does then I would think the next step would be to port SDL to Plan9
since I know that Qemu for Linux uses SDL for audio and video support.
You other option would be to rewrite QEMU to use the native graphics and
audio system of Plan9.
I have been temped to port QEMU to GTK so that works better with XGL. I am
afraid that life has not given me the free time to even start on that yet.
You know things like a job, exercising, a wife..

[-- Attachment #2: Type: text/html, Size: 529 bytes --]

                 reply	other threads:[~2006-09-18 16:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8c38cea40609180915y709c567fy3ab7590b5622d0a3@mail.gmail.com \
    --to=lwatcdr@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).