| Age | Commit message (Collapse) | Author |
|---|
|
Add pci=nomsi to boot arguments for Apalis iMX8. We cannot safely use
defargs since this variabel contains downstream specific environment
variables which might not work well with upstream kernels as used by
TorizonCore.
Related-to: #52562
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Set the package version to reflect the complete Linux kernel version
plus the git hash it has been built from.
This could be done in the inc file only once, however, the Yocto
kernel recipes set PV in the individual recipies as well. The close
proximity to LINUX_VERSION also makes it obvious what PV will be.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Also drop 'sumo' from compatible release series since we have not
tested that for a long time, so it's probably not supported any more.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|
We might not go this way to support aktualizr provisioning, revert it
for now, it's to be decided how we are going to do the provisioning.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|
Bump mainline Linux kernel to Linux 5.3.2.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Use the distro boot script to load the HDMI firmware. This minimizes
the dependencies to the U-Boot environment and gives more control
to the distribution.
Related-to: #52562
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
This reverts commit 3ad48d3c8a8fa5a1364450ea101b839140656279.
Running the machine specific setup is not how distro boot should
be used. Also this breaks Colibri iMX7s (and probably Colibri
iMX6ULL) PSCI support. Revert this and fix the firmware loading
issue separately.
Related-to: #52562
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
setup function needs to be run if it's defined in uboot environment,
for instance, loadhdp is being called in it for apalis-imx8 board.
Some setup functions also take care of setting bootargs, which is safe
for torizon as well if we run setup function before bootcmd_args, since
the later will override the bootargs.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|
The image recipes do not really support rm_work, I have observed a lot
of build issues when I modified some do_image tasks while do_rootfs not
touched, to give a example:
The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
0001:
*** 0002:buildinfo(d)
0003:
File: 'meta/classes/image-buildinfo.bbclass', lineno: 67, function: buildinfo
0063:# Write build information to target filesystem
0064:python buildinfo () {
0065: if not d.getVar('IMAGE_BUILDINFO_FILE'):
0066: return
*** 0067: with open(d.expand('${IMAGE_ROOTFS}${IMAGE_BUILDINFO_FILE}'), 'w') as build:
0068: build.writelines((
0069: '''-----------------------
0070:Build Configuration: |
0071:-----------------------
so we set RM_WORK_EXCLUDE to avoid running into those problems.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|
This patch mainly aims to reintroduce a old commit 1b5ef0c9:
[ image_type_tezi.bbclass: drop some useless code ]
which was reverted later on since it did not fix the problem, I
refactor that patch to really fix it.
This patch mainly aims to reintroduce a old commit d2dc3698:
[ image_type_tezi.bbclass: drop some useless code ]
which was reverted later on since it did not fix the problem, I
refactor that patch to really fix it.
I have observed this "basehash changed" issue quite often recently, it
could be reproduced easily by the following steps:
1 bitbake imagename
2 change your system time by one day ahead.
3 bitbake imagename
After debugging it with bitbake-diffsigs, I found it's still caused by
'DATE' variable changing, as follows:
| basehash changed from ecb5b34a4997e7f037f146932728f3eca9af34d70729e4c83cdd920dc21d7677 to
| 92ad5341f99ff3a56987f4ccdc34030d5aa3e3ea1365737b5a81a12e6eb83798
| Variable DATE value changed from '20190905' to '20190906'
our tricky fix of introducing 'TDX_VERDATE' does not really work,
actually it makes things worse, 'DATE' has been deleted when parsing
IMAGE_CMD_* tasks, which was introduced by commit 4af13a48 in OE:
[ image.bbclass: delete DATE variable too ]
which means DATE would not be expanded during recipe parsing, but
TDX_VERDATE would, so we should replace TDX_VERDATE with DATE in
IMAGE_CMD_teziimg and IMAGE_CMD_teziimg-distro tasks.
To fix this annoying issue, the key point is we should avoid
expanding 'DATE' during recipe parsing stage, or else the
vardepsexclude would not take effect since the 'DATE' has already
been expanded, so we should change a DATE reference in rootfs_tezi_json
function:
d.getVar('DATE') -> d.getVar('DATE', False)
And there is seems still some order issue when bitbake handle
vardepsexclude of IMAGE_CMD_* tasks, I have to explicitly set it
for do_image_teziimg and do_image_teziimg_distro.
With the above changes, the error does not show up again.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|
Add two items into image json file: ota_provisioning and
ota_credentials.
ota_provisioning would be set 'True' if SOTA_PACKED_CREDENTIALS is
being set, and ota_credentials would be set to the basename of
SOTA_PACKED_CREDENTIALS.
These two variables would be checked in Tezi installer to determine
whether OTA provisioning is needed.
This patch would not cause any functional change in Tezi installer
while SOTA_PACKED_CREDENTIALS is not set.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|
The TEZI_KERNEL_IMAGETYPE definition has been removed, however it is still
used in the code. Change that to use KERNEL_IMAGETYPE.
The results in image.json containing '"zImage"' instead of 'null' as the
kernel filename.
Fixes c1891e02dc9c.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Provide proper PARTUUID value in bootargs.
Signed-off-by: Igor Opaniuk <igor.opaniuk@toradex.com>
|
|
|
|
Add initial version of a recipe to build the mainline based PREEMPT_RT
kernel for Toradex modules. This kernel has been maintained for
TorizonCore and is now moving to the official BSP. At this point the
kernel is working well for the platforms supported by TorizonCore,
but the hardware support hasn't been completed or verified.
The defconfig files are the same configurations as generated by the
TorizonCore kernel-cache (kernel configuration metadata) commit
fd3d3be08c05 ("features/usb-net: enable some LTE/GSM modems").
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Add initial version of a recipe to build the mainline based kernel for
Toradex modules. This kernel has been maintained for TorizonCore and
is now moving to the official BSP. At this point the kernel is working
well for the platforms supported by TorizonCore, but the hardware
support hasn't been completed or verified.
The defconfig files are the same configurations as generated by the
TorizonCore kernel-cache (kernel configuration metadata) commit
fd3d3be08c05 ("features/usb-net: enable some LTE/GSM modems").
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
The changes include:
- Introduce tezi_deploy_files helper function, it could be used to
install files listed in IMAGE_BOOT_FILES, the install logic is same
with how WIC handle IMAGE_BOOT_FILES.
- Use WKS_FILE_DEPENDS to handle the dependencies of do_image_teziimg
and do_image_teziimg_distro, when USING_WIC is not set, then we need
add WKS_FILE_DEPENDS to DEPENDS, or else it would be done in wic
image bbclass.
- Drop TEZI_KERNEL_IMAGETYPE and TEZI_KERNEL_DEVICETREE, now all the
boot files would be controlled by IMAGE_BOOT_FILES.
- Use ${IMAGE_LINK_NAME} instead of ${IMAGE_NAME}, to avoid including
DATETIME for torizon builds.
Patch has been verified on the following machines, the artifacts
generated with and wihtout the patch are identical:
- apalis-imx6
- apalis-imx8
- apalis-tk1
- apalis-tk1-mainline
- colibri-imx6
- colibri-imx6ull
- colibri-imx7
- colibri-imx8x
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|
- Inherit nopackages since it does not generate any non-empty packages.
- Drop do_compile, we can run mkimage directly in do_deploy task.
- Drop 'S = "${WORKDIR}"', we do not have to explicitly set it, the
default S would be good enough.
- Do not install DEPLOYDIR, that is not necessary, it's already done
in deploy.bbclass.
- Do not set noexec flag to do_install, do_populate_sysroot, they are
basically empty tasks, making do_populate_sysroot noexec also will
cause QA warning when u-boot-distro-boot is set to DEPENDS in other
recipes.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|
The i.MX8 kernel is currently 20MB and doesn't fit in the hard coded 16MB
boot partition size.
Set the boot partition size dynamically to twice the payload size
rounded up to the next power of 2, but at least to 16MB.
The Apalis iMX8 needs additional firmware for HDMI in the boot partition.
Provide a new MACHINE_BOOT_FILES variable which adds to the list of to be
installed files.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
With thud I still see "basehash value changed" errors, even though the
commit e74158b6c is available in the OE thud branch.
This reverts commit 9f84ffa4b42b4d518191116614aef269ab227f0e.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
This creates a distro boot script boot.scr and deploys it into
the ${DEPLOYDIR}.
Moved here from meta-toradex-torizon u-boot-distro-boot-ostree.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Signed-off-by: Dominik Sliwa <dominik.sliwa@toradex.com>
(cherry picked from commit 8109e0a87240489e6bc698e79f2cc748cbe40b17)
(cherry picked from commit 95e057e986e782e85c7ed37e61d27ff389ea4239)
|
|
Signed-off-by: Dominik Sliwa <dominik.sliwa@toradex.com>
(cherry picked from commit d02ed084d1c4a13e77898affc1b48beabef956f4)
(cherry picked from commit 5bf79f8880f4193bd9c7fd490a25c90383aa0514)
|
|
Backports based on 4.19 kernel.
Signed-off-by: Dominik Sliwa <dominik.sliwa@toradex.com>
(cherry picked from commit 78e1cdabe0baeb794945bd4926c28058f9f12aa9)
(cherry picked from commit 5d59a8eddb01c439281970496529e0e9a3d6f493)
|
|
Backports based on 4.19 kernel.
Signed-off-by: Dominik Sliwa <dominik.sliwa@toradex.com>
(cherry picked from commit 56829b6d643fa5dfdac42c0adddf5d41e7fb982e)
(cherry picked from commit 85f6a85b8a8cc400a6f4e201ff5c5cbc43ac1d85)
|
|
Add the product name at compile time so that we do not need to provide
slightly different copies of the file.
While at it set package arch to machine arch. The packages created are
machine specific due to the g1.schema file.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 3fa96f28bb30643cac3b8a49d3abd7c976acb704)
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 88fbe7232ef49a4564de97c0e676a66577986f43)
|
|
We decided we won't do a BSP 3.0 for Vybrid.
For new designs we recommend ULL now.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 0f57f7913867e70ec691eaf31d4a74dd0becb0d4)
|
|
This machine hasn't been used nor updated in years.
The SoM's are discontinued by now.
Drop it.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
The default setting is now done in the distro.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Check whether argument two is given before passing it to basename.
This avoids build failure when building without deploying device
trees in the bootfs (e.g. TorizonCore).
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Aarch64 typically stores device trees in subdirectories, e.g.
freescale/fsl-imx8qm-apalis.dtb. However, the kernel-devicetree.bbclass
deploys those files without subdirectory. Make sure the Tezi image class
behaves like the kernel-devicetree.bbclass.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
There are quite a few common code being shared by rootfs_tezi_rawnand
and rootfs_tezi_distro_rawnand, we should merge them to a same function
to avoid being redundant.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
We have generic prepare.sh and wrapup.sh scripts hence tezi-metadata
is buildable and useable for any machine.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Replace hard-coded tar.xz by TEZI_ROOT_SUFFIX since the rootfs image
suffix is being controlled by that variable.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
We currently have some tricky code intended to get rid of the
"basehash value changed" errors, but they are actually not needed.
Since the references to "DATE" only exist in image tasks or their
prefuncs, so they would be expanded at task executing time but not
recipe parsing time, a 'vardepsexclude' flag would be enough in this
case.
I guess the reason we introduced this piece of code was that we
found we still could see the annoying "basehash value changed" errors
with 'vardepsexclude' flag set at that moment, but that's probably was
not caused by our code, it's actually another issue now had been fixed
in OE by e74158b6cc1d683ab14ef5d47ec531f986fc2259:
[ rm_work: sort the value of do_build dependencies ]
We can safely drop these useless code per my test.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
Since oe-core commit 3150253898ba ("systemd-conf: simplify
creation of machine-specific configuration") systemd-conf no
longer unpacks the systemd sources. Hence the patch which patches
units/systemd-udevd.service.in does no longer apply.
Apply the patch in the systemd recipe instead.
The systemd-udevd.service file is only deployed in a package
built from the systemd recipe anyway, hence this also makes sure
that the patched file gets actually deployed.
This essentially reverts commit 118f6b1b17b6 ("systemd: follow
recipe split which added systemd-conf").
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Including u-boot-toradex-initial-env.inc will generate a uEnv.txt
for newer U-Boot versions using U-Boot's u-boot-initial-env
Makfile target. It essential does what u-boot-toradex-env.inc did
before.
Note: Since there is now support for an exported environment in
upstream U-Boot, we should upstream the OE logic to the official
U-Boot too.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Upstream has changes in the context lines.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
The patch is not obsolete AFAIKT.
i.e. the configuration file should NOT make mounts by udevd private or
other processes will not be able to see the mount.
This reverts commit 3640a12c85df4ac180e38f19038072df6b1d6d55.
|
|
That patch has been merged to systemd-conf.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
Or else the changes for systemd-conf recipe will be missed.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
The systemd configuration has been split from the systemd recipe.
Thus we need to move our changes to the systemd configuration.
While at it drop the kmod packageconfig. This was only needed with angstrom.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
These machines use an old Nvidia provided downstream kernel 3.1.10. They no
longer much the way more recent sysroot components, e.g. libc, xserver et. al.
The maintance burden to keep the userspace components in their old version
becomes simply to high. Keep using the rocko based 2.8 BSP for these machines.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
With the removal of angstrom we can drop this workaround.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Drop bootfs_get_size since it has a obvious flaw, it's being called in
both do_image_teziimg and do_image_teziimg_distro but the boot files of
these two tasks are different.
Drop rootfs_get_size, it's trying to get the size of IMAGE_ROOTFS
directory, but in some cases, that is not correct, for instance, when
TEZI_ROOT_SUFFIX is 'ota.tar.gz', the rootfs directory should be
OTA_SYSROOT rather than IMAGE_ROOTFS.
Introduce get_uncompressed_size function, it reads the image size from
a image-size file in ${T} directory, and that image size is written into
this file by the image functions when they making the tarballs.
Also split the duplicated bootfs tarball creating code to a common
function create_bootfs, and it must run as a prefuncs before
rootfs_tezi_run_json and rootfs_tezi_run_distro_json, this ensures the
image size has been written to the file when the later functions run.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
[use _append for tar commands]
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
