00:07 <smaeul> LordKalma: the interrupt-parent properties are fine to be there. they tell Linux to route wakeup-capable interrupts through the wakeup-capable interrupt controller, so they are useful for system suspend. but they don't hurt anything otherwise.

08:18 <LordKalma> thanks smaeul

09:39 <apritzel> LordKalma: so is there something not working? I would try to address one issue after another, and not care too much about the pure differences against the vendor DT

10:55 <LordKalma> the display wasn't working still, checking that diff I noticed there was a "disabled" in my DTS on the MIPI interface (bad!) :)

10:55 <LordKalma> so the whole exercise was positive

10:56 <LordKalma> that said, display still doesn't work, but I'm closing in :)

10:57 <LordKalma> https://gist.githubusercontent.com/ruilvo/79ef3c6070d1d196d77807de651404e2/raw/1d3ef9a4918971c5e59a74a3e8374fc2791db6c5/log.txt

11:00 <LordKalma> "# D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz" and "timings 0 0 0 0 0 0 0" can't be good

11:00 <LordKalma> but I can get back to that now

11:00 <LordKalma> now that I'm confortable it's probably not the dtb ;)

11:49 <karlp> apritzel: did you ever find a solution ot the FEL boot with env in MMC?

11:52 <apritzel> karlp: do you mean without CONFIG_ENV_IS_IN_FAT defined?

11:52 <karlp> yeah.

11:52 <karlp> i was just reading the logs again,

11:52 <apritzel> so I have a simple patch that fixes this particular issue

11:52 <karlp> yeah, adding mmc to the end of the fat/ubi case right?

11:52 <apritzel> yes

11:53 <apritzel> I am tempted now to merge it

11:53 <karlp> the "real" fix seems substantially bigger :)

11:54 <apritzel> not necessarily bigger, but taking more time to think about, and touching generic code

12:45 <blathijs> Is disp.screen0_output_mode on the kernel cmdline still the way to force a specific resolution to be used on HDMI? I'm running a recent Armbian (15.19.14-sunxi) on an Orange Pi PC, and that option is explicitly listed in boot.scr, to be configured using disp_mode in armbianEnv.txt, but it does not seem to work. So I'm wondering if this option is still expected to work and I

12:45 <blathijs> should be figuring out why it doesn't, or maybe the armbian config is outdated and there is a new way for this?

12:51 <blathijs> (kernel 5.19.14 btw, not 15.19.14)

13:02 <blathijs> It looks a bit like this option applied with the older sunxi kernel fork, but is not supported by the more recent upstream sun4i drm driver that I think is used in recent armbian versions. From reading https://wiki.archlinux.org/title/kernel_mode_setting#Forcing_modes, using `video=` might be the way forward with drm/kms drivers, let me try that.

13:07 <blathijs> Yup, that seems to work as expected