[PATCH] travis: Setup latest qemu version for Versal

[PATCH] travis: Setup latest qemu version for Versal

[Michal Simek]

Qemu v4.2.0 maps bootmode registers to address space which was the reason
why board_late_init() was disabled and accesses were failing.

With new Qemu board_late_init() can be called without any issue.

Signed-off-by: Michal Simek <michal.simek@xilinx.com>
---

Not sure which qemu version azure and gitlab are using but I think that
also make sense to move the whole travis to v4.2.
As of now I am sending this patch to open that discussion.
---
 .travis.yml                          | 1 +
 configs/xilinx_versal_virt_defconfig | 1 -
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/.travis.yml b/.travis.yml
index 5da046ca7ed5..168455bd9f68 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -514,6 +514,7 @@ matrix:
         - TEST_PY_BD="xilinx_versal_virt"
           TEST_PY_TEST_SPEC="not sleep"
           QEMU_TARGET="aarch64-softmmu"
+          QEMU_VERSION="v4.2.0"
           TEST_PY_ID="--id qemu"
           BUILDMAN="^xilinx_versal_virt$"
     - name: "test/py xtfpga"
diff --git a/configs/xilinx_versal_virt_defconfig b/configs/xilinx_versal_virt_defconfig
index 11428e1e03c1..6488bca2c004 100644
--- a/configs/xilinx_versal_virt_defconfig
+++ b/configs/xilinx_versal_virt_defconfig
@@ -9,7 +9,6 @@ CONFIG_FIT_VERBOSE=y
 # CONFIG_ARCH_FIXUP_FDT_MEMORY is not set
 CONFIG_BOOTDELAY=5
 CONFIG_SUPPORT_RAW_INITRD=y
-# CONFIG_BOARD_LATE_INIT is not set
 # CONFIG_DISPLAY_CPUINFO is not set
 CONFIG_BOARD_EARLY_INIT_R=y
 CONFIG_HUSH_PARSER=y
-- 
2.24.0

[PATCH] travis: Setup latest qemu version for Versal

[Tom Rini]

On Tue, Dec 17, 2019 at 03:41:40PM +0100, Michal Simek wrote:
> Qemu v4.2.0 maps bootmode registers to address space which was the reason
> why board_late_init() was disabled and accesses were failing.
> 
> With new Qemu board_late_init() can be called without any issue.
> 
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
> 
> Not sure which qemu version azure and gitlab are using but I think that
> also make sense to move the whole travis to v4.2.
> As of now I am sending this patch to open that discussion.

OK, so, the Azure and GitLab are both controlled by
https://gitlab.denx.de/u-boot/gitlab-ci-runner/blob/master/Dockerfile so
we just change
https://gitlab.denx.de/u-boot/gitlab-ci-runner/blob/master/Dockerfile#L137
and use v4.2 for all, which I agree we should do for travis as well.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20191230/6dd8ccb8/attachment.sig>

[PATCH] travis: Setup latest qemu version for Versal

[Michal Simek]

Hi,

On 30. 12. 19 16:14, Tom Rini wrote:
> On Tue, Dec 17, 2019 at 03:41:40PM +0100, Michal Simek wrote:
>> Qemu v4.2.0 maps bootmode registers to address space which was the reason
>> why board_late_init() was disabled and accesses were failing.
>>
>> With new Qemu board_late_init() can be called without any issue.
>>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>> ---
>>
>> Not sure which qemu version azure and gitlab are using but I think that
>> also make sense to move the whole travis to v4.2.
>> As of now I am sending this patch to open that discussion.
> 
> OK, so, the Azure and GitLab are both controlled by
> https://gitlab.denx.de/u-boot/gitlab-ci-runner/blob/master/Dockerfile so
> we just change
> https://gitlab.denx.de/u-boot/gitlab-ci-runner/blob/master/Dockerfile#L137
> and use v4.2 for all, which I agree we should do for travis as well.

Good.
I have sent a patch to update it to v4.2 but untested.
I will run gitlab and travis session.

Thanks,
Michal