00:14 <agl> steev: Have you contacted clover[m]?

00:17 <steev> why would i?

00:18 <agl> steev: Because the EndeavourOS arm there worked all and after an upgrade (yay -Syyu) the grafical system does not work.

00:18 <steev> i don't use endeavoros

00:22 <agl> yes, you want bevor some days that I send some thinks form /lib/firmware (you look about the versions) and other directories and you find nothing. Then you say you would contakt clover[m] when he is back.

00:26 <steev> no, i said you should, because i don't use endeavor and i have no idea where to look or why that would occur. i'm not going to do your work for you and just be a middle man

00:28 <agl> ok, I understood that you would contact him. Ok, I see clover[m] is not in the user list ... then I have to wait if he is back ....

00:30 <abby> probably the matrix bridge being bad

00:31 <agl> ok I can try to use matix. I have until now not an Account there.

00:32 <agl> steev: Sorry, that I mean you want to contact clover[m].

00:33 <agl> steev: My english language is not so good.

00:35 <steev> your english is better than my german :)

00:37 <agl> ok, the german language is a little bit difficult to learn it for a english man ;-)

01:18 <clover[m]> i think the bridge is working again

01:25 <abby> every time the bridge crashes it tries to reconnect every user who's ever connected, which just leads to it crashing again and again until it finally recovers within a week or two

01:26 <colemickens> I think I am one linux-firmware repo away from having a test nixos iso with grub entries for each DTB. :D

03:34 <agl> clover[m]: In this moment the grafical system starts under EndeavourOS arm, but some times it starts not. I can not understand why sometimes the grafical system starts and why not at an another start.

03:36 <clover[m]> Okay did you get any log info about it

03:37 <agl> not yet it runs in this moment

03:37 <agl> I look

03:43 <agl> clover[m]: Under dmesg it says adreno is loaded and running

05:45 <strongtz[m]> colemickens: not much actually, you can use Abel's branch or simply linux-next

08:33 <JensGlathe[m]> New deb packages available for Ubuntu, -el2, and Pop! (6.10-rc6) https://drive.google.com/drive/folders/1Lps5o3FXroAJFDiKj18vutJbC1uld49s?usp=drive_link

09:26 <steev> i'll probably push my 6.9.8 tomorrow

09:27 <steev> i was trying to figure out this pmu stuff for the bluetooth, but i think i'll leave it for someone who has schematics

09:28 <steev> seems like the person who submitting it has plans to do x13s anyway, at least based on my reading of it

16:10 <mani_s> maz, I'm seeing a behavior with gic-v3-its driver where if odd number of MSIs are requested (ex. 3) using pci_alloc_irq_vectors_affinity(), then its_alloc_device_irq() allocates log2 of the MSI count (ex. 4). But when pci_free_irq_vectors() is called, it only frees the 3 MSIs

16:12 <mani_s> leaving 1 MSI always allocated. When the driver is unloaded and loaded again, requesting 3 MSIs again is failing because of the previous 1 MSI already allocated (here max MSI is 4).

16:13 <mani_s> I can see that this behavior is applicable to other irqchip drivers also using bitmap to manage irqs.

16:15 <mani_s> 'driver is unloaded' -> I'm referring to the PCI driver.

16:17 <kettenis> mani_s: Someone should tell Qualcomm that shipping hardware with PCI devices that uses multiple MSI vectors but doesn't support MSI-X is unacceptable in 2024

16:18 <mani_s> kettenis, I'm don't agree with this statement. If the PCI device has no requirement to support > 32 MSI vectors per function, then there is no need for MSI-X

16:19 <mani_s> Most of the chipsets that Qcom supports for PCI devices are for modems, WLAN, where 32 MSIs is more than enough

16:20 <mani_s> That's one of the reason why PCIe spec hasn't deprecated MSI

16:28 <kettenis> multi-vector MSI has some serious design flaws that make it interact poorly with many interrupt controller designs

16:29 <kettenis> MSI-X fixes those flaws and every other vendor seems to be able to implement it even for devices that need significantly less than 32 vectors

16:29 <kettenis> the issue you're seeing is entirely because of that design flaw

16:30 <kettenis> I just implemented multi-vector MSI support for an OpenBSD PCIe controller driver that has exactly the same flaw ;)

16:56 <gabertron> Has anybody made a working / partially working dts for the t14s x1 laptop? Was taking a look at that but thought I’d check if there was one out there that I could start with

17:06 <mani_s> kettenis, ah okay... I was checking if this is something already known or not. Sounds like it is ;)

17:14 <JensGlathe[m]> <mani_s> "maz, I'm seeing a behavior..." <- Hmm looks loke some bit shifting only in one of the driver functions. Maybe a good idea to take a look at this driver

17:19 <mani_s> JensGlathe[m], It is not *this* driver specific issue, but applies to other drivers as well.

17:21 <JensGlathe[m]> mani_s: I figured after reading again. Fix would be to allocate log2 vectors only to ensure it doesn't bite

17:23 <robclark> gabertron: most folks interested in t14 seem to be holding out for option to configure device

17:24 <mani_s> JensGlathe[m], yes, that looks like the only possible solution to me. But currently, drivers just don't do that

17:26 <mani_s> It is also tricky because, if a driver just wants odd number of vectors, why should it request more vectors? And what should it do with those? Just return IRQ_HANDLED? That sounds sub optimal

17:27 <JensGlathe[m]> It would solve the problem. Wouldn't cost too much tbh, if the spec is flawed as kettenis suggests.

17:30 <clee> gabertron: in the branch with the (mostly) working DTS/DTB for my Yoga Slim 7X, I see: x1e80100-{crd,qcp,surface,vivobook,yoga}.dts so I'm guessing not yet for the T14S

17:30 <clee> (I wonder how different it is from the Yoga…)

17:36 <mani_s> JensGlathe[m], in that case, the restriction should be imposed in the API level i.e, for all pci_alloc_irq_vectors*() API

17:41 <JensGlathe[m]> It could even wire up the unused vectors with the "dummy" handler

17:43 <JensGlathe[m]> Keeping track of them might be tricky...?

18:18 <gabertron> Yea I tried the crd dts but no luck so far but will try the yoga to see if that works

19:23 <konradybcio> gabertron send me an acpi dump and ill send you a dts back..

19:23 <konradybcio> https://dortania.github.io/Getting-Started-With-ACPI/Manual/dump.html#from-windows

19:30 <gabertron> Oh nice Will do thanks! (Later today thanks)

23:41 <colemickens> Anyone testing on the Surface Pro? I'm considering it over the Yoga but worried about the Flex keyboard being some kind of proprietary Bluetooth handshake with the tablet/windows.