On Fri, May 10, 2019 at 03:14:40PM +, Pankaj Bansal wrote:
>
>
> > -Original Message-
> > From: Tom Rini
> > Sent: Friday, 10 May, 2019 08:36 PM
> > To: Pankaj Bansal
> > Cc: u-boot@lists.denx.de; Prabhakar Kushwaha
> > ; Varun Sethi
> > Subject: Re: [EXT] Re: [ARMv8] kernel entry
> -Original Message-
> From: Tom Rini
> Sent: Friday, 10 May, 2019 08:36 PM
> To: Pankaj Bansal
> Cc: u-boot@lists.denx.de; Prabhakar Kushwaha
> ; Varun Sethi
> Subject: Re: [EXT] Re: [ARMv8] kernel entry point
>
> On Fri, May 10, 2019 at 02:40:52PM +, Pankaj Bansal wrote:
> > Hi
On Fri, May 10, 2019 at 02:40:52PM +, Pankaj Bansal wrote:
> Hi Tom,
>
> Further update.
> I asked this question to linux maintainer, and he pointed out that load
> address that I am using is not correct.
> The linux load address should be (2 MB aligned + text_offset).
> The text_offset can
Hi Tom,
Further update.
I asked this question to linux maintainer, and he pointed out that load address
that I am using is not correct.
The linux load address should be (2 MB aligned + text_offset).
The text_offset can be obtained from first 64 bytes in linux Image.
For our use case it comes out
On further testing I tried to boot the linux from ATF
(https://github.com/ARM-software/arm-trusted-firmware)
Without using u-boot
Even with ATF, the linux is not able to boot from 0x8100, but is able to
boot from 0x8008
Seems like linux issue and not u-boot issue.
I will ask this
Hi Tom,
In order to determine whether linux entry point has been called or not, I put a
loop in kernel:
diff --git a/arch/arm64/kernel/head.S b/arch/arm64/kernel/head.S
index 261f3f88364c..dea6cb8baa6a 100644
--- a/arch/arm64/kernel/head.S
+++ b/arch/arm64/kernel/head.S
@@ -80,6 +80,7 @@ _head:
> -Original Message-
> From: Tom Rini
> Sent: Monday, 6 May, 2019 06:59 PM
> To: Pankaj Bansal
> Cc: u-boot@lists.denx.de; Prabhakar Kushwaha
> ; Varun Sethi
> Subject: [EXT] Re: [ARMv8] kernel entry point
>
> On Mon, May 06, 2019 at 01:06:45PM +, Pankaj Bansal wrote:
>
> > Hi
7 matches
Mail list logo
