00:08 <steev> welp, there's 6.1

00:32 <HdkR> Any new ioctls, syscalls, or syscall features of note? :D

00:40 <steev> no gpu, but audio stuff will be there, if you can get it working

00:44 <steev> not sure how much time i'll have this week, mom and dad are gonna be in town

01:26 <clover[m]> Oh you have audio working steev?

01:35 <steev> only kinda sorta

01:35 <steev> i can get 1 play before the underflow happens

01:36 <steev> e.g. canberra-gtk-play -i message-new-instant will play 1 time, and then either start doing the static thing, or i can start to play it one more time and it will do the static in the middle of the play

01:51 <steev> pushed lenovo-x13s-6.1

01:51 <steev> it's pretty much rc8, but with now at 6.1

01:52 <steev> oh, i pulled in mani_s' llcc address stuff, but iirc, there's another revision needed

11:19 <xnox> steev: every grub vendor have their own dtb loading grub thingie, debian/ubuntu/suse/fedora/vanilla-upstream. I wish vanilla-upstream grub would accept one way of doing it by default, and all distros converbe on that. However, last time i pushed for that upstream linaro/arm out of all the things pushed back on that, in vafour of dtbloader which is a non-starter to ship

11:19 <xnox> custom per-distribution-kernel dtbs

11:51 <arnd_> HdkR: no new syscalls, a couple of netlink additions that should all be compatible, a few ioctls for obscure drivers

11:53 <arnd_> panfrost and vfio might be the most relevant drivers

11:53 <arnd_> HdkR: struct statx gained two new members

15:07 <HdkR> arnd_: That's good information, I wouldn't have looked at statx at all

15:07 <arnd_> HdkR: I just looked at all of 'git diff v6.0..v6.1 -- include/uapi arch/*/include/uapi/'

15:12 <HdkR> Good idea for next time

15:12 <HdkR> Now I'll have some ideas as to what to look for when adding support for the new kernel at least :D

15:20 <init> just saw the linus announcement on merge limitation for 6.2. looks like we'll be waiting for 6.3.

15:21 <init> (specifically for x13s owner) i should precise.

15:22 <steev> what merge limitation?

15:23 <init> https://www.theregister.com/2022/11/27/linus_torvalds_to_be_more/

15:23 <init> what wasn't in 6.2 pull request before the opening of the merge window won't get into it.

15:23 <jhovold> init: wait for what specifically?

15:23 <init> basically, any patch we haven't yet seen in next will be pushed to 6.3

15:24 <init> my interpretation might be wrong, but basically, our savenged patch set from next is pretty much the state we'll get with 6.2

15:24 <steev> we're only about 50 patches on top of next at this point

15:24 <init> scavenged.

15:24 <init> my interpretation could be definitely wrong

15:24 <steev> although, mine is currently broken

15:25 <jhovold> yes, that's how I read it too, but I mean, what specifically did you have in mind which isn't already in next?

15:26 <init> jhovold: a unrealistic expectation of working gpu.

15:26 <steev> oh that's more like 6.4

15:26 <jhovold> init: heh, yeah that's not happening for a while. :)

15:26 <init> yeah, good thing is. i'm not standing on the edge of my chair anyways. I'm more a passive bystander.

15:27 <init> if we get working sound, It'll be more than enough for now.

15:28 <steev> sound is really close, that should be 6.2 or 6.3; the issue is it's there, it's just not working correctly

15:28 <jhovold> steev: lol

15:28 <steev> it's in my 6.1 branch, and as long as you have the alsa-ucm-conf files...

15:28 <steev> jhovold: it is :(

15:28 <steev> i can get 1 sound, or about 40 seconds of audio from a video before there's some sorta underrun/underflow and then the audio stuff shits itself

15:29 <jhovold> steev: sure, there is a difference if it's merged we can fix it up. Just sounded funny to me: it's there, just not working

15:29 <jhovold> :)

15:30 <steev> :) i pushed it with 6.1 to hopefully get more people trying it and/or hacking on it

15:34 <jhovold> steev: oh, that's right, the dts bits are not actually in -next yet. I guess it is not really "there" yet then either. :)

16:04 <steev> yeah, there's a few bits outside next still :(

16:04 <steev> not a lot, like 50

16:05 <steev> maybe 40, i haven't counted the hacks yet

16:08 <steev> but with what i currently have, the sa8450p is killing the build because it includes sc8280xp and i haven't yet had a chance to track down what is causing it

16:10 <steev> the two i assumed it was, were not

16:12 <jhovold> steev: just run a bisect? -next is building an running just fine here, so it must be something in your tree

16:13 <steev> stop talking sense please

16:13 <jhovold> :)

16:34 <steev> may be screwed with c630 testing for a while, my cat seems to have developed an affinity for laying on it

16:34 <steev> not sure why as it doesn't get warm at all

16:36 <gwolf> Cats love elegancy 😉

18:18 <steev> bamse: do you have a cursor in sway on the thinkpad?

18:28 <selmer443[m]> Just a shot in the dark here but have you tried export WLR_NO_HARDWARE_CURSORS=1

18:29 <steev> not a shot in the dark, and i hadn't - was just about to ask robclark what i might be missing, as sway shows https://paste.debian.net/hidden/48b3dcd6

18:31 <bamse> steev: not without export WLR_NO_HARDWARE_CURSORS=1

18:34 <robclark> steev: no idea, maybe fallout from not having a gpu? It is apparently failing to pick a cursor format, whatever that means ;-)

18:34 <bamse> steev: do you have mesa installed?

18:35 <steev> i think so? gnome is normally used, and i'd expect mesa to be

18:35 <steev> but i am tired of multi monitor being broke on gnome so

18:35 <bamse> i thought you fixed that?

18:37 <steev> i fixed it for stable

18:38 <steev> testing and above are broken in a different way that's way above my paygrade

18:38 <steev> testing being gnome 43

18:39 <steev> i still think i'm missing *something* because what currently happens is, when it tries to fall back to xorg... you end up with a blinking cursor

18:46 <steev> but it happens on the c630 too, so

18:48 <steev> as for mesa, i only have libgbm1, libegl0-mesa0, libgl1-mesa-dri, libglapi-mesa and libglx-mesa installed, not sure if i need other packages, but those are what get pulled in by default

18:51 <HdkR> Sounds like enough

19:02 <bluerise> steev: do you have like a fancy git tree with the "for 6.4" stuff?

19:03 <steev> bluerise: it was more sarcasm since 6.2 isn't even started merging

19:03 <steev> just sayin, it ain't gonna be in 6.2, and 6.3 hasn't even started yet

19:03 <bluerise> Heh

19:03 <steev> i guess technically, 6.3 has started

19:04 <steev> since it's the stuff on the mailing lists that hasn't made it into next

19:04 <steev> but the gpu stuff.... i need to go back to, but there are things i want first

19:04 <bluerise> I have no clue about linux upstreaming mechanism, I only check https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git/refs/?h=for-next like every day

19:06 <steev> there's that... and a lot of trees that funnel into next/linux-next and that's the one that i pile patches from the mailing list onto

19:06 <steev> and sometimes, something random breaks, and i try to fix it up

19:06 <bluerise> sounds complicated

19:06 <steev> not complicated at all

19:07 <steev> i just worry about next... and then when i cant figure stuff out, i beg people like bamse and jhovold who actually know what they're doing, to fix it

22:20 <steev> of course, v2 of mani's stuff showed up today