qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Stefan Weil <sw@weilnetz.de>, Robert Schiele <rschiele@gmail.com>,
	qemu-devel@nongnu.org, John Spencer <maillist-qemu@barfooze.de>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] Allow building without graphics support
Date: Wed, 12 Dec 2012 18:53:46 -0600	[thread overview]
Message-ID: <1355360026.28445.24@snotra> (raw)
In-Reply-To: <50C8B6AC.10703@suse.de> (from afaerber@suse.de on Wed Dec 12 10:54:04 2012)

On 12/12/2012 10:54:04 AM, Andreas Färber wrote:
> Am 12.12.2012 17:28, schrieb John Spencer:
> > On 12/12/2012 04:18 AM, Scott Wood 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.
> >>
> >> Signed-off-by: Scott Wood<scottwood@freescale.com>
> >> ---
> >> There are undoubtedly some rough edges that need to be cleaned up  
> and
> >> other parts of graphics code that could be compiled out -- this is  
> mainly
> >> meant to see what people think of the concept.
> >>
> >> My immediate motivation was that the QEMU-supplied pixman was  
> being a
> >> pain to cross compile (especially without hacking up the generated  
> QEMU
> >> makefiles to pass additional things to pixman's configure), and in
> >> general it would be nice to not have to carry around graphical  
> baggage
> >> when running on hardware that doesn't even have a display (so I  
> was more
> >> inclined to do this than to spend effort fixing the pixman build).
> >> ---
> >
> > very nice, i hope this one makes it upstream.
> > it's always good to minimize external dependencies, or make them
> > optional when they're unneeded in some cases.
> 
> There is already a patch by Robert Schiele on the list, let's not
> reinvent the wheel here. That part should be pretty uncontroversial.
> What this patch does on top is prone to clash with a number of ongoing
> refactorings so I'd rather hold that off a bit.

Ah, didn't notice that -- though tying it to CONFIG_USER_ONLY doesn't  
help my use case.

-Scott

  reply	other threads:[~2012-12-13  0:53 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 [this message]
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

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=1355360026.28445.24@snotra \
    --to=scottwood@freescale.com \
    --cc=afaerber@suse.de \
    --cc=kraxel@redhat.com \
    --cc=maillist-qemu@barfooze.de \
    --cc=qemu-devel@nongnu.org \
    --cc=rschiele@gmail.com \
    --cc=sw@weilnetz.de \
    /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).