| Age | Commit message (Collapse) | Author |
|---|
|
For the Toradex Easy Installer update to the last git hash before the
device tree resp. overlay re-work of late.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Lock use-head-next to the last git hash before the device tree resp.
overlay re-work of late.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
NAND support may help (;-p).
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Both colibri-imx7 use the same defconfig, however we do not have a
common mx7 override so provide it for each machine.
Add a apalis-tk1-mainline defconfig using the 4.19.59 tegra_defconfig
with enabled CONFIG_PREEMPT_RT_FULL.
Add a default defconfig, use the 4.19.59 arm64 defconfig with enabled
CONFIG_PREEMPT_RT_FULL.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 60f4dbc77be23abfe2995f9f2bd448694157d020)
|
|
Both colibri-imx7 use the same defconfig, only provide it once.
Add a apalis-tk1-mainline defconfig using the 5.4.6 tegra_defconfig.
Add a default defconfig, use the 5.4.6 arm64 defconfig.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit f9d7fe8962838dbb8a166f8ec991b397fde28a5f)
(cherry picked from commit 47bba89a6a09dc0e353cabb343b04f9322f7e3c2)
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Using the only backported versions of mwifiex, cfg80211 and lib80211
allows to avoid several sporadical bugs about wrong dependencies
from built-in modules to backports modules and vice versa.
Related-to: ELB-2687
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Related-to: ELB-2686
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
With common depmod config file, the backported rtl8188eu driver
tries to load for Realtek 8188EU USB devices. On the other hand,
on-module Wi-Fi chip loads built-in mwifiex_pcie driver. This driver
uses cfg80211 built-in module. Backported rtl8188eu driver can't use
built-in cfg80211 module, so, to allow using Realtek 8188EU USB device
with Colibri iMX8QXP module, the built-in rtl8188eu driver should be
used.
With this patch the specific depmod config file deploys on the image
for Apalis iMX8QM.
Related-to: ELB-2687
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
With common depmod config file, the backported rtl8188eu driver
tries to load for Realtek 8188EU USB devices. On the other hand,
on-module Wi-Fi chip loads built-in mwifiex_pcie driver. This driver
uses cfg80211 built-in module. Backported rtl8188eu driver can't use
built-in cfg80211 module, so to allow using Realtek 8188EU USB device
with Colibri iMX8QXP module, the built-in rtl8188eu driver should be
used.
With this patch the specific depmod config file deploys on the image
for Colibri iMX8QXP.
Related-to: ELB-2687
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Backports recipe deploys the custom config file for depmod.
Use it in depmodwrapper to generate modules dependencies properly.
Related-to: ELB-2687
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Deploying depmod.conf file makes almost all manipulations
in postinst and postrm scripts useless. Clean up these scripts.
Related-to: ELB-2687
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Only backported drivers should depend on backported common modules.
Deploying the 99-backports.conf file allows depmod to build modules.dep
dependancies file properly.
Related-to: ELB-2687
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
This fixes the following build failure:
++ bitbake console-tdx-image
Parsing recipes...ERROR: ParseError at /workdir/oe/build/../layers/meta-toradex-bsp-common/recipes-connectivity/hostapd/hostapd_2.9.bb:22: Could not inherit file classes/features_check.bbclass
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Update hostapd to version 2.9 to sync with wpa_supplicant 2.9.
Related-to: ELB-2677
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Generic and RT-kernels use diffierent package names.
Add dependancy on virtual name kernel package fixes
build issue for RT-kernels.
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Related-to: ELB-2388
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
backports-5.4 provides latter drivers.
The main issue that fixes with these backports: the earlier mwifiex
drivers for Marvel 8997 WiFi module stucks on firmware crash (ELB-2596).
Related-to: ELB-2388
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
The version 2.9 works more stable with Marvel WiFi solutions.
Related-to: ELB-2388
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
This will generate a hostname based on machine name and serial number.
(E.g. colibri-imx7-031111777)
If serial number is not found it will say "no-serial-number" in host
name.
If machine is not supported hostname will include "unsupported-device"
string.
If /dev/device-tree does not exist it will say "recovery-mode"
as it assumes its in recovery mode of Toradex Easy Installer
To prevent openembedded from creating /etc/hostname file
add hostname_pn-base-files = "" to configration
Related-to: TEI-100, ELB-1322
Signed-off-by: Luka Pivk <luka.pivk@toradex.com>
|
|
These rules make sure that a symlink is created for all i2c and tty
devices. This symlinks are named like on the Toradex carrier boards.
This makes it easy to identify which device in software is matching
the hardware pins.
Additional non-standard devices that are not named clearly on the
carrier board are left out to prevent confusion.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
While at it, add the use-head-next override which builds head instead
of the pinned version. This is useful for integration work.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Make sure u-boot enviroment is erased when installing
new Toradex Easy Installer image
Related-to: TEI-130
Signed-off-by: Luka Pivk <luka.pivk@toradex.com>
|
|
Fix Linux version to really represent 5.4.6.
Update to latest which includes the following two commits:
e87dbbae2576:
ARM: dts: imx7: Fix Toradex Colibri iMX7S 256MB NAND flash support
575bd2d69a82:
arm64: dts: freescale: add initial support for colibri imx8x
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Bump to latest LTS release Linux 5.4.6 plus Apalis T30/TK1 patches.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Bump to latest LTS release Linux 5.4.5.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
(cherry picked from commit 2d635349eff45166feb4340c3008fd2a12f354cf)
|
|
Bump to latest LTS release Linux 5.4.2.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
(cherry picked from commit 6e96e4c828b853edefbc9107680efa38c143c7f6)
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
This patch mainlay aims to refactor bootfs image function, use tar and
xz conversion functions to replace our own create_tezi_bootfs, the
benifit would be we could choose other compression type like Zstandard
easily by setting TEZI_BOOT_SUFFIX and TEZI_ROOT_SUFFIX for bootfs and
rootfs.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|
The blank should be before the value rather than after it, or else we
risk on messing up the values by 'a b' > 'ab'.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
|
|
The bootcmd variable is the entry point for regular boot. If booting
fails for some reason and one saves the environment at this point,
the next boot will no longer use distro boot. Often booting works
since the boot script setup all variables correctly, so one does not
notice that the boot flow has been altered/hard-coded.
Do not reuse bootcmd to avoid accidentally alter the boot flow.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
(cherry picked from commit 98dbc9f5c52616618cbf722965ce2f5dd90409db)
|
|
Use OFFSET_SPL_PAYLOAD to decide if a SPL has to be deployed or not.
This allows a simple integration of machines which have an SPL (as e.g.
verdin-imx8mm has) but do aggregate the SPL and U-Boot proper into one
binary.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
The list of deployed U-Boot artefacts is set in python for the 'distro'
tezi-image, but in the non 'distro' case directly in the tar command.
Unify that to put the list together in python.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
The problem was within connman that constantly disables RF. So this
commit is not needed.
This reverts commit a64ff768b7d5d24360a1ac9bec67409f0daa931d.
|
|
systemd-rfkill disables by default our RF devices. We do not want them
to be disabled at all so remove that rfkill from systemd.
Signed-off-by: Philippe Schenker <philippe.schenker@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>
|
|
If DISTRO_FLAVOUR is not set, then the string '${DISTRO_FLAVOUR}' is
appended.
Fix this by providing a weak default.
Fixes commit 3d072f3077b6.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
So that one sees in the Toradex Easy Installer which image is which.
Signed-off-by: Max Krummenacher <max.krummenacher@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.
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>
|
|
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>
|
