From: Hannes Schmelzer <hannes@schmelzer.or.at>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/5] arm: Show cache warnings in U-Boot proper only
Date: Tue, 2 Aug 2016 08:42:35 +0200 [thread overview]
Message-ID: <57A040DB.1020203@schmelzer.or.at> (raw)
In-Reply-To: <1466386991-10469-6-git-send-email-sjg@chromium.org>
On 20.06.2016 03:43, Simon Glass wrote:
> Avoid bloating the SPL image size.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> arch/arm/lib/cache.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/lib/cache.c b/arch/arm/lib/cache.c
> index 642a952..d330b09 100644
> --- a/arch/arm/lib/cache.c
> +++ b/arch/arm/lib/cache.c
> @@ -61,8 +61,8 @@ int check_cache_range(unsigned long start, unsigned long stop)
> ok = 0;
>
> if (!ok) {
> - debug("CACHE: Misaligned operation at range [%08lx, %08lx]\n",
> - start, stop);
> + warn_non_spl("CACHE: Misaligned operation at range [%08lx, %08lx]\n",
> + start, stop);
> }
>
> return ok;
Since this i've, and probably many others, have a bunch of warnings on
doing something in u-boot.
Just compiled and installed today new u-boot on my zynq-board.
"
U-Boot 2016.09-rc1-00353-g2ac625b-dirty (Aug 02 2016 - 08:06:57 +0200)
I2C: ready
DRAM: ECC disabled 256 MiB
MMC: sdhci at e0100000: 0
SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB,
total 16 MiB
FPGA: id 0x2 (7z010)
Net: ZYNQ GEM: e000b000, phyaddr 0, interface rgmii-id
*CACHE: Misaligned operation at range [0fff03b0, 0fff03b4]*
Warning: ethernet at e000b000 (eth0) using random MAC address -
aa:99:75:dd:1d:71
eth0: ethernet at e000b000
SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB,
total 16 MiB
device 0 offset 0xc0000, size 0x10000
SF: 65536 bytes @ 0xc0000 Read: OK
## Executing script at 000c0000
=> dhcp
*CACHE: Misaligned operation at range [0eb583b0, 0eb583b4]**
**CACHE: Misaligned operation at range [0eb583b4, 0eb583b8]*
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
DHCP client bound to address 192.168.21.193 (1008 ms)
=>
"
Do we have real trouble inside or can we quiet this warning?
cheers,
Hannes
next prev parent reply other threads:[~2016-08-02 6:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 1:43 [U-Boot] [PATCH 0/5] arm: Tidy up the cache aligning warning code Simon Glass
2016-06-20 1:43 ` [U-Boot] [PATCH 1/5] arm: Move check_cache_range() into a common place Simon Glass
2016-06-20 2:58 ` Marek Vasut
2016-07-16 13:46 ` [U-Boot] [U-Boot, " Tom Rini
2016-06-20 1:43 ` [U-Boot] [PATCH 2/5] arm: Don't invalidate unaligned cache regions Simon Glass
2016-06-20 3:00 ` Marek Vasut
2016-07-16 13:46 ` [U-Boot] [U-Boot, " Tom Rini
2016-06-20 1:43 ` [U-Boot] [PATCH 3/5] Add comments for debug() and pr_fmt Simon Glass
2016-07-16 13:47 ` [U-Boot] [U-Boot,3/5] " Tom Rini
2016-06-20 1:43 ` [U-Boot] [PATCH 4/5] Add warn_non_spl() to show a message in U-Boot proper Simon Glass
2016-07-16 13:47 ` [U-Boot] [U-Boot, " Tom Rini
2016-06-20 1:43 ` [U-Boot] [PATCH 5/5] arm: Show cache warnings in U-Boot proper only Simon Glass
2016-07-16 13:47 ` [U-Boot] [U-Boot, " Tom Rini
2016-08-02 6:42 ` Hannes Schmelzer [this message]
2016-08-02 6:49 ` [U-Boot] [PATCH " Michal Simek
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=57A040DB.1020203@schmelzer.or.at \
--to=hannes@schmelzer.or.at \
--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