lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 265 seconds]
<Armbian-Discord> <T​onymac32> Don't do it
<Armbian-Discord> <T​onymac32> Not worth it
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 265 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 265 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 260 seconds]
<Armbian-Discord> <a​mazingfate> There are many rk3588/rk3588s sbcs now. How shall we support them? Sharing the u-boot and kernel with radxa rock5b or each board has its own u-boot/kernel source?
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
<Armbian-Discord> <r​pardini> Yeah. It's not worth it, for a board sans-UART and sans-PCIe. If someone were to do it... I'd start by looking and comparing Khadas' kernel (which I suppose is https://github.com/khadas/linux/commits/khadas-edge2-android12) vs the Radxa one. I might embark on such a foolish thing if Khadas can solve my non-solder-to-pogo-pads problem...