10:55 <warpme_> Hi!. Can anybody update me with usablility current mesa-lima? I built mesa-lima/linux-mali accordingly to https://github.com/yuq/mesa-lima/wiki booting my s905w shows in dmesg lima is loaded. Also I see /dev/dri0 for meson-dp and /dev/dri1 for lima gpu but xorg says: https://pastebin.com/A5iqDA9k Is this expected or I miss something?

11:38 <adema_> maybe you need fbdev and dbus ?

12:49 <warpme_> adema_: fbdev is nonaccell alternative to dri. I already have working dri so switching to fbdev is path to nowehere….

13:34 <narmstrong> warpme_: are you sure dri0 is the meson dp ? on my tests, it was on dri1 and it caused a lot of issus where sw expects the dp to be on dri0, but we cannot force lima to be on dri1 since it's probed before

13:34 <warpme_> narmstrong: give me sec. i’ll check it

13:36 <warpme_> well - acordingly to dmesg I think so. pls look: https://pastebin.com/wSwiaE22

16:16 <ldevulder_> narmstrong, I will do the rebase for regmap, so you didn't find anything weird in my code that could explain the kvim2 boot issue I have with my changes?

16:16 <narmstrong> ldevulder: not really

16:18 <ldevulder> narmstrong, ok thx, I will test it with your all refactoring, maybe it solves the issues :D like the USB change made by Jean-Jacques Hiblot that resolved the issues on kvim/libretech-cc (I hope this change will be merged in the next u-boot version)

16:54 <narmstrong> ldevulder: i'll be thankful if you test the refactor aswell !!!

16:55 <Xogium> anyone here getting kernel oops on kernel 4.17 on odroid c2 using nfs as sever ? http://ix.io/1tSl

16:56 <Xogium> *server

16:56 <Xogium> no idea why it does that

16:56 <Xogium> its random

16:57 <Xogium> its mean

17:34 <narmstrong> Switch to 4.18 and use the last stable release

17:34 <narmstrong> Oops 4.19

17:35 <Xogium> narmstrong: yeah, I'll do that… But that oops is annoying. I hope it was fixed, its a pain when it spawns out of nowhere

17:36 <Xogium> some mess up in memory allocation I suppose it is

17:38 <Xogium> only way is to try it I guess

17:39 <Xogium> this c2 acts weird when its under some load, could be downloading a file with wget or building stuff, they keyboard starts repeating keys at random, and a lot of times

17:39 <Xogium> *the keyboard

17:41 <Xogium> no clue why though, nothing else is affected, not sound via usb, not even the external drive plugged in

21:47 <ldevulder> narmstrong, I think I found the reason for the kvim2 boot issue

21:48 <ldevulder> after rebase my code I found this change I did:

21:48 <ldevulder> -clrsetbits_le32(priv->addr + gate->reg,

21:48 <ldevulder> +clrsetbits_le32(priv->regmap->ranges[0].start + gate->reg,

21:48 <ldevulder> BIT(gate->bit), on ? BIT(gate->bit) : 0);

21:48 <ldevulder> not so good, it's better to use this I think:

21:48 <ldevulder> - clrsetbits_le32(priv->addr + gate->reg,

21:48 <ldevulder> - BIT(gate->bit), on ? BIT(gate->bit) : 0);

21:48 <ldevulder> + regmap_update_bits(priv->map, gate->reg,

21:48 <ldevulder> + BIT(gate->bit), on ? BIT(gate->bit) : 0);

21:48 <narmstrong> Indeed it’s better

21:48 <ldevulder> like you did in clk_meson_axg.c

21:49 <ldevulder> and I'm now able to boot Ubuntu on kvim2 with my changes (and all your refactory code)

21:49 <ldevulder> but still issue on openSUSE, looks like a config diff, I will check the difference

22:56 <ldevulder> narmstrong, network looks broken on kvim with the latest u-boot and the amlogic cleanup + my patch... I need to check which patch is broken