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> [Discord] <tyro_noob> I'm trying to enable SPI but it just has a blank selection box in armbian-config.
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC> [Discord] <lanefu> What files are in /boot/dtb
<DC-IRC> [Discord] <lanefu> And configuration is in /boot/armbianEnv.txt
<DC-IRC> [Discord] <lanefu> paste.armbian.com is your friend
<DC-IRC> [Discord] <lanefu> Also you didn't say what board or kernel you were using
<DC-IRC> [Discord] <Tonymac32> we need to pipe in an AI bot that uses individual message context to post the "what are you talking about" boilerplate if someone has asked for something with no background information
<DC-IRC> [Discord] <lanefu> We used to just yell `armbianmonitor -m`
<DC-IRC> [Discord] <tyro_noob> 3b 5.10
<DC-IRC> [Discord] <Tonymac32> especially if that's a vendor kernel, that familay has been all over the place
<DC-IRC> [Discord] <amazingfate> rk 6.1 kernel tag uploaded: https://github.com/armbian/linux-rockchip/tree/linux-6.1-stan-rkr1
<DC-IRC> [Discord] <spooky8086> sweet, id send a pull request to make a rk-6.1-rkr1 branch, but i do not think i have permissions. But id sync my rk-6.1-rkr1 branch, it has most patches from 5.10 rebased. The only patches i had to drop where LCD related and for the edge 2. https://github.com/Joshua-Riek/linux-rockchip/commits/rk-6.1-rkr1/
<DC-IRC> [Discord] <Werner> No permission? Odd. I always thought everyone can do PRs... @igorpec got an idea?
<DC-IRC> [Discord] <spooky8086> I can send a pr, though I do not think I can make a new branch
<DC-IRC> [Discord] <spooky8086> I could be missing something
<Werner> I don't know for sure tbh but Igor should :)
<DC-IRC> [Discord] <amazingfate> Let me create a new branch based on the tag.
<DC-IRC> [Discord] <amazingfate> @spooky8086 branch created: https://github.com/armbian/linux-rockchip/tree/rk-6.1-rkr1
<DC-IRC> [Discord] <rpardini> Hmm. Is there any chance we can keep the 5.10 as an "oldlegacy" or such, at least for a few months?
<DC-IRC> [Discord] <rpardini> I think great news about 6.1, but it took us long to estabilize 5.10, shouldn't we capitalize on it a bit more.?
<DC-IRC> [Discord] <liwei19920307> 6.1 kernel is really good news. I spent a lot of time adapting the 5.10 kernel armbian to HA Green, NPU, VPU and GPU all work normally. 5.10 kernel is old, but it is still a little useful.
<DC-IRC> [Discord] <Werner> Maybe attach 6.1 to _current_ temporary? Atm I think there is only legacy and edge?
<DC-IRC> [Discord] <efectn> I agree. I've not yet found a chance to try 6.1 but there are always potantial issues
<DC-IRC> [Discord] <efectn> It might be confusing. We use current from linux git not downstream kernels
<DC-IRC> [Discord] <rpardini> Might be nice if we
<DC-IRC> [Discord] <rpardini> - keep 5.10 as `legacy` for time being
<DC-IRC> [Discord] <rpardini> - add 6.1 (when its ready) as `vendor` or such
<DC-IRC> [Discord] <rpardini> - consolidate rk35xx + rockchip-rk3588 family into one, there's a bit of confusion still
<DC-IRC> [Discord] <efectn> I think the main difference between rk35xx and rockchip-rk3588, they use different edge linux kernels
<DC-IRC> [Discord] <efectn> Maybe we can merge both in 6.9 or 6.10
<DC-IRC> [Discord] <rpardini> oh -- I didn't know that... thought they were same except 2 different names
<DC-IRC> [Discord] <mecoblock> 5.10 as legacy and 6.1 as vendor makes sense to me too.
<DC-IRC> [Discord] <amazingfate> What about rk35xx-current? rk35xx is a legacy only family now.
<DC-IRC> [Discord] <rpardini> Hmm -- then I'm more confused, Efe mentioned there's different edge kernels?
<DC-IRC> [Discord] <efectn> rk35xx uses rockchip64 for edge
<DC-IRC> [Discord] <efectn> Are there any reason why rockchip64 and rk35xx not get merged?
<DC-IRC> [Discord] <efectn> I suppose there are no legacy kernel for rockchip64
<DC-IRC> [Discord] <rpardini> Yeah this is deeply twisted. I don't think there's much logic, we've just been dancing the dance as the tune played
<DC-IRC> [Discord] <rpardini> rockchip64 had ayufan 4.x (sic?) for legacy but we've dropped it completely, hopefully
<DC-IRC> [Discord] <amazingfate> Vop2 driver for rk3588 did not work on rk356x, I don't know if mainline has solved it.
<DC-IRC> [Discord] <tyro_noob> The image is from Armbian website.
<DC-IRC> [Discord] <igorpec> who needs new RC for RK3588 https://github.com/armbian/build/pull/6340 review
<DC-IRC> [Discord] <rpardini> I've rebases upcoming for rc6 too
<DC-IRC> [Discord] <rpardini> https://github.com/armbian/build/pull/6342
<DC-IRC> [Discord] <igorpec> ok
<DC-IRC> [Discord] <Tonymac32> I'm not familiar with what our RK3568 images look like, the kernel family, etc. If it's 5.10 that sounds like a Rockchip kernel. Please provide the requested information at minimum.
<DC-IRC> [Discord] <shivansps> Waiting on 6.9-RC1, that one should include HDMI and panthor
<DC-IRC> [Discord] <monkablyat> And what about the Mali firmware? There would have to be a solution because if Panthor is merged into upstream mesa you can simply build an image with Oibaf PPA
<DC-IRC> [Discord] <shivansps> panthor userspace driver in mesa can work with mali blob then?
<DC-IRC> [Discord] <efectn> It's exists on linux-firmware
<DC-IRC> [Discord] <efectn> HDMI PHY is mainlined, bridge is not so still need some patches for bridge
<DC-IRC> [Discord] <efectn> Also need patches to add gpu nodes to rk3588s devicetree
<DC-IRC> [Discord] <monkablyat> As far as I understand, there are two versions of the mali blob, one for the BSP kernel and one for mainline. We need the BSP blob for legacy builds, which is available in amazingfate's PPA, but is missing for rk3588 legacy debian builds and there is a blob for mainline that is currently missing at the armbian firmware but is part of the linux firmware git
<DC-IRC> [Discord] <efectn> Yeah
<DC-IRC> [Discord] <efectn> I suppose it is not good idea to use rockchip blob with panthor
<DC-IRC> [Discord] <monkablyat> Indeed so a different solution must be found for the blob so that the BSP blob is integrated for legacy builds and the mainline blob for mainline builds
<DC-IRC> [Discord] <amazingfate> rk 6.1 kernel rebase info: https://github.com/armbian/linux-rockchip/issues/154
<DC-IRC> [Discord] <shivansps> but you need the blob at all? i trought that was wha the drm driver was for
<DC-IRC> [Discord] <shivansps> but you need the blob at all? i trought that was what the drm driver was for
<DC-IRC> [Discord] <shivansps> but you need the blob at all? i trought that was what the drm driver was for
<DC-IRC> [Discord] <monkablyat> Yes you need the BSP blob for panfork and GPU acceleration via rockchip blob's on the BSP kernel and the mainline blob for upstream mesa with panthor merg
<DC-IRC> [Discord] <shivansps> then i dont undertand what was merged into drm-misc-next
<DC-IRC> [Discord] <shivansps> i trought that is the kernel driver
<DC-IRC> [Discord] <shivansps> i trought that panthor-mesa could be used by either this open source panthor-csf-drm-driver or the mali blob
<DC-IRC> [Discord] <shivansps> and performance may not be the same as i dont know if the mali blob used hardware scheduling
<DC-IRC> [Discord] <shivansps> and performance may not be the same as i dont know if the mali blob uses hardware scheduling
<DC-IRC> [Discord] <monkablyat> Unfortunately, I can't answer you exactly what both blobs do at the end of the day. It's hard enough trying to keep an overview with all the rochchip madness. However, as far as I know, the mainline blob is also needed for Panthor Mesa
<DC-IRC> [Discord] <shivansps> ill see if i can get answers at mesa but it makes no sense to me, i trought the panthor drm kernel driver and mesa panthor userspace driver is everything we needed