All of
 help / color / mirror / Atom feed
From: Peter Maydell <>
To: Mark Cave-Ayland <>
Cc: QEMU Developers <>,
	Gerd Hoffmann <>
Subject: Re: [PATCH] hw/display/tcx: Drop unnecessary code for handling BGR format outputs
Date: Tue, 16 Feb 2021 10:11:31 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, 15 Feb 2021 at 22:41, Mark Cave-Ayland
<> wrote:
> On 15/02/2021 10:21, Peter Maydell wrote:
> > For a long time now the UI layer has guaranteed that the console
> > surface is always 32 bits per pixel, RGB. The TCX code already
> > assumes 32bpp, but it still has some checks of is_surface_bgr()
> > in an attempt to support 32bpp BGR. is_surface_bgr() will always
> > return false for the qemu_console_surface(), unless the display
> > device itself has deliberately created an alternate-format
> > surface via a function like qemu_create_displaysurface_from().
> >
> > Drop the never-used BGR-handling code, and assert that we have
> > a 32-bit surface rather than just doing nothing if it isn't.
> >
> > Signed-off-by: Peter Maydell <>

> Thanks Peter - looks good to me.
> Reviewed-by: Mark Cave-Ayland <>
> Would you like this to go via a qemu-sparc PR or is it easier to go as part of a
> group alongside your other display surface patches via

I'm happy either way -- if you don't happen to have anything else
queued up for sparc I can just put it in with the arm queue.

-- PMM

  reply	other threads:[~2021-02-16 10:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 10:21 [PATCH] hw/display/tcx: Drop unnecessary code for handling BGR format outputs Peter Maydell
2021-02-15 22:40 ` Mark Cave-Ayland
2021-02-16 10:11   ` Peter Maydell [this message]
2021-02-16 21:57     ` Mark Cave-Ayland
2021-02-16  0:46 ` Richard Henderson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \

* 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.