qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Just a thought (high level API)
Date: Thu, 10 Feb 2005 23:16:58 +0100	[thread overview]
Message-ID: <aec7e5c3050210141635b0024f@mail.gmail.com> (raw)
In-Reply-To: <1108067564.8083.7.camel@localhost.localdomain>

On Thu, 10 Feb 2005 15:32:44 -0500, Nathaniel McCallum
<npmccallum@gentoo.org> wrote:

[snip]

> Thanks for your input!  I was hoping you'd come out and play ;).  I'll
> gladly do a gtk frontend (I was planning on it).  However, one of the
> first things I would need to do would be to create some kind of config
> file to store the settings in.  I'd rather do this upstream and let
> other front ends benefit from this as well.

Please implement a gtk frontend, that would be really cool and useful!
And speaking about config files, I think extending the current way of
passing options to the system emulator further leads to is a dead end:

http://lists.gnu.org/archive/html/qemu-devel/2005-01/msg00175.html

I would like to see more reentrant code that makes it possible to have
several instances of the same code hooked up at different places in
the emulator. Code that emulates hardware is of course a candidate,
but I also think displaying and muxing graphics is a typical thing
that a user wants to control from somewhere. Say that I would like to
emulate a system with two vga cards - where should the output go? To
one window and to /dev/null? Or two windows? Or muxed together like
the vga output and the monitor in one window? I think the best is to
let the user decide.

/ magnus

  parent reply	other threads:[~2005-02-10 22:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 15:09 [Qemu-devel] Just a thought (high level API) Nathaniel McCallum
2005-02-09 15:52 ` McMullan, Jason
2005-02-10  0:02 ` Jim C. Brown
2005-02-10  1:28   ` Nathaniel McCallum
2005-02-10  2:34     ` Jim C. Brown
2005-02-10  3:47       ` Nathaniel McCallum
2005-02-10 19:59 ` Fabrice Bellard
2005-02-10 20:32   ` Nathaniel McCallum
2005-02-10 21:21     ` Fabrice Bellard
2005-02-10 22:16     ` Magnus Damm [this message]
2005-02-11 11:07     ` Jan Marten Simons
2005-02-11 12:20       ` Johannes Schindelin
2005-02-11 15:07         ` Jim C. Brown
2005-02-11 15:35           ` Nathaniel McCallum
2005-02-11 16:14             ` [Qemu-devel] " Ronald
2005-02-11 23:02               ` Nathaniel McCallum
2005-02-11 23:39                 ` [Qemu-devel] " Ronald
2005-02-11 18:27         ` [Qemu-devel] " Jan Marten Simons
2005-02-11 18:30           ` Paul Brook
2005-02-11 20:03             ` Nathaniel McCallum
2005-02-11 22:55               ` art yerkes
2005-02-11 23:04                 ` Nathaniel McCallum

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=aec7e5c3050210141635b0024f@mail.gmail.com \
    --to=magnus.damm@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).