[Buildroot] Bump ATF version in arm_juno_defconfig ?

[Buildroot] Bump ATF version in arm_juno_defconfig ?

[Thomas Petazzoni]

Hello Joao,

You originally contributed the arm_juno_defconfig in Buildroot. It
currently uses v1.2 of ATF, and I encountered a build failure with this
ATF version as part of the Buildroot test suite:

    ./build/juno/release/bl1/context_mgmt.o: In function `cm_prepare_el3_exit':
    context_mgmt.c:(.text.cm_prepare_el3_exit+0x54): undefined reference to `cm_set_next_context'
    context_mgmt.c:(.text.cm_prepare_el3_exit+0x54): relocation truncated to fit: R_AARCH64_JUMP26 against undefined symbol `cm_set_next_context'

This issue has been fixed since ATF v1.3. Do you think you could
provide a patch bumping the ATF version ? The latest version is ATF
v1.5, so if you could bump the defconfig, it would be nice.

In addition, it would be great if you could send a patch adding
yourself in the DEVELOPERS file for this platform, so we easily know who
to contact for questions related to this platform.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] Bump ATF version in arm_juno_defconfig ?

[Joao Pinto]

Hi Thomas,

Hope you are doing fine!

?s 9:17 PM de 4/23/2018, Thomas Petazzoni escreveu:
> Hello Joao,
> 
> You originally contributed the arm_juno_defconfig in Buildroot. It
> currently uses v1.2 of ATF, and I encountered a build failure with this
> ATF version as part of the Buildroot test suite:
> 
>     ./build/juno/release/bl1/context_mgmt.o: In function `cm_prepare_el3_exit':
>     context_mgmt.c:(.text.cm_prepare_el3_exit+0x54): undefined reference to `cm_set_next_context'
>     context_mgmt.c:(.text.cm_prepare_el3_exit+0x54): relocation truncated to fit: R_AARCH64_JUMP26 against undefined symbol `cm_set_next_context'
> 
> This issue has been fixed since ATF v1.3. Do you think you could
> provide a patch bumping the ATF version ? The latest version is ATF
> v1.5, so if you could bump the defconfig, it would be nice.
> 
> In addition, it would be great if you could send a patch adding
> yourself in the DEVELOPERS file for this platform, so we easily know who
> to contact for questions related to this platform.
> 
> Thanks!
> 
> Thomas
> 

My team member Gustavo will check this out and he will be the maintainer if it
is ok for you.

Thanks,
Joao

[Buildroot] Bump ATF version in arm_juno_defconfig ?

[Thomas Petazzoni]

Hello,

On Mon, 28 May 2018 17:52:07 +0100, Joao Pinto wrote:

> My team member Gustavo will check this out and he will be the
> maintainer if it is ok for you.

Sure, thanks! Nice to meet you Gustavo.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] Bump ATF version in arm_juno_defconfig ?

[Thomas Petazzoni]

Hello,

On Mon, 28 May 2018 17:52:07 +0100, Joao Pinto wrote:

> > You originally contributed the arm_juno_defconfig in Buildroot. It
> > currently uses v1.2 of ATF, and I encountered a build failure with this
> > ATF version as part of the Buildroot test suite:
> > 
> >     ./build/juno/release/bl1/context_mgmt.o: In function `cm_prepare_el3_exit':
> >     context_mgmt.c:(.text.cm_prepare_el3_exit+0x54): undefined reference to `cm_set_next_context'
> >     context_mgmt.c:(.text.cm_prepare_el3_exit+0x54): relocation truncated to fit: R_AARCH64_JUMP26 against undefined symbol `cm_set_next_context'
> > 
> > This issue has been fixed since ATF v1.3. Do you think you could
> > provide a patch bumping the ATF version ? The latest version is ATF
> > v1.5, so if you could bump the defconfig, it would be nice.
> > 
> > In addition, it would be great if you could send a patch adding
> > yourself in the DEVELOPERS file for this platform, so we easily know who
> > to contact for questions related to this platform.
> 
> My team member Gustavo will check this out and he will be the maintainer if it
> is ok for you.

Following this discussion, Gustavo never sent any patch to fix
arm_juno_defconfig, and the ATF build broken was still broken as of
today. So I went ahead, and bumped the ATF version to 1.3, to at least
fix the build issue.

It would be nice if you could give it a test on the actual hardware,
and perhaps bump ATF to an ever newer version.

See
https://git.buildroot.org/buildroot/commit/?id=395bc11dde5b4ef034118a9be568131f134daaa3
for details.

Best regards,

Thomas Petazzoni
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] Bump ATF version in arm_juno_defconfig ?

[Joao Pinto]

Hello Thomas,

?s 4:03 PM de 8/12/2018, Thomas Petazzoni escreveu:
> Hello,
> 
> On Mon, 28 May 2018 17:52:07 +0100, Joao Pinto wrote:
> 
>>> You originally contributed the arm_juno_defconfig in Buildroot. It
>>> currently uses v1.2 of ATF, and I encountered a build failure with this
>>> ATF version as part of the Buildroot test suite:
>>>
>>>     ./build/juno/release/bl1/context_mgmt.o: In function `cm_prepare_el3_exit':
>>>     context_mgmt.c:(.text.cm_prepare_el3_exit+0x54): undefined reference to `cm_set_next_context'
>>>     context_mgmt.c:(.text.cm_prepare_el3_exit+0x54): relocation truncated to fit: R_AARCH64_JUMP26 against undefined symbol `cm_set_next_context'
>>>
>>> This issue has been fixed since ATF v1.3. Do you think you could
>>> provide a patch bumping the ATF version ? The latest version is ATF
>>> v1.5, so if you could bump the defconfig, it would be nice.
>>>
>>> In addition, it would be great if you could send a patch adding
>>> yourself in the DEVELOPERS file for this platform, so we easily know who
>>> to contact for questions related to this platform.
>>
>> My team member Gustavo will check this out and he will be the maintainer if it
>> is ok for you.
> 
> Following this discussion, Gustavo never sent any patch to fix
> arm_juno_defconfig, and the ATF build broken was still broken as of
> today. So I went ahead, and bumped the ATF version to 1.3, to at least
> fix the build issue.

