On 2020/9/28 20:57, Geert Uytterhoeven wrote:
> Hi Zhen,
>
> On Mon, Sep 28, 2020 at 2:15 PM Ard Biesheuvel wrote:
>> On Mon, 28 Sep 2020 at 13:57, Leizhen (ThunderTown)
>> wrote:
>>> On 2020/9/28 18:14, Ard Biesheuvel wrote:
On Mon, 28 Sep 2020 at 11:27, Zhen Lei wrote:
>
>
Hi Zhen,
On Mon, Sep 28, 2020 at 2:15 PM Ard Biesheuvel wrote:
> On Mon, 28 Sep 2020 at 13:57, Leizhen (ThunderTown)
> wrote:
> > On 2020/9/28 18:14, Ard Biesheuvel wrote:
> > > On Mon, 28 Sep 2020 at 11:27, Zhen Lei wrote:
> > >>
> > >> mov r4, pc
> > >> and r4, r4, #0xf800
On Mon, 28 Sep 2020 at 13:57, Leizhen (ThunderTown)
wrote:
>
>
>
> On 2020/9/28 18:14, Ard Biesheuvel wrote:
> > On Mon, 28 Sep 2020 at 11:27, Zhen Lei wrote:
> >>
> >> mov r4, pc
> >> and r4, r4, #0xf800 //truncated to 128MiB boundary
> >> add r4, r4, #TEXT_OFFSET
On 2020/9/28 18:14, Ard Biesheuvel wrote:
> On Mon, 28 Sep 2020 at 11:27, Zhen Lei wrote:
>>
>> mov r4, pc
>> and r4, r4, #0xf800 //truncated to 128MiB boundary
>> add r4, r4, #TEXT_OFFSET//PA(_start)
>>
>> Currently, the decompressed kernel must be placed at the
On Mon, 28 Sep 2020 at 11:27, Zhen Lei wrote:
>
> mov r4, pc
> and r4, r4, #0xf800 //truncated to 128MiB boundary
> add r4, r4, #TEXT_OFFSET//PA(_start)
>
> Currently, the decompressed kernel must be placed at the position: 128MiB
> boundary + TEXT_OFFSET. This limitation
mov r4, pc
and r4, r4, #0xf800 //truncated to 128MiB boundary
add r4, r4, #TEXT_OFFSET//PA(_start)
Currently, the decompressed kernel must be placed at the position: 128MiB
boundary + TEXT_OFFSET. This limitation is just because we masked PC with
0xf8000. Actually, we
6 matches
Mail list logo