LinuxImage4.0

Technical Support
, , , ,
1

I’ve been trying to get the LinuxImage4.0 to work. I’ve followed this tutorial, but I’ve changed few commands to download the LinuxImage4.0.

I used

repo init -u http://git.toradex.com/toradex-bsp-platform.git -b LinuxImage4.0 -m default.xml

to initialize the repo’s repository, but upon building the image with the bitbake -k graphical-tdx-image, the kernel built is still on 4.19, which shouldn’t be the case, as the LinuxImage4.0, aka zeus, uses kernel 5.4.

Is there something I’m doing wrong or something I forgot to consider?

2

Hi

LinuxImage4.0 is still under development, so do not expect anything useful resulting from your builds and it is expected to be released in Q2.

Max

3

I do understand that, but I’m doing it just to test something out with the kernel versions.

What I was wondering about is, when I init the repo, I get that manifest.xml file, which should contain different branches that should be pulled (if I understood that correctly), but even with all of them set to zeus (default on LinuxImage4.0), warrior and thud are downloaded instead.

Would there be a way to bypass that?

4

Hi

Just to stress it again:

LinuxImage4.0 is still under development, so do not expect anything useful resulting from your builds and it is expected to be released in Q2.

You could use the integration.xml manifest which checks out HEAD of the specified branches for meta-toradex-*. E.g.:

repo init -u http://git.toradex.com/toradex-bsp-platform.git -b LinuxImage4.0 -m default.xml
repo sync

Max