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
lanefu has quit [Server closed connection]
lanefu has joined #armbian-rockchip
montjoie has quit [Ping timeout: 255 seconds]
montjoie has joined #armbian-rockchip
<DC-IRC>
<mergelab> Anyone using the orange pi 5 plus 32GB ram.
<DC-IRC>
<infinity_q> no, but I have the 16GB model, but I don't see how it would be any different
<DC-IRC>
<lanefu> Single lpddr4 memory chips at 16GB density had been mythical for a long time. Def curious to hear from someone that has one in the wild
<DC-IRC>
<mergelab> I wonder what the use cases can be for the 32GB model vs 16 GB
<DC-IRC>
<infinity_q> AI usually, but also more exotic uses like diskless running
<DC-IRC>
<infinity_q> I might get a 32GB model sometime
<DC-IRC>
<mergelab> I need to learn AI
<DC-IRC>
<lanefu> I'm so skeptical about the useful "AI" capabilities of the NPU and "GPU" on these embedded SoCs. You can't really use the same tooling at all as the big kid stuff.
<DC-IRC>
<lanefu> Just goofy forks and things like yolo v8
<DC-IRC>
<lanefu> In my jaded opinion the NPU stuff is just enough image recognition on the edge to update someone's social credit score
<DC-IRC>
<infinity_q> except maybe openCL(if you can get it working on the gpu),but I feel the same
<DC-IRC>
<mergelab> What about opencv
<DC-IRC>
<lanefu> Googling "rknn opencv" kinda shows the landscape
<DC-IRC>
<lanefu> Looks like forks and modified stuff. I'm sure it's usable
<DC-IRC>
<djhardrich> Opi CM4 update: fixed hw cursor in DTS, last thing to fix is wifi/bt (strangely working fine on CM4 when booting with a 3b image that I’ve built; matched sections in DTS but no luck yet)
<DC-IRC>
<djhardrich> Opi CM4 update: fixed hw cursor in DTS, last thing to fix is wifi/bt (strangely working fine on CM4 when booting with a 3b image that I’ve built; matched sections in DTS but no luck yet) and then I’ll be making a PR! 🎉
<DC-IRC>
<lanefu> That's super awesome!
<DC-IRC>
<lanefu> PS Make sure your board config is .csc and not .conf when submitting PR
<DC-IRC>
<djhardrich> Yep, it’s a .csc 🙂
<DC-IRC>
<rpardini> Yo @mariob help me out here 😉
<DC-IRC>
<rpardini> I've been trying to make Armbian UEFI images for 3588 with your edk2.
<DC-IRC>
<rpardini> I've started by having UEFI `.img` directly burned to SD card, Armbian UEFI image on NVMe, works great. (SPL loads uefi ok, I get `Trying fit image at 0x800 sector` and it works)
<DC-IRC>
<rpardini> Armbian image is simple GPT with ESP partition fat32 starting at 16mb (with grub) and then ext4 rootfs partition.
<DC-IRC>
<rpardini> Now I'm trying to make a *single image containing edk2 and Armbian's GPT*, as per the instructions (`dd if=uefi.img of=armbian.img bs=512 skip=64 seek=64`)
<DC-IRC>
<rpardini> But that results in SPL not finding uefi to boot (`spl: partition error`, `Trying fit image at 0x4000 sector`, `Not fit magic`)
<DC-IRC>
<rpardini> I noticed that `misc/rk3588_spi_nor_gpt.img` is not really a GPT, instead `dos`, with a `type=ee` partition...
<DC-IRC>
<rpardini> Any ideas how to make this work? I suppose there is some magic in that `misc/rk3588_spi_nor_gpt.img` that needs to be kept / replicated somehow...?