All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
	qemu-devel@nongnu.org,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"QEMU Trivial" <qemu-trivial@nongnu.org>
Subject: Re: [PATCH v2] vnc: increase max display size
Date: Thu, 18 Jul 2024 17:12:15 +0100	[thread overview]
Message-ID: <Zpk-31nhmIAj7P5N@redhat.com> (raw)
In-Reply-To: <CAFEAcA8ShMnj43QwhKZxPvqQ9ei3s6LBGgXHQwRvpKf98dvuBA@mail.gmail.com>

On Thu, Jul 18, 2024 at 04:58:10PM +0100, Peter Maydell wrote:
> On Thu, 30 May 2024 at 12:11, Gerd Hoffmann <kraxel@redhat.com> wrote:
> >
> > It's 2024.  4k display resolutions are a thing these days.
> > Raise width and height limits of the qemu vnc server.
> >
> > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1596
> > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> > ---
> >  ui/vnc.h | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/ui/vnc.h b/ui/vnc.h
> > index 4521dc88f792..e5fa2efa3e5d 100644
> > --- a/ui/vnc.h
> > +++ b/ui/vnc.h
> > @@ -81,8 +81,8 @@ typedef void VncSendHextileTile(VncState *vs,
> >
> >  /* VNC_MAX_WIDTH must be a multiple of VNC_DIRTY_PIXELS_PER_BIT. */
> >
> > -#define VNC_MAX_WIDTH ROUND_UP(2560, VNC_DIRTY_PIXELS_PER_BIT)
> > -#define VNC_MAX_HEIGHT 2048
> > +#define VNC_MAX_WIDTH ROUND_UP(5120, VNC_DIRTY_PIXELS_PER_BIT)
> > +#define VNC_MAX_HEIGHT 2160
> >
> >  /* VNC_DIRTY_BITS is the number of bits in the dirty bitmap. */
> >  #define VNC_DIRTY_BITS (VNC_MAX_WIDTH / VNC_DIRTY_PIXELS_PER_BIT)
> 
> Hi -- somebody on IRC pointed out that this simple patch
> had been code-reviewed by Daniel but never made it into git.
> Marc-André: you're listed maintainer for ui/ -- do you have
> a pullreq planned?
> 
> Alternatively we could take it via qemu-trivial since it's
> a pretty tiny patch (cc'd).

I'm working on a misc pull request, so I'll just include this
patch

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      reply	other threads:[~2024-07-18 16:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 11:10 [PATCH v2] vnc: increase max display size Gerd Hoffmann
2024-05-31 12:35 ` Daniel P. Berrangé
2024-07-18 15:58 ` Peter Maydell
2024-07-18 16:12   ` Daniel P. Berrangé [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=Zpk-31nhmIAj7P5N@redhat.com \
    --to=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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.