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
<Armbian-Discord> <j​oekhoobyar> Can confirm Rock PI 4 Model SE works using the Model B build - just as Radxa's DL links seemed to suggest. Even the PCIE Gen2 overlay works as expected. Updated the Rock PI 4 Downloads page description to have updated links now.
<Armbian-Discord> <j​oekhoobyar> Honestly, thought, I'll bet we could improve on the state of things as left by Radxa. We still get messages like this that are signs of dirtyness in the DTB: [ 7.798979] rockchip-pinctrl pinctrl: pin gpio4-0 already requested by ff880000.i2s; cannot claim for 1-0011 [ 7.799003] rockchip-pinctrl pinctrl: pin-128 (1-0011) status -22 [ 7.799012] rockchip-pinctrl pinctrl: could not request pin
<Armbian-Discord> 128 (gpio4-0) from group i2s-8ch-mclk on device rockchip-pinctrl [ 7.799020] es8316 1-0011: Error applying setting, reverse things back I don't have a Model B, so I can't say if messages like this are specific to the Model SE or not.
<Armbian-Discord> <j​oekhoobyar> I gotta say though, it's nice to have an NVME drive on a tiny SBC.
<Armbian-Discord> <m​arcone> what does cat /sys/firmware/devicetree/base/model say on the 4 SE?
<Armbian-Discord> <j​oekhoobyar> from which build? The Armbian one?
<Armbian-Discord> <j​oekhoobyar> # cat /sys/firmware/devicetree/base/model ; echo Radxa ROCK Pi 4B
<Armbian-Discord> <j​oekhoobyar> doesn't that just come from the DTB?
<Armbian-Discord> <j​oekhoobyar> Let me boot it again from the Radxa DL, but I expect the same
<Armbian-Discord> <m​arcone> yes. Interesting that they're just using the 4B dtb, when the 4 SE has a different SoC than the 4B.
<Armbian-Discord> <j​oekhoobyar> It is odd, I imagine it is laziness on their part - see an example of a sign of a dirty DTB above.
<Armbian-Discord> <m​arcone> especially given https://github.com/radxa/kernel/commit/8018b82e9954e3c7cc637eb7102d81930901ba91 where they're using a separate dtsi for the rk3399t
<Armbian-Discord> <j​oekhoobyar> lol - not a great sign
<Armbian-Discord> <j​oekhoobyar> yeah, I haven't moved Armbian's build to the T variant yet - I wanted this working before fiddling. We didn't have the T variant in the patches - but I think it might be good to take a stab at it.
<Armbian-Discord> <j​oekhoobyar> not having a baseline example from the vendor isn't good either - in the case of the SE
<Armbian-Discord> <j​oekhoobyar> still I'm happy it works, even with the PCIE-2.0 overlay
Armbian-Discord has quit [*.net *.split]