From: Scott Wood <scottwood@freescale.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] Allow building without graphics support
Date: Wed, 12 Dec 2012 18:51:38 -0600 [thread overview]
Message-ID: <1355359898.28445.23@snotra> (raw)
In-Reply-To: <CAFEAcA8RKMinAQZvBGACjaNoTY5Rt8xDW4DX3myAQtX6R1bwiQ@mail.gmail.com> (from peter.maydell@linaro.org on Wed Dec 12 10:47:04 2012)
On 12/12/2012 10:47:04 AM, Peter Maydell wrote:
> On 12 December 2012 03:18, Scott Wood <scottwood@freescale.com> wrote:
> > QEMU is sometimes used in embedded contexts, where graphical support
> > is unnecessary. The ability to turn off graphics support not only
> > saves some space, but it eliminates the dependency on pixman.
>
> I would expect that we'd want to use pixman in the emulation
> of graphics devices (which should be visible to the guest even
> if the host doesn't have display support).
And those devices would have a dependency on the QEMU graphics
subsystem. Not all targets have graphics devices to be emulated.
> > My immediate motivation was that the QEMU-supplied pixman was being
> a
> > pain to cross compile
>
> Problems with cross compilation should be reported as bugs
> so we can fix them -- we need to fix them anyway for the more
> common case where there is host graphics support.
Sure. It wasn't meant as a long-term alternative to fixing pixman
issues, so much as as a final nudge to do something I'd wanted to do
before.
-Scott
prev parent reply other threads:[~2012-12-13 0:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 3:18 [Qemu-devel] [RFC PATCH] Allow building without graphics support Scott Wood
2012-12-12 6:46 ` Stefan Weil
2012-12-13 0:48 ` Scott Wood
2012-12-13 6:31 ` Stefan Weil
2012-12-13 15:53 ` Scott Wood
2012-12-13 18:58 ` Stefan Weil
2012-12-13 19:16 ` Scott Wood
2012-12-13 19:32 ` Scott Wood
2012-12-14 8:13 ` Gerd Hoffmann
2012-12-14 18:51 ` Scott Wood
2012-12-19 9:02 ` Gerd Hoffmann
2012-12-19 18:47 ` Scott Wood
2012-12-14 8:07 ` Gerd Hoffmann
2012-12-14 18:48 ` Scott Wood
2012-12-19 9:13 ` Gerd Hoffmann
2012-12-19 18:57 ` Scott Wood
2012-12-20 6:59 ` Gerd Hoffmann
2012-12-20 16:19 ` Scott Wood
2012-12-21 8:56 ` Gerd Hoffmann
2012-12-21 10:56 ` Robert Schiele
2012-12-21 19:01 ` Scott Wood
2012-12-12 7:52 ` Gerd Hoffmann
2012-12-13 0:57 ` Scott Wood
2012-12-13 7:16 ` Gerd Hoffmann
2012-12-13 14:44 ` Alexander Graf
2012-12-13 15:10 ` Peter Maydell
2012-12-13 15:16 ` Gerd Hoffmann
2012-12-13 15:30 ` Alexander Graf
2012-12-13 15:57 ` Scott Wood
2012-12-12 16:28 ` John Spencer
2012-12-12 16:54 ` Andreas Färber
2012-12-13 0:53 ` Scott Wood
2012-12-12 16:47 ` Peter Maydell
2012-12-12 17:09 ` Andreas Färber
2012-12-12 17:37 ` Peter Maydell
2012-12-12 17:42 ` Paolo Bonzini
2012-12-13 0:51 ` Scott Wood [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=1355359898.28445.23@snotra \
--to=scottwood@freescale.com \
--cc=aliguori@us.ibm.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.