openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Fertser <fercerpav@gmail.com>
To: Lei Yu <yulei.sh@bytedance.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: Re: About KVM screenshot
Date: Mon, 13 Sep 2021 16:57:12 +0300	[thread overview]
Message-ID: <20210913135712.GW23326@home.paul.comp> (raw)
In-Reply-To: <CAGm54UG1guTohXRB5CPYJR=4PQmdXaqZ0Tgq5Z0WXPS7QBxg5Q@mail.gmail.com>

Hello,

On Mon, Sep 13, 2021 at 09:47:03PM +0800, Lei Yu wrote:
> The whole KVM screenshot is implemented by the below pieces:
> 1. The vncsnapshot[1] is slightly modified for cross-compile, and a
> bitbake recipe is created for it;
> 2. A service is created to host the DBus interface to provide the
> "Trigger" and "Clear" methods for KVM screenshot;
> 3. OEM redfish actions are implemented to trigger and clear the KVM
> screenshot, including the download of the picture;

Currently obmc-ikvm gets a steady stream of JPG images, frame by
frame, from V4L2. Have you considered extending it a bit so that it
would be capable of simply saving the current frame to disk, without
any conversion/transformation, just dump an array of bytes to a file?

What would be the advantage of establishing a local VNC session with
this additional software compared to the straightforward JPG to file
writing?

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com

  reply	other threads:[~2021-09-13 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 13:47 About KVM screenshot Lei Yu
2021-09-13 13:57 ` Paul Fertser [this message]
2021-09-14  1:38   ` [External] " Lei Yu

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=20210913135712.GW23326@home.paul.comp \
    --to=fercerpav@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=yulei.sh@bytedance.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 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).