This is tested on a tinkerboard 2s.
The u-boot dts for tb2 contains other fixes, and the major ones are:
- add missing basic gpio-fan node
- usb-c altmode fix, dts part
- similar to e9708b8c33, but for the Blade3
- this reverts d048673c00 just for the Blade3
- there is little to be gained from .10 anyway on those machines (IMHO)
- it is still vendor 2017.09 after all, dunno why Radxa calls them "2024.x"
- UMS mode (use the black USB port)
- Boot order: SD -> NVMe -> SATA -> USB -> eMMC
- Flash LEDs in preboot
- Networking stuff
- Lots of FS's and compression methods
* helios4: fix wake-on-lan (wol)
- added ethtool package
- enable wol on all ethernet interfaces
- support common systemd.net-naming-schemes (ethX/endX/enoX)
* Update helios4-wol.service
Removed test code.
* Update helios4-wol.service
Fix bug after retesting.
From the Kconfig:
```
Preload default EDID (Extended Display Identification Data)
branded by Linux Foundation that exposes display modes up
to 4k@30Hz, which have best compatibility with HDMI transmitters.
Enabling this option is recommended for a non-production use-cases.
It will make driver usable out-of-the-box.
For a higher display modes you will need to load customized EDID
from userspace using v4l2-ctl tool or by other means.
Without enabling this option driver will be practically
non-functional until EDID will be loaded from userspace.
Which is a wanted behavior when using this driver in a
commercial product that should utilize own branded EDID.
```
On v2025.01 and v2025.04 I get the following error
starting USB...
Bus usb@ff500000: dwc3_meson_gxl_get_phys: usb2 ports: 1
probe failed, error -114
No USB controllers found
So revert back to v2024.10 until sorted.
Signed-off-by: Patrick Yavitz <pyavitz@gmail.com>
ATF is currently built in Debug mode for K3 family of devices. This is
due to the fact that K3 Armbian images have been experimental so far.
However, there is work underway to make Armbian a production-capable
environment. Therefore, drop the DEBUG=1 flag from the ATF build
command.
Signed-off-by: Suhaas Joshi <s-joshi@ti.com>
Presently, in k3 devices, we are setting TEE=bl31.bin. However TEE
should be set to OPTEE, not ATF.
Therefore, do the following:
* clone and compile OPTEE
* add variables for OPTEE platform and `make` arguments in all k3
board configs
* use the compiled binary as TEE to compile U-Boot
Signed-off-by: Suhaas Joshi <s-joshi@ti.com>
Currently `current` picks 6.6.y kernel baseline, and `edge` picks
upstream's 6.12.y tree.
Make `current` pick the current SDK release (which, at the moment, is at
11.00.09 baseline), and make `edge` pick the latest un-released RC's
from TI's tree.
`current` is what most people will use, therefore it should be the same
as our official and tested release. `edge` can be either cutting-edge
(latest RC) or bleeding-edge (latest commit on cicd branch). For now,
keep it cutting-edge.
Signed-off-by: Suhaas Joshi <s-joshi@ti.com>
- Added FDT resize/trim to allow big DT and overlays and still use
configured load addresses in case `setexpr` not available
- Moved FDT resize and next load address alignment
- Added filename information to load instructions
- Moved all "global" variable determinations to the top of the
bootscript
https://github.com/armbian/build/issues/8178
- Add switch to turn avoidance on/off
- Increment base address before alignment to resolve the oboe
- oboe observed in U-Boot v2021.04 and in particular with DT loading
