All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH v2] console: Correct computation of bytes per pixel from bits per pixel
Date: Wed, 22 Aug 2012 17:32:13 +0200	[thread overview]
Message-ID: <5034FB7D.5050009@siemens.com> (raw)
In-Reply-To: <Pine.GSO.4.64.1208221718470.28960@mono>

On 2012-08-22 17:19, BALATON Zoltan wrote:
> Division with round up is the correct way to compute this even if the
> only case where division with round down gives incorrect result is
> probably 15 bpp. This case was explicitely patched up in one of these
> functions but was unhandled in the other. (I'm not sure about setting
> 16 bpp for the 15bpp case either but I left that there for now.)
> 
> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
> ---
>  console.c |    5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
>  v2: Use DIV_ROUND_UP and extended commit message
> 
> diff --git a/console.c b/console.c
> index 4525cc7..9df1701 100644
> --- a/console.c
> +++ b/console.c
> @@ -1612,7 +1612,7 @@ PixelFormat
> qemu_different_endianness_pixelformat(int bpp)
>      memset(&pf, 0x00, sizeof(PixelFormat));
> 
>      pf.bits_per_pixel = bpp;
> -    pf.bytes_per_pixel = bpp / 8;
> +    pf.bytes_per_pixel = DIV_ROUND_UP(bpp, 8);
>      pf.depth = bpp == 32 ? 24 : bpp;
> 
>      switch (bpp) {
> @@ -1661,13 +1661,12 @@ PixelFormat qemu_default_pixelformat(int bpp)
>      memset(&pf, 0x00, sizeof(PixelFormat));
> 
>      pf.bits_per_pixel = bpp;
> -    pf.bytes_per_pixel = bpp / 8;
> +    pf.bytes_per_pixel = DIV_ROUND_UP(bpp, 8);
>      pf.depth = bpp == 32 ? 24 : bpp;
> 
>      switch (bpp) {
>          case 15:
>              pf.bits_per_pixel = 16;
> -            pf.bytes_per_pixel = 2;

Removed unintentionally?

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux


WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] console: Correct computation of bytes per pixel from bits per pixel
Date: Wed, 22 Aug 2012 17:32:13 +0200	[thread overview]
Message-ID: <5034FB7D.5050009@siemens.com> (raw)
In-Reply-To: <Pine.GSO.4.64.1208221718470.28960@mono>

On 2012-08-22 17:19, BALATON Zoltan wrote:
> Division with round up is the correct way to compute this even if the
> only case where division with round down gives incorrect result is
> probably 15 bpp. This case was explicitely patched up in one of these
> functions but was unhandled in the other. (I'm not sure about setting
> 16 bpp for the 15bpp case either but I left that there for now.)
> 
> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
> ---
>  console.c |    5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
>  v2: Use DIV_ROUND_UP and extended commit message
> 
> diff --git a/console.c b/console.c
> index 4525cc7..9df1701 100644
> --- a/console.c
> +++ b/console.c
> @@ -1612,7 +1612,7 @@ PixelFormat
> qemu_different_endianness_pixelformat(int bpp)
>      memset(&pf, 0x00, sizeof(PixelFormat));
> 
>      pf.bits_per_pixel = bpp;
> -    pf.bytes_per_pixel = bpp / 8;
> +    pf.bytes_per_pixel = DIV_ROUND_UP(bpp, 8);
>      pf.depth = bpp == 32 ? 24 : bpp;
> 
>      switch (bpp) {
> @@ -1661,13 +1661,12 @@ PixelFormat qemu_default_pixelformat(int bpp)
>      memset(&pf, 0x00, sizeof(PixelFormat));
> 
>      pf.bits_per_pixel = bpp;
> -    pf.bytes_per_pixel = bpp / 8;
> +    pf.bytes_per_pixel = DIV_ROUND_UP(bpp, 8);
>      pf.depth = bpp == 32 ? 24 : bpp;
> 
>      switch (bpp) {
>          case 15:
>              pf.bits_per_pixel = 16;
> -            pf.bytes_per_pixel = 2;

Removed unintentionally?

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-08-22 15:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 15:19 [Qemu-trivial] [PATCH v2] console: Correct computation of bytes per pixel from bits per pixel BALATON Zoltan
2012-08-22 15:19 ` [Qemu-devel] " BALATON Zoltan
2012-08-22 15:32 ` Jan Kiszka [this message]
2012-08-22 15:32   ` Jan Kiszka
2012-08-22 16:29   ` [Qemu-trivial] " Stefan Weil
2012-08-22 16:29     ` Stefan Weil
2012-08-22 16:44     ` [Qemu-trivial] " Jan Kiszka
2012-08-22 16:44       ` Jan Kiszka
2012-08-22 16:56       ` [Qemu-trivial] " Jan Kiszka
2012-08-22 16:56         ` Jan Kiszka
2012-08-24 11:20       ` [Qemu-trivial] " Stefan Hajnoczi
2012-08-24 11:20         ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2012-08-24 11:21         ` [Qemu-trivial] [Qemu-devel] " Jan Kiszka
2012-08-24 11:21           ` [Qemu-devel] [Qemu-trivial] " Jan Kiszka
2012-08-24 11:53           ` [Qemu-trivial] [Qemu-devel] " Stefan Hajnoczi
2012-08-24 11:53             ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2012-08-24 11:16 ` [Qemu-trivial] [Qemu-devel] " Stefan Hajnoczi
2012-08-24 11:16   ` Stefan Hajnoczi

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=5034FB7D.5050009@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=balaton@eik.bme.hu \
    --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.