08:58 <tolszak> narmstrong: Hello! Is there any information about running X11 image on Odroid n2+ meta-meson? I see that default kernel on meta-meson is 5.4 but n2+ was introduced later. Or perhaps is there ongoing effort to run latest kernel?

09:08 <narmstrong> tolszak: I’m currently working on upgrading the kernel and uboot, I still need to fixup some stuff first

09:10 <tolszak> narmstrong: Is it on github? Can I help somehow - like testing builds, udpating to new syntax etc?

09:11 <tolszak> I have N2+ so I can also test images

09:11 <narmstrong> tolszak: not yet I must fix up the way the rootfs partition is selected, the kernel changed the mmc enumeration since 5.4

09:12 <tolszak> narmstrong: Is there any timeframe? Or it is available once it is done?

09:13 <narmstrong> tolszak: I hope to have something at the end of this week

09:14 <tolszak> narmstrong: How can I follow your work so that you won't be poked by every a few days?

09:15 <narmstrong> tolszak: I’ll push my current hardknott-next dev branch today so you hack it aswell !

09:15 <tolszak> narmstrong: Many thanks!

09:16 <narmstrong> For master it’s another story, it needs much more changes concerning a new bitbake syntax

09:31 <tolszak> narmstrong: I've modified my layer in 2 hours and seems like 20 times bigger than meta-meson

09:31 <tolszak> narmstrong: I don't think new syntax is a big problem

09:32 <narmstrong> tolszak: never said that, it just needs proper testing !

09:33 <tolszak> narmstrong: fair enough, the biggest issue is with custom variables/overrides which are not found by default by bitbake

09:33 <tolszak> parser

12:33 <tolszak> narmstrong: I've built latest hardknott hardkernel-odroidn2 and it doesn't boot, petit boot doesn't see boot config etc. In the boot partition there is kernel and aml_autoscript, s905_autoscript. How does it suppose to boot then? SHouldn't it have boot.ini and config init?

12:33 <tolszak> config.ini

12:35 <narmstrong> tolszak: I don’t handle the hard kernel boot process, only the amlogic vendor one. I’ll push soon the recipes with mainline u-boot…

12:37 <tolszak> narmstrong: I see wic_command_meson_gxl which seems to be invoked on the image I've built, so it may be a case that e.g. amogic-image-sato never worked with hardkernel-odroidn2 machine right?

12:38 <narmstrong> This wic cmd is ok

12:43 <narmstrong> You may need to add a recipe to provide boot.ini & co to boot using petitboot

13:51 <tolszak> narmstrong: hardkernel-odroidn2plus amlogic-image-sato has only one partition

13:52 <narmstrong> tolszak: it’s expected, mainline uboot will get the boot data from the main ext4 partition

13:52 <tolszak> so still the uboot bits are placed in first 512 bytes of sd card?

13:53 <tolszak> The image boots!

13:53 <tolszak> But I would like to see where uboot configuration is

13:53 <tolszak> e.g. where root partition is set

13:53 <tolszak> Or kernel parameters

13:53 <narmstrong> it uses extlinux.conf

13:54 <narmstrong> u-boot will look an all possible partitions to find it, and then load it and boot with the specified configuration

14:00 <tolszak> narmstrong: Boots alright!

14:01 <tolszak> narmstrong: When trying to run opengl app I see "libEGL warning: DRI2: failed to authenticate"

14:30 <tolszak> narmstrong: there is definitely no HW acceleration for opengl. I wonder if you know anything about it, I thought that newest kernel has mali g52 GPU support

14:33 <narmstrong> I’ll investigate

14:36 <narmstrong> À mesa config must be missing or the kernel doesn’t have the panfrost config enabled

14:42 <tolszak> Please let me know if I can help somehow

14:43 <tolszak> narmstrong: E.g for example point me machine that has HW support enabled and I can investigate too

14:43 <tolszak> I will call it a day today, but will look at it tomorrow early morning

14:44 <tolszak> narmstrong: Sorry for introducing confusion, I mean if you tel me e..g configuration for odroid-c2 works with proper gpu support, I can compare this configuration agains n2plus and perhaps find an issue

14:50 <tolszak> narmstrong: Qt diagnostic tool shows that X11 using softpipe mesa and egl fullscreen uses panfrost

14:51 <tolszak> narmstrong: So it is possible to run HQ accelerated applications, but perhaps not through X11

15:38 <narmstrong> tolszak: you should be able to find something in the X11 logs

15:38 <narmstrong> Maybe a mesa option is missing to enable gallium dri extensions