All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] Allow building without graphics support
Date: Wed, 12 Dec 2012 18:57:51 -0600	[thread overview]
Message-ID: <1355360271.28445.25@snotra> (raw)
In-Reply-To: <50C837BD.4020604@redhat.com> (from kraxel@redhat.com on Wed Dec 12 01:52:29 2012)

On 12/12/2012 01:52:29 AM, Gerd Hoffmann wrote:
> On 12/12/12 04:18, 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.
> 
> We have tons of hand-crafted pixel shuffeling code all over the place
> which I want replace with pixman library calls.  It's a long road and
> will take quite some time.
> 
> I wanna have pixman as core service in qemu for that, not some  
> optional
> add-on.

Why?  Isn't modularity a good thing?  It can still be a core service  
for any part of QEMU that deals with graphics.

> > 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),
> 
> We pass on cross-prefix to pixman's configure, so it should
> JustWork[tm].

That's actually what was breaking it (I gave more details in another  
e-mail in this thread).  cross-prefix and host tuple are not quite the  
same thing.

> > 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).
> 
> I run qemu on headless machines alot, then connect via vnc/spice ...

So then don't turn off graphics support in your build, just as you  
don't turn off vnc/spice. :-P

Another thing that is missing on the hardware I'm talking about is a  
hard drive, so overly large qemu binaries are also not fun.

-Scott

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

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=1355360271.28445.25@snotra \
    --to=scottwood@freescale.com \
    --cc=aliguori@us.ibm.com \
    --cc=kraxel@redhat.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 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.