- Replace creation of `armbian-config.list` with
`armbian-config.sources`. This holds the same information in a newer
format, deb822. This does not affect `armbian.list`.
See also: https://github.com/armbian/configng/pull/407
Overlay for testing purposes:
There is a strange interaction between that ethernet adapter and the rtc
(it runs better -but still not well- with the ethernet adapter enabled).
Contains rewritten dts, based on decompiled dtb from original Klipad50
(as similiar as possible to original).
Kernel defconfig taken from MKSPI (replaced "mkspi" with "mksklipad50")
While syncing with upstream Linux helios64 dts for 6.9 I missed
the diff for the helios64 status led label (upstream was
helios64:green:status instead of Armbian helios64::status) and
thus broke armbian helios64-heartbeat-led.service.
This commit restores the Armbian label helios64::status to let
helios64-heartbeat-led.service starts.
Fixes: cbaf67f00 ("Sync helios64 to its updated 6.9 dts")
Signed-off-by: Alban Browaeys <alban.browaeys@gmail.com>
- this allows us to drop a bunch of code needed for 2025.01
- UMS works out of the box (simple dr_mode = peripheral change enough)
- USB3 Type-A port works out of the box
- SPI works out of the box
This makes:
W: Possible missing firmware /lib/firmware/regulatory.db for built-in driver cfg80211
W: Possible missing firmware /lib/firmware/regulatory.db.p7s for built-in driver cfg80211
go away.
Since v5.11, Linux upstream commit 8b5c2b45b8f0 disabled the internal pull-down
for the strobe line explicitly instead of leaving it in its default
state (the opposite of Rockchip Kernel which force enable this intrnal
pulldown by default) thus causing I/O errors in HS400 mode for various
eMMC modules (the ones that did not have an external pulldown on the
strobe line likely).
Discussed upstream and the choice has been made to keep this
behavior as it has been there for too long and reverting might break
other boards http://lists.infradead.org/pipermail/linux-rockchip/2024-April/046416.html
HS400 for helios64 was disabled in commit 5f2e23e90
"Disabled hs400 on Helios64 (hopefully only temporarily) (#3126)"
but for 5.10.63 (ie before the above commit disabled internal pulldown).
Back then I had bisected the emmc I/O issue to a double init of the emmc
regulator introduced while adding deferred support to the regulator driver
core, ie commit 06653ebc0ad2 "regulator: core: resolve supply for boot-on/always-on regulators"
in 5.10.60. But due to the new default for the strobe line internal pulldown
introduced in 5.11, when this double voltage regulator init issue was fixed likely by
8a866d527ac0 "regulator: core: Resolve supply name earlier to prevent double-init"
in Linux 6.1.
* add nanopi-r3s.csc board config
* Nanopi R3S - add uboot patch
* Nanopi R3S - add dts
* fix bogus patch header
* Migrate to new patch series
Source & credits https://patchwork.ozlabs.org/project/uboot/list/?series=438193
I still need to figure out how to convert a patch series from patchwork in a way so the build framework doesn't complain about headers and magic and whatever. So a few hundreds of header lines have been replaced with something generic.
Applies and builds fine now against current stable v2024.10
* Create board-nanopi-r3s-fix-leds.patch
Thx https://github.com/armbian/build/pull/7556#issuecomment-2615110100
* Rename board-nanopi-r3s-fix-leds.patch to xx-board-nanopi-r3s-fix-leds.patch
* add new patch
- post_family_tweaks_bsp_ is called during the build of armbian-bsp-cli-xxx
- the cli package is built separately on the build server
- comparisons to build parameters such as DESKTOP_ENVIRONMENT do not work
Signed-off-by: Martin Schmiedel <Martin.Schmiedel@tq-group.com>
Now that upstream U-Boot has support for building K3 boot artifacts
we can drop using the ti-u-boot fork. Switch to v2025.01 and
adjust file names and add new dependencies as needed.
Option "--connect-timeout" used to determine external IP covers only
connection phase. Curl may "hans" in a different phase and this makes
login to the system impossible if MOTD "header" module enabled.
Using "--max-time" is more reliable and prevents hanging for hours.
Fixes issue https://github.com/armbian/build/issues/7753
Signed-off-by: Uladzimir Bely <wiselord1983@gmail.com>
