From: Ziyuan Xu <xzy.xu@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: re-implement proper ISB instruction for ARMv7-A
Date: Thu, 28 Jul 2016 20:03:43 +0800 [thread overview]
Message-ID: <5799F49F.5080801@rock-chips.com> (raw)
In-Reply-To: <5799E0F0.9030608@suse.de>
Hi Alexander,
On 2016?07?28? 18:39, Alexander Graf wrote:
> On 07/28/2016 12:13 PM, Ziyuan Xu wrote:
>> For ARMv7-A architecture, the valid ISB instruction is asm
>> volatile("isb").
>>
>> This patch fixes the U-Boot was stuck in invalidate_dcache_all() before
>> booting linux kernel, which occurred on rk3288-base development board
>> such as evb-rk3288, rock2-rk3288. And something output via console like:
>>
>> => bootz 0x2000000
>> 0x02000000
>> ramdisk start = 0x00000000, ramdisk end = 0x00000000
>> Continuing to boot without FDT
>> Initial value for argc=3
>> Final value for argc=3
>> using: ATAGS
>>
>> Starting kernel ...
>>
>> Linux kernel exactly the same way(see arch/arm/include/asm/barrier.h).
>>
>> Signed-off-by: Ziyuan Xu <xzy.xu@rock-chips.com>
>
> Perfect! So with this, EFI support can still be in and things work fine?
I had not test EFI feature, in fact, I have no experience about it. Any
progress I will promptly inform you.
>
>
> Alex
>
>
>
>
next prev parent reply other threads:[~2016-07-28 12:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 10:13 [U-Boot] [PATCH] arm: re-implement proper ISB instruction for ARMv7-A Ziyuan Xu
2016-07-28 10:39 ` Alexander Graf
2016-07-28 12:03 ` Ziyuan Xu [this message]
2016-07-28 12:41 ` Sandy Patterson
2016-07-28 11:03 ` Chen-Yu Tsai
2016-07-28 11:51 ` Ziyuan Xu
2016-07-28 22:15 ` Tom Rini
2016-07-28 23:34 ` Ziyuan Xu
2016-07-29 0:34 ` Tom Rini
2016-07-29 1:06 ` Ziyuan Xu
2016-07-29 1:12 ` Tom Rini
2016-07-29 1:30 ` Ziyuan Xu
2016-07-31 3:59 ` Ziyuan Xu
2016-07-31 14:27 ` Tom Rini
2016-08-01 1:07 ` Ziyuan Xu
2016-07-28 22:16 ` Tom Rini
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=5799F49F.5080801@rock-chips.com \
--to=xzy.xu@rock-chips.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;
as well as URLs for NNTP newsgroup(s).