From: Ye Li <ye.li@nxp.com>
To: u-boot@lists.denx.de
Subject: [PATCH] splash: Fix build warning on 64 bits CPU
Date: Wed, 10 Jun 2020 02:52:22 -0700 [thread overview]
Message-ID: <1591782743-22846-2-git-send-email-ye.li@nxp.com> (raw)
In-Reply-To: <1591782743-22846-1-git-send-email-ye.li@nxp.com>
Get below warning on ARM64 platform, because the bmp_load_addr
is defined to u32.
common/splash.c: In function ?splash_video_logo_load?:
common/splash.c:74:9: warning: cast to pointer from integer
of different size [-Wint-to-pointer-cast]
74 | memcpy((void *)bmp_load_addr, bmp_logo_bitmap,
Signed-off-by: Ye Li <ye.li@nxp.com>
---
common/splash.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/splash.c b/common/splash.c
index e7d8477..2b9313e 100644
--- a/common/splash.c
+++ b/common/splash.c
@@ -59,7 +59,7 @@ static struct splash_location default_splash_locations[] = {
static int splash_video_logo_load(void)
{
char *splashimage;
- u32 bmp_load_addr;
+ ulong bmp_load_addr;
splashimage = env_get("splashimage");
if (!splashimage)
--
2.7.4
next prev parent reply other threads:[~2020-06-10 9:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 9:52 [PATCH] video: vidconsole: avoid multiple lines overwrite logo Ye Li
2020-06-10 9:52 ` Ye Li [this message]
2020-06-17 7:09 ` [PATCH] splash: Fix build warning on 64 bits CPU Jagan Teki
2020-06-29 7:05 ` Anatolij Gustschin
2020-06-10 9:52 ` [PATCH] video: bmp: Support 8bits BMP to 24/32 bits display Ye Li
2020-06-17 7:10 ` Jagan Teki
2020-06-18 21:04 ` Fabio Estevam
2020-06-23 11:51 ` Anatolij Gustschin
2020-06-27 22:59 ` [PATCH v2] video: bmp: support 8bits BMP drawing on 24/32 bpp framebuffer Anatolij Gustschin
2020-06-29 7:04 ` Anatolij Gustschin
2020-06-17 7:11 ` [PATCH] video: vidconsole: avoid multiple lines overwrite logo Jagan Teki
2020-06-29 7:04 ` Anatolij Gustschin
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=1591782743-22846-2-git-send-email-ye.li@nxp.com \
--to=ye.li@nxp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox