Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump mvdan/sh from 3.9.0 to 3.10.0 in lib/tools/shellfmt.sh #2

Conversation

github-actions[bot]
Copy link

Bump mvdan/sh from 3.9.0 to 3.10.0 by bumping SHELLFMT_VERSION in lib/tools/shellfmt.sh.

Release notes

Sourced from mvdan/sh's releases.
Please note that this only shows the release notes for the latest release.

Consider becoming a sponsor if you benefit from the work that went into this release!

Binaries built on go version go1.23.2 linux/amd64 with:

CGO_ENABLED=0 go build -trimpath -ldflags="-w -s -X=main.version=v3.10.0"

MichaIng and others added 7 commits October 12, 2024 17:52
All credits go to @gitmeister: MichaIng/DietPi#5414 (comment)

Signed-off-by: MichaIng <micha@dietpi.com>
Signed-off-by: MichaIng <micha@dietpi.com>
Upstream kernel defines the exact same LEDs already. having both defined leads to unusable LED sysfs nodes: MichaIng/DietPi#5401

Signed-off-by: MichaIng <micha@dietpi.com>
In case of rk35xx-vendor, the mt7921e PCIe WiFi drivers were enabled already,
but the one for USB was missing. It was enabled for most other boards already,
hence this commit is an alignment.

Signed-off-by: MichaIng <micha@dietpi.com>
since it sometimes results in a boot loop, when aiming to boot from eMMC or SD card: MichaIng/DietPi#7168, https://forum.armbian.com/topic/36141-usb-errors/

The attempt to boot from USB might be too fast, when trying it first, where some USB drives are not ready yet, resulting in an error.

Signed-off-by: MichaIng <micha@dietpi.com>
Linux prior to v6.11 did not contain a native Orange Pi 3B device tree, hence "rk3566-orangepi-3b.dtb" was added via patch. Since there is an incompatibility between board revisions v1.1 and v2.1, mainline Linux however added two device trees for those two revisions. Since mainline U-Boot did already select those new device trees by default, we needed to define the old one via boot environmetn, which does not exist in new kernel. Older U-Boot versions however won't load the new device trees.

To not break boot after kernel package upgrade, a symlink is hence added to the package to keep it compatible with old U-Boot and boot environment. A migration to new U-Boot, removing the then obsolete fdtfile declaration from boot env, can be done via distro upgrade scripts or manually, to fully support board revision v2.1.

Signed-off-by: MichaIng <micha@dietpi.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant