From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] qemu/hw pixel_ops.h
Date: Sun, 10 Jun 2007 20:31:29 +0100 [thread overview]
Message-ID: <200706102031.30269.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580706101212o6b54bc2ckb481780549fa554e@mail.gmail.com>
> How about moving these and pixel_ops to sdl.c and other output
> drivers? Then the emulated devices didn't have to know about output
> device.
They should also be independent of the output device (as they are now).
Paul
prev parent reply other threads:[~2007-06-10 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 16:35 [Qemu-devel] qemu/hw pixel_ops.h Blue Swirl
2007-06-10 16:47 ` Andreas Färber
2007-06-10 17:02 ` Blue Swirl
2007-06-10 17:41 ` Andreas Färber
2007-06-10 17:28 ` Stuart Brady
2007-06-10 17:58 ` Paul Brook
2007-06-10 19:12 ` Blue Swirl
2007-06-10 19:31 ` Paul Brook [this message]
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=200706102031.30269.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=blauwirbel@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).