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
PhotoJim has joined #armbian-rockchip
<DC-IRC> [Discord] <microlinux> I just made them bc back then there wasn't ubuntu rockchip for them and the opi-armbian relationship was broken.
<DC-IRC> [Discord] <microlinux> I am testing opi 3b at the edge right from the builder regularly
<DC-IRC> [Discord] <microlinux> But, I don't have the 2.1v model
<DC-IRC> [Discord] <microlinux> There is a lot of love by @kwiboo, @amazingfate and armbian contributors in general towards the board. Someone enabled UHS on the dtb and it works flawlessly.
<DC-IRC> [Discord] <microlinux> I tend to avoid such experiments bc enabling it on the dtb alone usually does not work.
<DC-IRC> [Discord] <ioncube7221> _Someone enabled UHS on the dtb and it works flawlessly_ what does it mean?
<DC-IRC> [Discord] <microlinux> That the sd card sequential speeds bumped from 24MB/s to 72MB/s
<DC-IRC> [Discord] <microlinux> Similar improvements on random read/writes
<DC-IRC> [Discord] <microlinux> That the sd card sequential reading speeds bumped from 24MB/s to 72MB/s
<DC-IRC> [Discord] <microlinux> Since boot order defaults to sd, it's excellent for testing other system's from sd.
<DC-IRC> [Discord] <ddeath5421> Any idea how to debug `optee check api revision fail: -1.0` ? 😄 Trying to run armbian on Orange Pi 5 Max and in uart debug output I see only that stuff
<DC-IRC> [Discord] <efectn> Do you have full output
<DC-IRC> [Discord] <ddeath5421> https://pastebin.com/0X6De6LS
<DC-IRC> [Discord] <beohoff3174> What's the high level on the driver state for encoding / decoding on RK3588?
<DC-IRC> [Discord] <beohoff3174> Looking at the mpp code, patches that have been submitted to the kernel, and `verisilicon/hantro_drv.c`, I'm guessing:
<DC-IRC> [Discord] <beohoff3174> 1) mpp won't compile against the latest kernel version
<DC-IRC> [Discord] <beohoff3174> 2) a lot of the mpp code would probably be device tree or a .dts
<DC-IRC> [Discord] <beohoff3174> 3) it would take custom development or porting the mpp code to the linux drivers
<DC-IRC> [Discord] <beohoff3174> 4) all of the above is probably a lot of work
<DC-IRC> [Discord] <beohoff3174> Has anyone played around with the code at all?
<DC-IRC> [Discord] <ioncube7221> Will it effect NVME r/w speeds? &mind can you further explain this with some github link, what code is UHS?
<DC-IRC> [Discord] <ioncube7221> Will it effect NVME r/w speeds? And can you further explain this with some github link, what code is UHS?
<DC-IRC> [Discord] <ioncube7221> In my opinion a OPi3b must have have x2 separate board entries in build script, for v1.1 & v2.1
<DC-IRC> [Discord] <microlinux> No, that would ne too complicated, we cant target the different dtb after the first boot
<DC-IRC> [Discord] <microlinux> Of course no, UHS is a microsd standard
<DC-IRC> [Discord] <microlinux> Of course not, UHS is a microsd standard
<DC-IRC> [Discord] <Werner> I think he means literally two board configs that can be chosen while building an image
<DC-IRC> [Discord] <microlinux> Okay then ahha
<DC-IRC> [Discord] <kwiboo> For mainline it should probably be possible to use a single board config, with `unset BOOT_FDT_FILE` similar to https://github.com/armbian/build/pull/6842 correct DTB will be picked and correct Ethernet PHY voltage is be used, else history will repeat itself and users may end up with broken Ethernet
<DC-IRC> [Discord] <microlinux> Is there any roadmap towards 6.10 on edge?
<DC-IRC> [Discord] <microlinux> Maybe it's already possible
<DC-IRC> [Discord] <microlinux> I am mostly interested bc of the official panthor landing
<DC-IRC> [Discord] <microlinux> Not bc of rk3566
<DC-IRC> [Discord] <kwiboo> Then again I am not an armbian user, nor do I run vendor kernel on my boards, my only interest with opi3b (and other boards) is that I sent board DT upstream and I am listed as maintainer/reviewer of it in mainline U-Boot
<DC-IRC> [Discord] <microlinux> Oh, sure good to know
<DC-IRC> [Discord] <microlinux> So, you are a uboot maintainer
<DC-IRC> [Discord] <microlinux> I may do a video about uboot down the road
<DC-IRC> [Discord] <microlinux> But I will share you the script before. It's too technical
<DC-IRC> [Discord] <microlinux> I've never seen any yt video about uboot and that's a shame.
<DC-IRC> [Discord] <microlinux> Specially with the new uefi stuff
<DC-IRC> [Discord] <microlinux> Sadly, rk3566 doesn't output uboot on screen
<DC-IRC> [Discord] <microlinux> Only through uart
<DC-IRC> [Discord] <kwiboo> I am only listed as board maintainer for a few rk boards, not a real uboot maintainer with my own custodian tree or anything 🙂
<DC-IRC> [Discord] <microlinux> It would be awesome if newer uboot versions find a way to output anything to linux. Like, it only happens on uefi mode
<DC-IRC> [Discord] <microlinux> On uefi mode, I can see the uboot version at least from linux
<DC-IRC> [Discord] <microlinux> The conventional mode (no idea what name would have), has no idea about the used uboot on boot nor what parameters were used for ram, overlays, etc.
<DC-IRC> [Discord] <kwiboo> yeah, it would be nice to have full video support in u-boot, for me personally it is not something I am really missing, and is not something I have any plans to work on or look into
<DC-IRC> [Discord] <microlinux> No problem
<DC-IRC> [Discord] <kwiboo> typically video in uboot on rk platform cause some issue for video in linux (mainline), so for now I usually recommend to disable video feature of uboot
<DC-IRC> [Discord] <microlinux> What you do is more than we can ask
<DC-IRC> [Discord] <microlinux> What you do is more than what we can ask
<DC-IRC> [Discord] <microlinux> Text me of you get the rkvdec2 problem solved for fmmpeg/mpv for noble
<DC-IRC> [Discord] <microlinux> I was shocked by vp9 performance on rk3399 with mpv (rkvdec there I guess)
<DC-IRC> [Discord] <microlinux> 4k30 was sensational
<DC-IRC> [Discord] <kwiboo> Hehe, hoping to get out an updated ffmpeg v4l2-request v3 series any day now, with support for vp8, vp9 and av1. Focus should be on rkvdec drivers after that 🙂
_whitelogger has quit [Ping timeout: 252 seconds]
_whitelogger has joined #armbian-rockchip
<DC-IRC> [Discord] <microlinux> Nicee
<DC-IRC> [Discord] <smiggiddy> I must've done something wrong cuase my current is on 6.10 lol `6.10.7-current-rockchip-rk3588`
<DC-IRC> [Discord] <lanefu> rk3588-edge is 6.11 rc4 current might have gotten shifted to 6.10
<DC-IRC> [Discord] <jonh7776> That is correct for current on rk3588.
<DC-IRC> [Discord] <efectn> Probably uboot defconfig is wrong. Which source are you using?
<DC-IRC> [Discord] <pjack1212> hi does anbody know if current mainline u-boot is working without problem for vendor kernel on rk3568 plattform armbian is using radxa u-boot which is from 2017 and doesnt support btrfs, i know that npu and pcie 2.0 didnt work previsouly
<DC-IRC> [Discord] <pjack1212> because i have to build my own u-boot because vendor doesnt support boot from m.2 e-key (pcie 2.0 disable) i thoughth i could switch to mainline at the same time