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] <stonededge> Sure, we can give this a try. How to I interrupt the uboot process exactly? Press any key?
<DC-IRC> [Discord] <stonededge> https://pastebin.com/86wJsG3z
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC> [Discord] <amazingfate> videoconvert can't use rga. You have to use v4l2convert. Here is the pipeline I use to test mainline rga:
<DC-IRC> [Discord] <amazingfate> ```
<DC-IRC> [Discord] <amazingfate> gst-launch-1.0 videotestsrc ! video/x-raw,format=BGRx ! v4l2convert ! openh264enc ! h264parse ! qtmux ! filesink location=xyz.mp4
<DC-IRC> [Discord] <amazingfate> ```
<DC-IRC> [Discord] <amazingfate> Check if rga is used:
<DC-IRC> [Discord] <amazingfate> ```
<DC-IRC> [Discord] <amazingfate> watch -n1 'cat /proc/interrupts |grep rga'
<DC-IRC> [Discord] <amazingfate> ```
<DC-IRC> [Discord] <rpardini> Yeah, I see now, it's the `retro-lite-cm5` board, no?
<DC-IRC> [Discord] <rpardini> Mainline u-boot, sans any customizations. So it's fully bootstd. AFAIK it should support Android "v4" boot images, whatever those are.
<DC-IRC> [Discord] <rpardini> Try this: https://github.com/armsurvivors/armbian-build/commit/f30a9ec0b0d424a0ad1328adda4f79a56ed78951 -- absolutely no idea if this will work, but worth a try.
<DC-IRC> [Discord] <rpardini> (Might need BL32 at line 37 / `UBOOT_TARGT_MAP` too)
<DC-IRC> [Discord] <rpardini> Yeah, I see now, it's the `retro-lite-cm5` board, no?
<DC-IRC> [Discord] <rpardini> Mainline u-boot, sans any customizations. So it's fully bootstd. AFAIK it should support Android "v4" boot images, whatever those are.
<DC-IRC> [Discord] <rpardini> Try this: https://github.com/armsurvivors/armbian-build/commit/f30a9ec0b0d424a0ad1328adda4f79a56ed78951 -- absolutely no idea if this will work, but worth a try.
<DC-IRC> [Discord] <rpardini> (Might need BL32 at line 37 / `UBOOT_TARGET_MAP` too)
<DC-IRC> [Discord] <stonededge> Thank you. Actually, we're kinda struggling to install our new u-boot at all to be honest... does anything look weird with the platform_install script?
<DC-IRC> [Discord] <rpardini> Let me take a look later tonight when I'm off work.
<DC-IRC> [Discord] <rpardini> Seems like you're mixing binman and non-binman stuff there
<DC-IRC> [Discord] <stonededge> Thanks man
<DC-IRC> [Discord] <stonededge> Thank you. Actually, we're kinda struggling to install our new u-boot at all to be honest... looks like this isn't overwriting the old uboot when I try to install it. does anything look weird with the platform_install script?
<DC-IRC> [Discord] <beohoff3174> @amazingfate , can you point me in a spot to understand how to get panthor and mesa to play together in Ubuntu?
<DC-IRC> [Discord] <beohoff3174> Ive been compiling mesa to ensure it has support, but i need swsrast for qt, which wants to pull in llvmpipe and others
<DC-IRC> [Discord] <beohoff3174> Happy to dig around, but if you can point me some place to start digging, ill take any pionters as it seems lightly documented right now
<DC-IRC> [Discord] <amazingfate> File `/usr/lib/aarch64-linux-gnu/dri/panfrost_dri.so` from package `libgl1-mesa-dri` is the userspace gpu driver. If command `glxinfo` outputs `Panfrost` then panthor kernel driver is running, and qt apps will just use panfrost gl/egl driver.
<DC-IRC> [Discord] <jonh7776> 440. It does list and use 4k (which the monitor supports but isn't a native resolution obviously). EDID doesn't list 5120x1440 either on the new kernel although it did on the older .43 kernel. I've also tried edge (6.10-rc7) with similar results.
<DC-IRC> [Discord] <jonh7776> I'm having difficulty getting my 5120x1440 ultrawide monitor to work with the latest vendor kernel (6.1.75). I've had problems in the past but loading the 8k hdmi overlay seemed to fix that. I'm using exactly the same hardware so nothing changed there. Just a different kernel. When I look at available video modes in the /sys/class/drm tree it doesn't list 5120x1440 or even 2560x1 <clipped message>
<DC-IRC> [Discord] <jonh7776> I'm sort of at a lost for what could be going on here. It seems I fix this problem only to have to show up again when I change kernels. I really thought going to a newer vendor kernel wouldn't re-create this issue. I'll have to stick with the .43 kernel if I can't figure this out.
<DC-IRC> [Discord] <jonh7776> Any tips of how to understand what is going on under the hood here?
<DC-IRC> [Discord] <Werner> Was just a matter of time until someone discovers something that broke with the transition to rkr3 😂
<DC-IRC> [Discord] <h2o3046> There is no hdmi audio on mainline?
<DC-IRC> [Discord] <amazingfate> vop drivers has changed and I guess there should be a new version of 8k hdmi overlay.
<DC-IRC> [Discord] <rpardini> yeah this is strange -- when I build it (`BOARD=retro-lite-cm5 BRANCH=vendor`) I get completely different `platform_install.sh`, containing the correct `write_uboot_platform()` function pointing to binman `u-boot-rockchip.bin`
<DC-IRC> [Discord] <efectn> Yes
<DC-IRC> [Discord] <jonh7776> Ah, I will take a look and see if I can figure that out. I have little experience with overlays
<DC-IRC> [Discord] <rpardini> yeah, I can't see how you ended up with with that u-boot; even Ivan's first commit of that board file is already on mainline and with binman. Have you a fork that's outdated/different or something like it?