Differences in generated config

Technical Support
, ,
1

I am unable to generated a .config identical to the one pulled from a device. There are 2 differences:

CONFIG_LOCALVERSION

  • Generated is shows =""
  • From device shows ="-3.0.4"

CONFIG_MXC_GPU_VIV The generated .config has this enabled via =y, while the device does not have this set.

Can someone explain this difference? I would like to make modifications to the config to enable tracefs, but would some assurance that those will be the only modifications.

2

HI @fettersa

Thanks for writing to the Toradex Community!

Which branch with which git revision did you compile?

Best regards,
Jaski

3

@jaski.tx I generated the config at SHA baa6c24240a4c9e871e14c056a3485f98fef4dee on branch toradex_4.14-2.0.x-imx

4

I may be confused. The SHA is correct, but I am not confident it is on the toradex_4.14-2.0.x-imx branch. I assumed it was since the Kernel build instructions list it Build U-Boot and Linux Kernel from Source Code | Toradex Developer Center

Some investigation reveals baa6c24240a4c9e871e14c056a3485f98fef4dee to be on toradex_4.14-2.3.x-imx branch. Is the documentation I linked to out of date? Where should I be building from?

5

Hi

You are right. It is the toradex_4.14-2.3.x-imx branch. We will update the documentation soon.

Best regards,
Jaski

6

I am still having this issue on baa6c24240a4c9e871e14c056a3485f98fef4dee

7

May I ask which issues are you having?

8

The generated config does not match the one pulled from the device. I generated the config while on the Apalis-iMX8_Console-Image_3.0b4.254-20200421 tag.

9

Hi @fettersa

Regarding your issue, an OpenEmbedded build will change the config in two points:

  • LOCALVERSION_AUTO in the the following .bbclass, what is printed as kernel and also module verison
  • CONFIG_MXC_GPU_VIV in the following .bbclass, since in the OpenEmbedded Build this driver is build as external module. The advantage of this is the version of the kernel has not absolutely to match with the version of grahic components in UserSpace.Therefore you see these differences.

For a Build outside of OpenEmbedded, you should ignore the LOCALVERSION and set the CONFIG_MXC_GPU_VIV to y. Hence you need to create the kernel modules by yourself and copy them to the SoM.

Best regards,
Jaski

10

Thanks for the clarification. Is OpenEmbedded the supported build method for the LinuxBSP’s available on BSP Layers and Reference Images for Yocto Project Software | Toradex Developer Center ?

I had assumed that the instructions here were how the image was generated: Build U-Boot and Linux Kernel from Source Code | Toradex Developer Center

Is it possible to modify the configuration in OpenEmbedded? Specifically I’m wanting to enable tracefs support (via CONFIG_TRACING and CONFIG_FTRACE among others).

11

Hi

Is OpenEmbedded the supported build method for the LinuxBSP’s available on BSP Layers and Reference Images for Yocto Project Software | Toradex Developer Center ?

Yes. Please have a look here.

Is it possible to modify the configuration in OpenEmbedded?

Yes, it is discussed here.

Best regards,
Jaski