Hi, just noticed that rockchip kernels in apt repos lag wrt to those advertised on board pages. For example if you are on rockpro64 the web page https://armbian.com/boards/rockpro64 will tell you that the current kernel for this board is 6.18.26. However, the apt repos will give you 6.18.10 as the most recent current kernel. This seems particularly problematic today, with the serious copy-fail vulnerability that, to the best of my understanding, also affects ARM. Specifically, the board pages will give you the impression that you are on a kernel new enough to have the vulnerability patched, while in fact updating the system will not give you that kernel, but a vulnerable one. All boards with the rockchip64 kernel seem to be affected.

According to the circuit diagram, the reset button is connected to the hardware reset lines, so nothing can prevent forcing the reset state.

Looks like the current-rockchip64 kernel that one receives with apt on PINE64 rockpro64 is 3.18.10 (6.18.10-current-rockchip64), vulnerable to copy-fail. This seems weird because if you go to https://armbian.com/boards/rockpro64 that page says that the "current" kernel for these systems is 6.18.26 and that is what you get when you download the image file. Is there an issue with updating the apt repos?

Looks like the current-rockchip64 kernel that one receives with apt on rk3318/28 is 3.18.10, vulnerable to copy-fail. This seems weird because if you go to https://armbian.com/boards/rk3318-box, that page says that the "current" kernel for these systems is 6.18.26 and that is what you get when you download the image file.

Things are still very sad with Ethernet. Is this could be related to some low-level timings in device configuration?