00:22 <naoki> does anyone have rk3568 based board with 4GB or more RAM? my board has only 2GB but it needs a patch for mainline u-boot to boot

00:22 <naoki> https://github.com/RadxaNaoki/u-boot/commit/d78b9b1af280da3b1927e7d103dea2d5096df1ad

00:23 <naoki> it's a part of https://patchwork.ozlabs.org/project/uboot/patch/20220222013131.3114990-12-pgwipeout@gmail.com/

15:51 <wens> getting " Unable to handle kernel execute from non-executable memory at virtual address ffffff800123c728" on v6.0 on my roc-rk3399-pc

15:51 <wens> LR = call_timer_fn.constprop.0+0x24/0x80

15:56 <wens> looks like the fix is https://lore.kernel.org/lkml/20220902184543.1234835-1-pgwipeout@gmail.com/

15:59 <wens> which was applied for -next :(

16:20 <robmur01> wens: yeah, it shows up as all manner of weird nonsensical symptoms, and affects stable as well. I'm booting my NanoPC-T4 with "initcall_blacklist=rochckip_usb2phy_driver_init" for now :(

16:32 <wens> +1 to the regression tracking complaints raised at plumbers :(

16:35 <macromorgan> psydroid: I just hope they're working on releasing A-TF sources for the rk356x series :-)

16:35 <CounterPillow> I don't think they are. Asked them at the start of august, they said they'll look into it at the end of august, it's now october

16:39 <psydroid> macromorgan, that's fine as a short-term goal, but I want to relegate all my x86 hardware to relatively simple duties over the next few years :)

16:40 <psydroid> and for that more performant ARM and RISC-V chips would be very useful

16:41 <macromorgan> well that's going to severely limit things, especially when their more recent binary A-TFs don't work with mainline U-Boot anymore

16:44 <psydroid> I don't know what's the holdup here

16:44 <psydroid> they could just throw the code over the fence

16:44 <psydroid> and developers would take care of properly integrating it into mainline