All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Pooja Dhannawat <dhannawatpooja1@gmail.com>
Subject: Re: [Qemu-devel] [Patch v2 1/1] blizzard: Remove support for DEPTH != 32
Date: Fri, 18 Mar 2016 09:30:41 +0100	[thread overview]
Message-ID: <1458289841.6882.16.camel@redhat.com> (raw)
In-Reply-To: <CAFEAcA_LtboweFSe2WSQPk5g+ur_EvsarLp76hYzPrcfoDsZqQ@mail.gmail.com>

On Mo, 2016-03-14 at 15:22 +0000, Peter Maydell wrote:
> On 14 March 2016 at 15:04, Pooja Dhannawat <dhannawatpooja1@gmail.com> wrote:
> > Removing support for DEPTH != 32 from blizzard template header
> > and file that includes it, as macro DEPTH == 32 only used.
> >
> > Signed-off-by: Pooja Dhannawat <dhannawatpooja1@gmail.com>
> > ---
> >  hw/display/blizzard.c          | 24 ------------------------
> >  hw/display/blizzard_template.h | 30 +-----------------------------
> >  2 files changed, 1 insertion(+), 53 deletions(-)

> So are there any cases now when
> surface_bits_per_pixel(qemu_console_surface(c)) can return
> zero? (I don't understand the 'case 0' code in this switch
> at all...)

Looks like a somewhat strange way to zero-fill the function pointer
array.  Looks like a historical leftover.

As blizzard uses qemu_console_resize() you will always get a surface
with the default depth (32bpp).  So dropping the whole "switch { ... }"
block (except for the "case 32:" lines) and adding an
"assert(surface_bits_per_pixel(surface)==32)" should work just fine.

cheers,
  Gerd

  reply	other threads:[~2016-03-18  8:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 15:04 [Qemu-devel] [Patch v2 1/1] blizzard: Remove support for DEPTH != 32 Pooja Dhannawat
2016-03-14 15:22 ` Peter Maydell
2016-03-18  8:30   ` Gerd Hoffmann [this message]
2016-03-18 15:46     ` Pooja Dhannawat
2016-03-14 17:56 ` [Qemu-devel] [PATCH v3] " Pooja Dhannawat

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=1458289841.6882.16.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=dhannawatpooja1@gmail.com \
    --cc=peter.maydell@linaro.org \
    --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.