Karel Koci authored 3 years ago and Simon Borek committed 2 years ago

The syntax used in the Bash scripts here requires at minimum Bash 5.0.
This checks for it and reports reasonable error message instead of
failure.

There are two discovered issues with older versions of bash.

The first issue is the change of empty array expansion in Bash 4.4
resulted in empty arrays not being considered as undefined anymore. We
depended on this heavily and thus we can't easily go bellow that
version.

The second issue is that syntax `[[ -v "foo[key]" ]` works only in Bash
5.0 and newer. This checks if specific key is in the associative array.
The replacement could be `[ "${foo[key]:+_}" ]` in some cases but this
only works if value is also nonempty. Thus it makes sense to just the
more clear and reliable syntax and such depend on Bash 5.0.

Simon Borek authored 3 years ago and Josef Schlehofer committed 3 years ago

add important missing changes, update kernel version to current value

This was my fault, I think I copy&pasted this from older changelog and
did not bump the OpenWrt version.

Fixes:
a09c13dd ("NEWS: 5.3.6: Mention new
version of OpenWrt")

Reference:
https://github.com/openwrt/openwrt/commit/57293f51c48f1f7c4e8f1ab6fe2220761487bd65

Fixes: 28d86cbe ("patches/openwrt:
Turris 1.x support patch: compile DRTC DS1307 in kernel")

While at it, I included patch to compile USB storage support into
support patch

Pali Rohár authored 3 years ago and Josef Schlehofer committed 3 years ago

Reference: https://elixir.bootlin.com/linux/v4.14.262/source/drivers/rtc/rtc-ds1307.c#L309

Fixes: #208

Drop mention regarding Happy New Year. It does no longer makes
any sense to wish it on 18th January.

Karel Koci authored 3 years ago and Josef Schlehofer committed 3 years ago

The OpenWrt uses revision as part of base-files and that works for them
but not for us. Our version is declared by turris-build repository and
applied as a patch. We also have patch that changes revision detection
to latest OpenWrt commit (ignoring our patches). That is done to not
reinstall base-files with pretty much every rebuild as hashes for
patches change with any change in OpenWrt. Thus it is easy for us to
have same version of base-files where the content of it is different.
The most problematic is /etc/os-release file.

The switch from revision to full version code causes reinstall of
package when we change our Turris OS version not just when OpenWrt
revision changes.

Recently linux-stable 4.14 landed MOX' PCIe controller fixes, and one of
them changed the polarity of how GPIO reset is issued, compared to our
previous (non-upstream) patches.

Fix the device-tree so that GPIO reset is issued in correct polarity.

As we didn't make this release last year, it does not make any sense to
wish Merry Christmas anymore. :-)

There was updated zsh and domoticz. The domoticz was requested on our
forum as it didnt work out with the Python 3.7. Both of them are
included or pending to by accepted in upstream

It requires rebase, because there was added a new kernel config option
- UNWINDER_FRAME_POINTER

It seems that with recent changes in LTS kernel 4.14, this is no longer
necessary as it is done differently.

This patch is now included in kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/Documentation/devicetree/bindings/pinctrl/marvell,armada-37xx-pinctrl.txt?h=v4.14.258&id=15d3bc71e322c9591e65ae555de40669fe957f8a

This patch was removed in OpenWrt 19.07 branch (commit:
1d94f72439034c112bfa4b694fc736123f4890a5).

Reason: It was superseded by this commit [1] in kernel.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=62a3dc9b65a2b24800fc4267b8cf590fad135034