Hi Bhupesh,
> U-boot doesn't have ARM trusted firmware support as of now. U-boot for
> ARMv8 starts in EL3, whereas UEFI starts in EL2 as trusted firmware itself
> is working in EL3.
Since the ATF software doesn't really care whether it is loading uefi or
u-boot
and since it wants to load non
On 14-01-22 04:29 PM, Scott Wood-2 [via U-Boot] wrote:
>
>
> On Tue, 2014-01-14 at 09:52 +0800, FengHua wrote:
>> hi bhupesh,
>>
>>> Hi David,
>>>
>>> In reference to my mail above, I see that the transition to EL2 (from EL3)
>>> which occurs very early
>>> in start.S needs to be changed on line
On 14-01-25 11:46 AM, bhupesh.sha...@freescale.com [via U-Boot] wrote:
>
>
>>
>> However, if we set up u-boot so that it can wake up at any security
>> level and migrate to non-secure EL1, that might be a nice compromise.
>> But having specific EL3 startup assumptions and code that is always
>>
Hello,
If it helps, I would respectfully like to add that I reverted this change
and it fixes my problem nicely. I'm on an ARM platform (not yet upstreamed
to u-boot), with a microSD card inserted with valid files on it that I can
read on other systems. I have an Oct 16, 2013 version of U-Boot 201
I reverted my local change and the directory listing shows no duplicates
anymore which is surprising. An inspection of the generated assembly shows
more or less the same code with the exception of the early branch taken if
'dols' is 0. The 16/8 comparison is still awkward, but at this point I'm not
5 matches
Mail list logo
