04:27 <steev> wow, bamse has been busy

04:40 <steev> bamse: re clk_ignore_unused - what patchset does that rely on?

11:31 <ardb> has anyone made any progress with the windows dev kit?

14:03 <bamse> steev: there's a patch from abelvesa in the clk tree that you want

14:03 <bamse> steev: that i merged...

14:16 <ajhalaney[m]> he has been busy for sure lol feels like as soon as I see a TB/RB on a patch its scooped up. With that patchset from Abel are we now able to start dropping clk_ignore_unused?

14:17 <bamse> https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git/commit/?h=clk-for-6.3&id=26b36df7516692292312063ca6fd19e73c06d4e7

14:21 <steev> yeah, once we have those we can do so :)

14:23 <steev> which, i do seem to see here in my tree so i'll go ahead and give that a whirl

14:30 <steev> ajhalaney[m]: https://github.com/steev/linux/commits/sc8280xp-next-20230112 fwiw (admittedly i've only *just* started testing clk_ignore_unused not being needed)

14:30 <steev> i have to build with KALLSYMS_EXTRA_PASS=1 as well for some reason

14:31 <ajhalaney[m]> cool ill try and give that a whirl later this afternoon :) steev

14:33 <bamse> it's not giving you any noticable benefit, but i appreciate the testing

14:34 <steev> i mean, it means less typing when i screw up in grub

14:34 <steev> which i do often :D

14:34 <steev> ajhalaney[m]: http://sprunge.us/VYY4uj is the config i'm using

14:35 <steev> ah, and i'm not sure why but my initrd has to be gzip, not zstd but meh

14:35 <steev> that part is probably a debian thing

14:37 <ajhalaney[m]> Having to tell people to use that is just an extra quirk, so I'm glad to be rid of it bamse !

14:40 <bamse> ajhalaney[m]: right...we still need pd_ignore_unused...but it's getting there :)

14:57 <ajhalaney[m]> steev building now with that config + SECCOMP (hopefully that's all the extras I need). Is your normal config broken? iirc I saw you mention something to that end the other day about nvme not being found with your config. i gotta keep working on this x13s for the rest of the day haha but after my normal duties are over ill give that kernel a whirl.

14:57 <steev> ajhalaney[m]: that's what i mentioned the gzip thing for, idk why but with gzip it's fine, with zstd it was not fine

14:58 <steev> but that could be something in debian testing and not the kernel

15:00 <steev> and yeah, somewhere along the line i seem to have dropped the fedora stuff from the config, i'll try to find it in my patchsets and regrab it and do a new defconfig soon (sometime this weekend)

15:03 <steev> i also wanna try to fold the c630 stuff back in too, so i can stop using multiple kernels

15:06 <steev> bamse: do you know when pciids is gonna recognize whatever the pci is on the thinkpad? so it stops showing up in lspci as just Qualcomm Device 010e? (i have no idea where that info even comes from/goes to)

16:50 <bamse> steev: sorry, no idea

17:36 <ardb> steev: /usr/share/misc/pci.ids

17:36 <ardb> contributions welcome

17:41 <broonie> Data comes via https://pci-ids.ucw.cz/

18:40 <steev> the only issue with me contributing it, is that hinges on the knowledge of what 010e actually is... and i do not

19:44 <AlexMarty[m]> I havent been on in a while. is there any new cool updates? I am still on my kernel 5.19 install and was wondering if there was new drivers and functionality in newer kernels that I could install.

20:26 <ajhalaney[m]> steev -- thanks that branch worked w/ +CONFIG_SECCOMP for me. Didn't do anything magic, just let kernel-install do whatever initramfs generation dracut does for fedora I guess and I was off to the races. A nit picky request, but if you use b4 or something to apply patches from list can you start passing "-l/--add-link" to add the lore link? It would make figuring out which version of the patch I'm running simpler.. I struggle with

20:26 <ajhalaney[m]> confirming the version otherwise if the changes are subtle :P

20:27 <steev> ajhalaney[m]: AHA. yes i absolutely can!

20:27 <steev> i wasn't sure how the link was showing up on others and not mine, now that i know it's -l, i'll add that in :)

20:28 <ajhalaney[m]> thanks, you make my life way easier!

20:29 <steev> it will make mine easier too, i just didn't realize it was an option to pass, i thought that came from patchwork

20:30 <steev> and yes, i do use b4 to pull them from the list, aside from when i pull them from jhovold (or other misc trees)

20:32 <ajhalaney[m]> lol i just meant your branch maintainership in general! but that little bit will help even more

20:34 <steev> i just like testing things :) although i do need to send more t-bs

20:34 <steev> luckily my first todo list of the year is already down to only 75 more items to complete, so things should slow down a bit soon

20:36 <steev> most of it is "find out if this software is still being developed somewhere or not"

20:36 <ajhalaney[m]> I'm always a bit hesitant to add a RB or TB unless I'm really confident that I approached something from all angles, I'm a little looser with the TB's though

20:37 <steev> i don't send r-b because... i mostly look at the code and think, yeah sure, that looks right i guess? it's not like i have any idea what UCHE = 002309280 means

20:45 <steev> also a distinct lack of access to the schematics, and too lazy to google winstron(m?) whatever the code name was... i found it before when digging through the fcc database, but now i can't be bothered to find it

22:09 <amstan> winstron is a company i think

22:32 <broonie> Yes, they're a ODM

23:19 <steev> yeah, the board in the thinkpad is winstron

23:20 <steev> https://fcc.report/FCC-ID/PU5-TP00139A thats it

23:39 <steev> oh, right, now i remember what i wanted to test with the new stuff