On 07/07/2016 02:46 PM, Ryan Harkin wrote:
On 7 July 2016 at 13:41, Alexander Graf wrote:
On 07/07/2016 02:35 PM, Ryan Harkin wrote:
On 7 July 2016 at 13:30, Alexander Graf wrote:
On 07/07/2016 02:16 PM, Ryan Harkin wrote:
On 7 July 2016 at 07:30, Alison Wang
On 7 July 2016 at 13:41, Alexander Graf wrote:
> On 07/07/2016 02:35 PM, Ryan Harkin wrote:
>>
>> On 7 July 2016 at 13:30, Alexander Graf wrote:
>>>
>>> On 07/07/2016 02:16 PM, Ryan Harkin wrote:
On 7 July 2016 at 07:30, Alison Wang
On 07/07/2016 02:35 PM, Ryan Harkin wrote:
On 7 July 2016 at 13:30, Alexander Graf wrote:
On 07/07/2016 02:16 PM, Ryan Harkin wrote:
On 7 July 2016 at 07:30, Alison Wang wrote:
To support loading a 32-bit OS, the execution state will change from
AArch64
On 7 July 2016 at 13:30, Alexander Graf wrote:
> On 07/07/2016 02:16 PM, Ryan Harkin wrote:
>>
>> On 7 July 2016 at 07:30, Alison Wang wrote:
>>>
>>> To support loading a 32-bit OS, the execution state will change from
>>> AArch64 to AArch32 when jumping to
On 07/07/2016 02:16 PM, Ryan Harkin wrote:
On 7 July 2016 at 07:30, Alison Wang 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,
On 7 July 2016 at 07:30, Alison Wang 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
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
7 matches
Mail list logo