02:09 <chewitt> ndufresne: that's interesting

02:09 <chewitt> there's some changes to the DRM code in 5.1 .. once we get to rc3 i'm planning to rebase my branch and probably switch to the new kernel model (instead of kbase)

02:10 <chewitt> extracting and combining the patch-sets for lima/panfrost is one-step too awkward under 5.0 but 5.1 reduces other patch-sets and should make it entertainable

05:49 <brads> narmstrong: have been trying your gitlab of g12b https://gitlab.com/superna9999/linux/commits/amlogic/v5.1/g12b-odroid-n2 but I fail early boot (it appears the board almost powers off)

05:49 <brads> https://pastebin.com/RwEaj8uP

05:53 <brads> I have tried a few things to debug but not getting too many hints on the console, the log above I have triied disabling USB subsystem, USB PHY's and adding some debug. In a another boot I disabled the rtc. Maybe this might be in the power requlator setup, I see it mentions "[ 8.830718] VDDAO_1V8: supplied by VDDAO_3V3" which appears odd

05:55 <brads> should also mention in the log above I have maxcpus=1 set

06:10 <narmstrong> brads: at which point does it stop booting ? Did you add earlycon to the bootargs ?

06:11 <narmstrong> brads: ignore my msg I saw you shared the boot log...

06:23 <narmstrong> brads: seems GPIOH_6 locks your board

06:24 <narmstrong> Well it works on mine :-/ but since hk doesn’t share the schematics it was a guess looking at the hk uboot and kernel src...

06:24 <narmstrong> Try disabling this regulator

06:24 <brads> Thanks I will give it a try, this bit looked interesting "meson-g12a-pinctrl ff634400.bus:pinctrl@40: request pin 22 (GPIOH_6) for periphs-banks:449"

06:28 <brads> I will see what hardkernel can tell me about it

08:23 <hexdump0815> i just tried to build and use the meson_gx_mali_450 module on 5.0.1 mainline - it compiled and initialized (dmesg /dev/mali etc.) fine, but when i try to use anything egl it gives me "ret != 0" from https://github.com/superna9999/meson_gx_mali_450/blob/DX910-SW-99002-r6p1-01rel0_meson_gx/driver/src/devicedrv/mali/linux/mali_memory.c#L292-L294

08:24 <hexdump0815> the exact same setup (mali blob, meson_gx_mali_450 sources) worked fine with a balbes 4.19.13 kernel

08:25 <hexdump0815> are any extra kernel patches required for meson_gx_mali_450 in 5.0 or in general or did anything change between 4.19 and 5.0 which broke mali support? does it work for others with 5.0?

08:26 <hexdump0815> any special kernel config options required beyond defconfig for it (maybe the balbes kernel had something extra in it)?

08:26 <hexdump0815> btw. system is a s905w box

09:19 <chewitt> hexdump0815 what app(s) do you need to run? .. i.e. can you dump the blob and use lima instead?

09:19 <narmstrong> I think I will mark this module deprecated for now usages and point to Lima

09:20 <chewitt> balbes150 tracks my patch sets for LE and I stopped using the blob as for Kodi use lima runs fine

09:20 <narmstrong> hexdump0815: can you try the fix in https://github.com/superna9999/meson_gx_mali_450/pull/7 ?

09:21 <narmstrong> honestly I haven't used this module for a while now...

09:33 <narmstrong> I think I made panfrost work with the DRM driver on S912

09:58 <hexdump0815> narmstrong: thanks a lot, that pull fixed the problem - not it works fine with 5.0 as well :)

10:00 <hexdump0815> i'm using it for vcvrack.com - an open source modular synthesizer, its an opengl app which works well with gl4es as opengl wrapper and mali - i guess lima is not yet ready for it, but maybe i should give it a try ...

10:01 <hexdump0815> is the interactive x11 performance better with lima than with the armsoc/mali combination?

11:09 <narmstrong> xdarklight: I get `[ 4.851477] phy phy-d0078080.phy.3: unsupported PHY mode 5

11:09 <narmstrong> [ 4.856266] xhci-hcd: probe of xhci-hcd.0.auto failed with error -22` on 5.1-rc1

11:09 <narmstrong> dwc3 seems to use PHY_MODE_USB_HOST_SS for the USB3 phy

11:14 <narmstrong> weird

11:15 <narmstrong> may be this one https://marc.info/?l=linux-usb&m=154806984316445&w=2

13:05 <narmstrong> xdarklight: fixed in https://patchwork.kernel.org/patch/10865277/

13:05 <narmstrong> not yet merged

13:20 <narmstrong> if people want to test panfrost or lima : https://github.com/superna9999/linux/tree/linux-5.1-le-amlogic-gx

13:20 <narmstrong> for panfrost, you only need mesa master branch https://github.com/superna9999/linux/tree/linux-5.1-le-amlogic-gx

13:21 <narmstrong> for lima you will need : https://gitlab.freedesktop.org/yuq825/mesa/tree/topic/lima-master-upstream-v2

13:22 <narmstrong> it'a _all_

13:26 <narmstrong> `meson .. . -Ddri-drivers= -Dvulkan-drivers= -Dgallium-drivers=panfrost,kmsro -Dlibunwind=false` for panfrost and `meson .. . -Ddri-drivers= -Dvulkan-drivers= -Dgallium-drivers=lima,kmsro -Dlibunwind=false`for lima, maybe both could work using the lima branch