From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/3] EXYNOS: display 32bpp bitmap TIZEN logo
Date: Mon, 30 Apr 2012 12:14:03 +0200 [thread overview]
Message-ID: <20120430121403.1d7b4ab8@wker> (raw)
In-Reply-To: <4F990583.6090905@samsung.com>
Hi,
On Thu, 26 Apr 2012 17:21:23 +0900
Donghwa Lee <dh09.lee@samsung.com> wrote:
...
> diff --git a/drivers/video/exynos_fb.c b/drivers/video/exynos_fb.c
> index 96a8ec1..f669b65 100644
> --- a/drivers/video/exynos_fb.c
> +++ b/drivers/video/exynos_fb.c
...
> @@ -64,6 +68,29 @@ static void exynos_lcd_init(vidinfo_t *vid)
> exynos_fimd_lcd_init(vid);
> }
>
> +static void draw_logo(void)
> +{
> + int x, y;
> + bmp_image_t *bmp;
> + ulong addr, len;
> + unsigned int logo_width, logo_height;
> +
> + logo_width = panel_info.logo_width;
> + logo_height = panel_info.logo_height;
> + x = ((panel_width - logo_width) >> 1);
> + y = ((panel_height - logo_height) >> 1) - 4;
> +
> + addr = (ulong)logo;
> + bmp = (bmp_image_t *)addr;
> +
> + if (!((bmp->header.signature[0] =='B') &&
> + (bmp->header.signature[1] =='M'))) {
> + addr = (ulong)gunzip_bmp(addr, &len);
> + }
> +
> + lcd_display_bitmap((ulong)addr, x, y);
Here freeing the buffer allocated by gunzip_bmp() is needed. But I think
that we should better use bmp_display((ulong)addr, x, y) here to reuse
the existing code. I've sent a patch [1] making bmp_display() non static,
so please use bmp_display() here.
Thanks,
Anatolij
[1] http://patchwork.ozlabs.org/patch/155490/
prev parent reply other threads:[~2012-04-30 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 8:21 [U-Boot] [PATCH v2 3/3] EXYNOS: display 32bpp bitmap TIZEN logo Donghwa Lee
2012-04-27 0:46 ` Minkyu Kang
2012-04-30 10:14 ` Anatolij Gustschin [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=20120430121403.1d7b4ab8@wker \
--to=agust@denx.de \
--cc=u-boot@lists.denx.de \
/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.