02:03 <marcan> the ANS power domain thing won't affect battery life while active

02:03 <marcan> it should only affect battery life in suspend

02:04 <marcan> yes pstates are fixed

02:14 <chadmed_> beautiful

11:21 <jannau> nice: https://invent.kde.org/plasma/kwin/-/commit/114032d2ac4d2eb9433bf75c0e6a82ecce7fa558 I guess I should hook up color_matrix now

11:22 <chadmed> yoooooo finally

11:33 <jannau> marcan: we need to get rid of 6625def73ab9 ("arm64: dts: apple: HACK: Set base pstate to max") then

11:58 <chadmed> i would hold off on that

11:58 <chadmed> glmark2 Score: 517

11:59 <chadmed> interactivity absolutely slaughtered

15:26 <marcan> chadmed: err... okay lina has to look at that then

15:32 <lina> Between that and the kernel oopses I think next week is going to be another debugging week... ;;

15:32 <lina> chadmed: I didn't even know a glmark score that low was even possible, even at low pstates...

15:57 <jannau> unfortunately the kwin change doesn't appear to work, it never sets the ctm

17:15 <ChaosPrincess> marcan: hey, you doing releases, right? If yes, can you merge this: https://github.com/AsahiLinux/linux/pull/111

17:15 <ChaosPrincess> will help with people "forgetting to enable modules" :P

17:20 <jannau> problem seems to be that testing the gamma_lut doesn't fail

17:23 <jannau> worked around that and it sets now a all zero ctm

17:26 <marcan> ChaosPrincess: FYI you need to rebase on and request the merge against the relevant bits/ branch if you want me to apply that directly

17:26 <marcan> I can cherry pick this one though

17:27 <ChaosPrincess> Would be glad if you do, i will do that for commits to bits branches in the futures.

17:27 <ChaosPrincess> -s

17:27 <marcan> done (locally, will be in the next merge/push)

17:27 <ChaosPrincess> Ty

17:28 <ChaosPrincess> This all kernel stuff is lets just say "not exactly" the dev model im used to :P

17:30 <marcan> hey I made up the way we do it on asahi, upstream is worse :p

17:30 <ChaosPrincess> Ikr

20:03 <axboe> [ 2.203371] WARNING: CPU: 3 PID: 66 at drivers/of/irq.c:279 of_irq_parse_raw+0x504

20:03 <axboe> get a few of these on the current kernel, known?

20:03 <axboe> from...

20:03 <axboe> [ 2.130048] /soc/pcie@590000000/pci@2,0 interrupt-map failed, using interrupt-cont

20:03 <axboe> and

20:03 <axboe> [ 2.202662] /soc/pcie@590000000/pci@3,0 interrupt-map failed, using interrupt-controller

20:05 <jannau> axboe: yes. do you use u-boot with CONFIG_PCIE_APPLE=y?

20:05 <axboe> it's on, yes

20:10 <jannau> u-boot inits disabled pcie ports, we can't reset them so they are discovered in pci setup but the interrupt dt parsing code ignores disabled ports resulting in that warning

20:10 <jannau> I thinkt the wrning is harmless, disable CONFIG_PCIE_APPLE in u-boot if you want to get rid of them

20:11 <j`ey_> jannau: thats the fix you already sent to the mailing list right?

20:12 <jannau> no, the fix I sent was for linux only, booted directly from m1n1

20:13 <jannau> we need the same fix in u-boot

20:13 <j`ey_> ah ok

20:18 <kettenis> jannau: are you submitting a fix for that? or should I look into it?

20:18 <kettenis> I already fixed this for OpenBSD, so I think I know what is needed

20:19 <jannau> kettenis: I'll send a fix

20:24 <kettenis> thanks

20:35 <axboe> jannau: ok noted, thanks!

20:37 <jannau> night light works now with two bug fixes in kwin: https://invent.kde.org/plasma/kwin/-/merge_requests/3797?

20:37 <kesslerd> yay

20:37 <kesslerd> Just read the chat above that talks about upstreaming & ALARM. Is there a blog post or something explaining the situation with ALARM and the switch to a new distro for the future of the project? Or a webpage that can at least explain what ALARM is for someone who doesn't know? I keep hearing about it wanted to fully understanding what the issue was/is.

20:39 <j`ey_> https://archlinuxarm.org/

20:39 <j`ey_> that's ALARM