All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Rafael <verganic@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] PNG screendump alternative
Date: Mon, 19 Mar 2012 16:10:36 -0500	[thread overview]
Message-ID: <4F67A0CC.1030009@codemonkey.ws> (raw)
In-Reply-To: <CAB45g3Py9sHqNhZRs1jzT7DJjUgNa7AeWKYjbbsbOJaYuPRjZg@mail.gmail.com>

On 03/17/2012 05:45 PM, Rafael wrote:
> Hi,
>
> I  had already started to work on supporting PNG dump output on
> screendump when got to know there was another effort to do the same
> (see Add PNG screendump thread from Daniel P. Berrange). Anyway, I'd
> like to share my implementation which is a little bit different. It
> does not use any resource/lib besides libpng and qemu itself and is
> based on qemu-kvm 0.15.1 ppm_save code.
>
> I'm using that for a personal project developed at Mandriva which uses
> QMP directly to communicate with qemu VMs rather than using the
> libvirt although its usage is considered for the future. There is
> something more to show but it is just QMP related and soon I'll have
> it done to share.
>
> Comments and suggestions are appreciated.

I think the added value of this is minimal compared to the alternative 
implementation (just run convert on the PPM).

Can you talk a bit more about your use-case any why post-processing the PPM 
isn't a reasonable alternative?

Regards,

Anthony Liguori

>
> Cheers
> Rafael Cabral

  parent reply	other threads:[~2012-03-19 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-17 22:45 [Qemu-devel] [PATCH] PNG screendump alternative Rafael
2012-03-19 20:50 ` Luiz Capitulino
2012-03-20  0:57   ` Rafael da Veiga Cabral
2012-03-19 21:10 ` Anthony Liguori [this message]
2012-03-20  1:11   ` Rafael da Veiga Cabral

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=4F67A0CC.1030009@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=verganic@gmail.com \
    /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.