We are focused in top priority issues that don't include the ARM Juno platform
at the moment, so I apologize for the delay.

> 
> It would be nice if you could give it a test on the actual hardware,
> and perhaps bump ATF to an ever newer version.

Yes we will do that, thanks.

> 
> See
> https://urldefense.proofpoint.com/v2/url?u=https-3A__git.buildroot.org_buildroot_commit_-3Fid-3D395bc11dde5b4ef034118a9be568131f134daaa3&d=DwICAg&c=DPL6_X_6JkXFx7AXWqB0tg&r=s2fO0hii0OGNOv9qQy_HRXy-xAJUD1NNoEcc3io_kx0&m=5bh5AR12AC1liXRzkOXOJdxgehZPpCPel3tK_o4KxRY&s=cFDUqDTSi6slvtHyLlB1XzOjt1M9trCh6pctM1odcok&e=
> for details.
> 
> Best regards,
> 
> Thomas Petazzoni
> 

best regards,
Joao Pinto

[Buildroot] Bump ATF version in arm_juno_defconfig ?

[Gustavo Pimentel]

Hello Thomas,

On 12/08/2018 16:03, Thomas Petazzoni wrote:
> Hello,
> 
> On Mon, 28 May 2018 17:52:07 +0100, Joao Pinto wrote:
> 
>>> You originally contributed the arm_juno_defconfig in Buildroot. It
>>> currently uses v1.2 of ATF, and I encountered a build failure with this
>>> ATF version as part of the Buildroot test suite:
>>>
>>>     ./build/juno/release/bl1/context_mgmt.o: In function `cm_prepare_el3_exit':
>>>     context_mgmt.c:(.text.cm_prepare_el3_exit+0x54): undefined reference to `cm_set_next_context'
>>>     context_mgmt.c:(.text.cm_prepare_el3_exit+0x54): relocation truncated to fit: R_AARCH64_JUMP26 against undefined symbol `cm_set_next_context'
>>>
>>> This issue has been fixed since ATF v1.3. Do you think you could
>>> provide a patch bumping the ATF version ? The latest version is ATF
>>> v1.5, so if you could bump the defconfig, it would be nice.
>>>
>>> In addition, it would be great if you could send a patch adding
>>> yourself in the DEVELOPERS file for this platform, so we easily know who
>>> to contact for questions related to this platform.
>>
>> My team member Gustavo will check this out and he will be the maintainer if it
>> is ok for you.
> 
> Following this discussion, Gustavo never sent any patch to fix
> arm_juno_defconfig, and the ATF build broken was still broken as of
> today. So I went ahead, and bumped the ATF version to 1.3, to at least
> fix the build issue.
> 
> It would be nice if you could give it a test on the actual hardware,
> and perhaps bump ATF to an ever newer version.
> 
> See
> https://urldefense.proofpoint.com/v2/url?u=https-3A__git.buildroot.org_buildroot_commit_-3Fid-3D395bc11dde5b4ef034118a9be568131f134daaa3&d=DwICAg&c=DPL6_X_6JkXFx7AXWqB0tg&r=bkWxpLoW-f-E3EdiDCCa0_h0PicsViasSlvIpzZvPxs&m=GzjOJmjDDu3IEntiAG3pjUOTl40vfRpK8Kkwk-GuiLU&s=IoS7aorxXnFFePzfVA2rnT5SL95Frgn5RmLduEGTI6k&e=
> for details.

Sorry for the delay, but I was focus in another topic. I've sent a new patch
bumping to ATF to v1.4. For some reason the v1.5 wasn't able to boot.

> 
> Best regards,
> 
> Thomas Petazzoni
> 

Regards,
Gustavo