In reference to the master branch:
d1388f36 ("treewide U-boot: enable
parallel building")

- Replaced make by using MAKE variable
- Added PKG_JOBS, but as stated in OpenWrt include/package.mk, there
  needs to be set PKG_BUILD_PARALLEL

- It is disabled for Turris 1.x as there are two defconfigs and it might
  lead to some issues

The total size of a53-firmware partition is 1441792 bytes (0x160000).
The first 0x160000 bytes is BL1 and what remains is FIT.

On the absolute position 131184 (131072 + 112), there is offset, where
begins U-boot and on the position 131192 (131072 + 120), there you can
find the total size of U-boot.
(= Total size of partition - size BL1 - offset U-boot)

Reported-by: Pali Rohár <pali@kernel.org>
Co-authored-by: Pali Rohár <pali@kernel.org>

This version fixes path for mox_do_sign or in newer kernel versions as
do_sign, where it is now located in debugfs.

This is no longer necessary as all packages in Turris OS packages are
using Python3. This was dropped in OpenWrt packages repository in 21.02
version. [1]

Reference:
[1] https://github.com/openwrt/packages/commit/2210c4a60dd8fb6420f7bd3c6fe00ed0ae4c51be

Based on mox-a53-firmware package from e6c48f7e

Changelog:
- https://gitlab.nic.cz/turris/mox-boot-builder/-/releases/v2022.06.11

sha256sum for secure-firmware and secure-firmware-devel is the same:
db3c1df34d755911948c8c057d7a00862a3d68aeb1bd3b3270717f1881531199  secure-firmware.bin
db3c1df34d755911948c8c057d7a00862a3d68aeb1bd3b3270717f1881531199  secure-firmware-devel.bin

This fixes:
Makefile:1452: *** 'BL33=/foo/build/staging_dir/target-aarch64_cortex-a53_musl/root-mvebu/usr/share/mox/u-boot.bin' was specified, but '/foo/build/staging_dir/target-aarch64_cortex-a53_musl/root-mvebu/usr/share/mox/u-boot.bin' does not exist.  Stop.

replaced by mox-a53-firmware in 72919fc3

uboot is now built directly from upstream, the package name is
mox-uboot-uboot and it's build only, so users can not install this
package. It's used to build a new package called mox-a53-firmware that
combines uboot with trusted firmware and provides the uboot-devel binary
like uboot-mox used to.

Josef Schlehofer authored 2 years ago and Michal Vasilek committed 2 years ago

This helps in cases when someone forgets to bump PKG_RELEASE.

Reference:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=9ae3c6f94c616cfbf854d3ec749c7fafc9893942

It was changed that the MOX is now the same as Turris Omnia

This file, which I removed is no longer used as it was superseded by
the package mox-dtb. It does not require to bump package.

Fixes: 26fba930 ("nor-update: Generalize
to work for all devices")

Michal Hrusecky authored 3 years ago and Karel Koci committed 3 years ago

Should make no real difference, just code tiny bit looks nicer.

Michal Hrusecky authored 3 years ago and Karel Koci committed 3 years ago

Although the idea is great, it is currently not supported in reForis and
would cause more troubles, so let's drop it for now.

Michal Hrusecky authored 3 years ago and Karel Koci committed 3 years ago

SFP interface is now called SFP, no longer eth1. Switch to DHCP client
only if we have no WAN port - only one module device. If we have a switch,
set WAN as bridge between SFP and eth0.

We don't longer need to ship SDIO firmware in mox-support package as
this firmware is already present in package mwifiex-sdio-firmware [1],
which is located in linux-firmware's Makefile.

Package mwifiex-sdio-firmware is pulled by lists/base/min.lua.m4 and
lists/kmod-mox.list from turris-build repsitory.

[1] ed381e2fb2bde3e45295dff46f5fd8ca2e2c51b9 ("linux-firmware: add support for Marvell SDIO 8997")

Nor-update is provided by package turris-nor-update, which installs
nor-update into /usr/sbin

The new URL to our gitlab is now https://gitlab.nic.cz.
Our turris-build repository was moved to turris/os/build.

Add nor-update as dependency since we split it to generic package and
shield-support depends on it as we need to have nor that respects
contracts.

sha256 for firmware file:
- b423a8580ca62adf5b6ae7d10caa2c4b10aaaa7101acd58cf7b874cdacb6f541 secure-firmware-devel.bin

Michal Hrusecky authored 3 years ago and Karel Koci committed 3 years ago

This should contain the workaround for MOX reboot issue.

Michal Hrusecky authored 3 years ago and Karel Koci committed 3 years ago

It is version two of workaround to solve reboot issue on some MOX
devices.

https://gitlab.nic.cz/turris/mox-boot-builder/-/releases/v2021.01.22

Fixes:
Makefile:93: WARNING: skipping mox-generic-support -- package has no install section
inconsistent: Package mox-support requires package mox-generic-support that is not available.

We are shipping different reset_button function in Turris Shield and
Turris MOX. We can not have it in one generic file as it leads to this
issue:

/etc/hotplug.d/button/mox_reset: mox-support (existing-file), mox-generic-support (new-file)

So, ship reset_button in specific support packages instead of generic
one.

Fixes: 26fba930 ("nor-update: Generalize
to work for all devices")

Josef Schlehofer authored 4 years ago and Josef Schlehofer committed 4 years ago

In this commit, I added PKG_MIRROR_HASH for all of our packages.
This variable includes SHA256 checksum of the tarball which was
generated while checkout of the source repository.

I need to have before I can add CI.

We received a new SDIO firmware from NXP. The difference that it should
fix dropping connection to Wi-Fi if there is running iperf.

Checksum SHA256 of binary:
1f725e4f92bff871d031f625d58a4feeb390703f75d5190e2934ebe717d6a265

In generic package there was missing /etc directory.

Michal Hrusecky authored 4 years ago and Karel Koci committed 4 years ago

Long press does factory reset as well as the default reset mode
triggered during boot.

This was clearly invalidly placed in Mox directory as this package is
used by all.

This just renames packages to be consistent with other hardware specific
packages.

Package itself is named as Kernel but build system that resolves build
dependencies uses not package name but directory name where Makefile is
stored. It is stupid and inconsistent but that is how it works. Kernel
is stored in directory called linux so it should be linux and not
kernel.

Package itself is named as Kernel but build system that resolves build
dependencies uses not package name but directory name where Makefile is
stored. It is stupid and inconsistent but that is how it works. Kernel
is stored in directory called linux so it should be linux and not
kernel.

These two firmware files were added in this commit 73a39987 ("mox-support: Update WiFi firmware")
without any description. Also, they are not used. I removed it from the
router and it works.

By default, mwifiex and btmrvl are looking for mrvl/sd8997_uapsta.bin
which is wrong as it should look for mrvl/sdsd8997_combo_v4.bin
And because of that, there is a symlink. Pali Rohár sent two fixes to
mailine kernel [1] [2], which fixes it, but it was backported to stable
versions of kernel 5.8, 5.7 and 5.4

[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2e1fcac52a9ea
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=00eb0cb36fad5

In the future, this is going to be superseded by
https://lists.openwrt.org/pipermail/openwrt-devel/2020-August/030946.html

Because those separate firmware files are for separate Wi-Fi and BT
functionality. But this is not supported by kernel drivers.
Kernel drivers are using combo firmware, which initializes both Wi-Fi and
BT functionality.