public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 1/2] armv8: Support loading 32-bit OS in AArch32 execution state
Date: Thu, 7 Jul 2016 14:58:32 +0200	[thread overview]
Message-ID: <577E51F8.8020702@suse.de> (raw)
In-Reply-To: <CAD0U-hK2hi6vMdfP7YoVMJgb9Aa4bF1XTx1-xOQ3RgD34brVmA@mail.gmail.com>

On 07/07/2016 02:46 PM, Ryan Harkin wrote:
> On 7 July 2016 at 13:41, Alexander Graf <agraf@suse.de> wrote:
>> On 07/07/2016 02:35 PM, Ryan Harkin wrote:
>>> On 7 July 2016 at 13:30, Alexander Graf <agraf@suse.de> wrote:
>>>> On 07/07/2016 02:16 PM, Ryan Harkin wrote:
>>>>> On 7 July 2016 at 07:30, Alison Wang <b18965@freescale.com> wrote:
>>>>>> To support loading a 32-bit OS, the execution state will change from
>>>>>> AArch64 to AArch32 when jumping to kernel.
>>>>>>
>>>>>> The architecture information will be got through checking FIT image,
>>>>>> then U-Boot will load 32-bit OS or 64-bit OS automatically.
>>>>>>
>>>>>> Signed-off-by: Ebony Zhu <ebony.zhu@nxp.com>
>>>>>> Signed-off-by: Alison Wang <alison.wang@nxp.com>
>>>>>> Signed-off-by: Chenhui Zhao <chenhui.zhao@nxp.com>
>>>>> Unfortunately, this patch fails to boot for me.
>>>>>
>>>>> On FVP Foundation models, I see this error before the model hangs:
>>>>>
>>>>> [snip]
>>>>> Starting kernel ...
>>>>>
>>>>> resetting ...
>>>>> [snip]
>>>>>
>>>>> And I see the same output on AEMv8 Base models and Juno boards, only
>>>>> they reset continuously rather than hang.
>>>>>
>>>>> I think the problem is that I see this from ARM Trusted Firmware on
>>>>> boot:
>>>>>
>>>>> INFO:    BL31: Preparing for EL3 exit to normal world
>>>>>
>>>>> Looking at the patch, it appears to be changing everything to boot in
>>>>> EL2.
>>>>
>>>> That was the case before the patch (with the removal of the EL1 boot
>>>> thing)
>>>> already. Linux can't run in EL3, that's why it has to boot in EL2 (or
>>>> EL1,
>>>> but that really should be limited to VMs).
>>>>
>>> Pah!  I misread the patch, specifically this hunk (and the one before
>>> it, I suppose):
>>>
>>> diff --git a/arch/arm/lib/bootm.c b/arch/arm/lib/bootm.c
>>> index e3c9832..59adab8 100644
>>> --- a/arch/arm/lib/bootm.c
>>> +++ b/arch/arm/lib/bootm.c
>>> @@ -193,7 +193,6 @@ static void do_nonsec_virt_switch(void)
>>>    {
>>>        smp_kick_all_cpus();
>>>        dcache_disable();    /* flush cache before swtiching to EL2 */
>>> -    armv8_switch_to_el2();
>>>    }
>>>    #endif
>>>
>>> That's a "-", not a "+" on the call to armv8_switch_to_el2().
>>>
>>> Either way, all my platforms are dead with this patch.
>>
>> Since you're running in software models, can you try to figure out where
>> exactly it breaks?
> You assume that because I have a model that I have the ability to debug it ;-)
>
> ARM's FVP Foundation model is publicly available and free to use.  So
> if you want to give it a spin, it's there for the taking.

I thought the Foundation model doesn't support external debugging? I'd 
basically want to put a breakpoint at the point where the kernel exit 
print goes and then trace it from there :).

But since Alison wrote the patches, I'm sure he can do that too :).


Alex

  reply	other threads:[~2016-07-07 12:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07  6:30 [U-Boot] [PATCH v5 0/2] armv8: Support loading 32-bit OS in AArch32 execution state Alison Wang
2016-07-07  6:30 ` [U-Boot] [PATCH v5 1/2] " Alison Wang
2016-07-07 12:16   ` Ryan Harkin
2016-07-07 12:30     ` Alexander Graf
2016-07-07 12:35       ` Ryan Harkin
2016-07-07 12:41         ` Alexander Graf
2016-07-07 12:46           ` Ryan Harkin
2016-07-07 12:58             ` Alexander Graf [this message]
2016-07-07  6:30 ` [U-Boot] [PATCH v5 2/2] armv8: fsl-layerscape: SMP support for loading 32-bit OS Alison Wang

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=577E51F8.8020702@suse.de \
    --to=agraf@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox