06:31 <brads> narmstrong: do you have an idea how difficult it would be to implement kernel side mali driver for the g12b branch of your gitlab for testing? ie something based on this: https://developer.arm.com/products/software/mali-drivers/bifrost-kernel

06:32 <brads> hardkernel have released some wayland userspace patches to try https://dn.odroid.com/S922X/ODROID-N2/Wayland/

06:32 <narmstrong> brads: you mean https://github.com/superna9999/meson_g12a_mali_bifrost ?

06:32 <narmstrong> Never tested but should work

06:32 <brads> that would be it :) awsome

06:32 <brads> Thanks!

06:33 <narmstrong> It works fine on g12a and the integration is the same

06:34 <brads> ok great ill give it a try, most other basic things working quiet well on g12b as well

08:55 <brads> narmstrong: kernel driver worked well, only needed a small version check change (due to it technically being against the 5.0-rc+ kernel rather than 5.1).

08:57 <brads> I also tried the hardkernel/ malogic wayland drivers and weston has no issues detecting and utilsing the gpu :)

08:57 <brads> I had some issues with mutter / gnome but that is another story

08:57 <brads> or rather have

09:37 <memeka> brads: Ping

09:38 <memeka> brads: download the so from https://oph.mdrjr.net/memeka/bionic/gbm_compat/

09:39 <memeka> Set in /etc/environment LD_PRELOAD=/path/gbm_compat.so

09:39 <memeka> Reboot and run gnome

10:01 <brads> memeka: thanks I will give this a try in a bit

10:09 <narmstrong> brads: cool pretty good news !!

10:55 <brads> memeka: (wrong ELF class: ELFCLASS32)

10:56 <brads> I will have to try a compile

10:59 <memeka> brads: haha yes sorry it’s from armhf (xu4)

10:59 <memeka> Compile the c file as .so :)

11:15 <memeka> brads: did it work?

11:17 <brads> im about to reboot and try

11:34 <brads> memeka: now I can start gdm3 to the login screen (no longer an "on wayland" option thought to choose from). If I try to login it just resets to the login screen again so I have to see what might be missing and get some logs

11:35 <memeka> brads: try from console (no gdm): mutter —wayland —displayserver

11:35 <memeka> Check mutter —help maybe I have misspelled

11:35 <memeka> If you get a brown background => all good

11:50 <brads> memeka: clutter has a problem - Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found.

11:50 <brads> I might simply be missing some libraries

11:51 <memeka> brads: I think it’s trying gl

11:51 <memeka> There is an env var

11:52 <memeka> CLUTTER_BACKEND=gles2 mutter —wayland —

11:52 <memeka> —displayserver

11:53 <memeka> CLUTTER_DRIVER :)

11:55 <memeka> CLUTTER_DRIVER=gles2 mutter —wayland —display-server ?

11:55 <memeka> brads: ^^^

12:07 <memeka> brads: any luck?

12:25 <brads> memeka: no luck the same error

12:31 <brads> glmark-es2-wayland works inside weston, glmark2 Score: 1119

13:47 <narmstrong> wow

13:47 <narmstrong> brads: in fact, the right branch to use was `amlogic/v5.1/g12b-odroid-n2-integ`

13:47 <narmstrong> it contains all the fixes and current work on g12a

13:48 <narmstrong> but I forgot to push the branch...

13:48 <narmstrong> brads: can you check if it still works ?

17:32 <xdarklight> narmstrong: congrats for getting the G12A PHY patches merged :). I hope the USB/dwc3 maintainers will comment on the other patches this week

18:02 <hexdump0815> i have successfully chainloaded mainline uboot in legacy uboot, did load kernel, initrd and dtb from usb in it and then tried to boot it but always got either "Bad Linux ARM64 Image magic!" or "Wrong Image Format for bootm command" with various combinations of bootm/booti and the Image from a kernel build or a uImage created via mkimage

18:03 <hexdump0815> what would be the proper image format and boot command to use for mainline uboot and mainline kernel?

18:09 <hexdump0815> all the above is on a s905w box using the khadas vim uboot chainloaded

18:25 <narmstrong> hexdump0815: the plain Image from the kernel build is the most appropriate

18:25 <narmstrong> hexdump0815: beware where you load it, maybe you load it over a reserved memory area

18:30 <narmstrong> xdarklight: thanks for your reviews !!

18:32 <hexdump0815> narmstrong: thanks a lot - what address would be good? - i used 0x11000000 or 0x01080000 with uboot at go 0x01000000

18:33 <hexdump0815> for the plain kernel build image it would be booti then - right?

18:48 <narmstrong> We use 0x8080000 in pyamlboot

18:49 <narmstrong> And 0x13000000 for the initrd

20:27 <xdarklight> narmstrong: you're welcome - you're now part of the very exclusive club of Amlogic PHY mainline driver authors :)

20:29 <xdarklight> narmstrong: also the PWM discussion went in a totally different direction than I initially thought it would :/ I didn't think someone would find issues with the existing code (apart from what Jerome already noticed before: that we don't pass the clock inputs in .dts and some "I can replace this with a bit from the PWM core" changes that I already made)

20:48 <brads> narmsrong: I will try the g12b-odroid-n2-integ later today

20:49 <brads> memeka: I will do some more debug with mutter and see if I can work out why it is failing

20:50 <memeka> brads: i have a pretty good suspicion :)

20:50 <memeka> you need to compile it again, with different flags

20:50 <memeka> to disable GL and enable EGL/gles2

20:50 <brads> ok, I think I remmember this Rabbit hole on the C2 :|

20:52 <memeka> brads: that's ok, if weston is working, then mutter/gnome should work too

20:52 <memeka> i have more experience with it, i'll try to make it work

20:52 <memeka> provided I can get my monitor to show something :(

20:53 <brads> Awsome, would be very helpful :)

20:53 <memeka> narmstrong: any ideas about the monitor thing? :( i tried with video=HDMI...1080p@60 but didn't work :(

20:53 <memeka> all i get is a black screen :(

21:03 <brads> memeka: I still have an issue of needing to boot to text mode console only (or I get a black screen on boot).

21:03 <brads> I can start up weston after logging into the console

21:40 <hexdump0815> narmstrong: with your addresses it boots perfectly - thanks - as a nice side effect the chainloaded mainline uboot does not eat up as much memory as the legacy one - about 120m saved this way for free :)

22:56 <memeka> anyone can help with debugging why i get no output on my monitor?