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
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC>
<liwei19920307> 大家好
<DC-IRC>
<Tonymac32> with patching all things are possible. The HDMI support and VOP2 are not merged yet
<DC-IRC>
<liwei19920307> Hello everyone, I tried to adapt a 3566 development board HA Green to armbian NPU but I ran into some problems, first of all, it seems that only the 5.1 kernel supports NPU at the moment, so I tried to add the following in the 5.1 kernel armbian &bus_npu {
<DC-IRC>
<Tonymac32> so the reality is, unless an individual wants a ton of extra work chasing the mainline patchsets for every RC, we should not have this working yet, it's just more dev time we'll complain about later when someone asks an innocent question.
<DC-IRC>
<Tonymac32> should be 5.10, the vendor kernel
<DC-IRC>
<liwei19920307> Able to compile successfully, but got stuck in kernel boot after booting
<DC-IRC>
<liwei19920307> And there are no logs to troubleshoot the problem
<DC-IRC>
<liwei19920307> I've set the log level to debug
<DC-IRC>
<Tonymac32> a little earlier in that UART boot log might be useful, did it actually load the fdt?
<DC-IRC>
<liwei19920307> If I remove the NPU configuration from the DTS, it boots normally
<DC-IRC>
<Tonymac32> yeah just trying to make sure there wasn't some sort of quiet failure and you don't actually have a device tree in the images you included the nodes in
<DC-IRC>
<Tonymac32> because unfortunately, the Rockchip vender kernel is a cursed piece of hackery, and I can't even begin to theorize what's going on in that thing
<DC-IRC>
<liwei19920307> I tried to remove a lot of references to troubleshoot the error, but it didn't seem to work, as long as the device tree with the npu was added, it wouldn't start
<DC-IRC>
<liwei19920307> Thank you, @mackahan, I'll try it again, and I'll come back if there's any progress
<DC-IRC>
<amazingfate> You can try `verbosity=7` in armbianEnv.txt and make sure you have tty output in serial console. Kernel should have some error outputs.
<DC-IRC>
<liwei19920307> I've set the log level to verbosity=8 but there aren't any logs, so I'd like to ask if anyone has encountered it as well
<DC-IRC>
<liwei19920307> 😂 I've been trying for days and still haven't found the problem
<DC-IRC>
<viraniac> try adding extraargs=debug and earlycon=on as well
<DC-IRC>
<Tonymac32> But I admit I haven't been watching that closely 🤷♂️
<DC-IRC>
<shivansps> but hdmi works on joshua images and as far as i know it is just the regular kernel, people reported building armbian with 6.7rc1 and working too
<DC-IRC>
<shivansps> but hdmi works on joshua mainline images and as far as i know it is just the regular kernel, people reported building armbian with 6.7rc1 and working too
<DC-IRC>
<efectn> Yes i tested it on opi5+ with trash tft monitor, as well
<DC-IRC>
<efectn> Joshua also apply some patches over mainline kernel
<DC-IRC>
<efectn> Joshua also applies some patches over mainline kernel
<DC-IRC>
<tenkawa42> As the saying goes... all RK3588 != same
<DC-IRC>
<tenkawa42> don't equate the OPI5+ for all RK3588s
<DC-IRC>
<tenkawa42> don't equate the OPI5+ for all RK3588
<DC-IRC>
<efectn> I didn't add patches for panthor because i don't want to mess
<DC-IRC>
<efectn> For sure
<DC-IRC>
<Tonymac32> well right, you'ge got each devices DTS to deal with
<DC-IRC>
<Tonymac32> I should work through the T6 again and prep for the HDMI stuff getting merged, since that's my best RK3588 by a massive margin and it would be a shame to let it go to waste
<DC-IRC>
<Tonymac32> we need a vendor that actually cares about mainline to adopt an RK3588, but I suspect that won't happen until after the support actually exists 😄