Some K3 boards use a split initial boot stage requiring an extra file
called "sysfw.itb". If defined in the board configuration deploy this
file if available.
- restore the victims as well
```
CONFIG_INPUT_RK805_PWRKEY=y
CONFIG_PINCTRL_RK805=y
CONFIG_CHARGER_RK817=m
CONFIG_REGULATOR_RK808=y
CONFIG_SND_SOC_RK817=m
CONFIG_RTC_DRV_RK808=y
CONFIG_COMMON_CLK_RK808=y
```
A change to ledtrig_netdev causes the boot to fail on Orangepi-r1plus-lts and possibly other boards. The board boots and LED netdev trigger works if service is modified to use After=timers.target.
Also added some cleanup fixes to silence some of the compiler warnings,
fixes for issues during inserting and removing xradio module and fixes
for possible data corruption on vmmaped stack.
All of these fixes were taken from https://github.com/fifteenhex/xradio
The causes the first-stage bootloader to be generated before the normal
U-Boot allowing the later build to use the firmware fetched during the
first-stage build.
* patch: misc: rtw88: wireless-next: 2023-08-25
Updated: 6.1 / 6.4
Added: 6.5
For doc sake, this update makes 6.1 slightly differrent than 6.4 and
6.5 in one particular area of main.c.
As shown here:
7746e2fa87
6.1 requires we use del_timer_sync, where the above releases use
timer_delete_sync.
Tested-on: ODROID-C4 X96-AIR BPI-CM4 (linux 6.x.y)
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
* driver_rtw88: `linux-version compare "${version}" ge 6.1`
Suggested-by: @viraniac
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
---------
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
Co-authored-by: Patrick Yavitz <pyavitz@xxxxx.com>
- bsp-cli: `postinst` is now generated _after_ the hooks are run
- hooks are allowed to append to `postinst_functions` array
- hooks are _not_ allowed to modify `DEBIAN/postinst` directly anymore (it won't even be there)
- rewrite the postinst stuff in `helios4`'s `family_tweaks_bsp()` to use new way
- introduce `add_file_from_stdin_to_bsp_destination()`, a helper for easy heredoc-based adding of files to bsp-cli
- First and only argument is the destination path, relative to the root of the package -- do NOT include $destination -- it is already included.
- Containing directory, if any, is created automatically (no more "mkdir -p x; cp y x/z")
- The full path (including $destination) is set in $file_added_to_bsp_destination, declare in outer scope to get it if needed.
- deprecated in `bullseye`: _This package is for legacy applications and no longer used by GNOME._
- https://packages.debian.org/bullseye/gconf2
- removed in `trixie` and `sid`
- `bullseye` is the father of all symlinks, so yeah, call me lazy
