ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
<steev>
szclsya[m]: hm, you can try backing out d6a0dc9d6f28ce9829eaed1d7e17f8b6159fff59
<steev>
it's a dtsi change, so you should be able to make dtbs, then point at the newly built dtb file instead of installing the full kernel to test it
<steev>
but yeah, looks like thats the one
<steev>
that wasn't actually supposed to go in, sorry about that :(
<steev>
szclsya[m]: should be a new tag (sorry!)
<szclsya[m]>
hmm I can't find this tag on github, but I saw you just redone 5.19.0 branch, so I guess it's good now?
<szclsya[m]>
also no worries, I'd expect some small annoyance when using such bleeding edge branch :)
<steev>
bleeding edge will be when -next stuff starts rolling in :D
<steev>
i haven't wanted to deal with the pcie patches in it, so i'm still doing 20220722 here :(
<szclsya[m]>
what's still missing in -next now? just the pcie patchset?
<steev>
quite a bit
<steev>
in actual next, the biggest thing missing is mdss
<szclsya[m]>
ah...
<szclsya[m]>
so we won't even get a framebuffer
<steev>
we can patch it, and we have the patches, and they'll be applied, they just, haven't made it yet and won't make the merge window for 5.20, or 6.0, whatever linus decides to number it
<steev>
but between 22 and 28, a bunch of pcie changes happened
<steev>
and it's about to be release time so i'm gonna be busy the next couple weeks and don't wanna poke at it, but eventually a new -next branch will show p
<steev>
i'm also gonna try and combine what i have for the c630, flex5g, and thinkpad together for the 5.19 branch
<steev>
it's currently 150 patches for the thinkpad, and 199 for the c630/flex5g (and there's some... but probably not all the thinkpad stuff in there) so i just need to see what is what
<steev>
i also wanna try to git annotate to point out where the patchsets come from
<steev>
jstultz used to do that with his kernel tree, and i always found it helpful to know what i could dismiss and what i could try to play with
<szclsya[m]>
nice, thanks for your work
<szclsya[m]>
ah I see some GPU bring up in the next branch. does it work?
<steev>
or if i knew how the cros tooling stuff worked, where it adds stuff like chromium: or fromlist: or whatever (or maybe whoever is doing it amends the commits)
<steev>
no
<steev>
you just end up with a black screen (it's booted) and a bunch of smmu faults currently
<steev>
you can ssh in though
<steev>
oh
<steev>
you know what, i might have missed the gpu mem reserving
<szclsya[m]>
that would explain the mmu errors!
<steev>
the other option is that the firmware we're loading for the a690 isn't actually correct
<steev>
which is entirely possible
<steev>
suppose i can give it a whirl, and then spin it back to the a660 ones that are in linux-firmware just to see
<steev>
robclark: 0x1ff is supposed to give me *all* drm messages no?
srinik has quit [Killed (NickServ (Too many failed password attempts.))]
srinik has joined #aarch64-laptops
<robclark>
steev: drm.debug=0x1ff should get you a lot of traces.. but might also need loglevel=10 or so?.. and fwiw there is a fromupstream.py script that does the UPSTREAM/FROMGIT/FROMLIST formatting
<steev>
hm, or not, i do have debug stuff enabled, but maybe not enough
<steev>
robclark: even with loglevel 10, it looks exactly like my previous paste
<robclark>
not detecting a connected display, maybe?
klardotsh has quit [Ping timeout: 480 seconds]
<steev>
definitely possible
<clover[m]>
Leo Shen: I see other arch projects separating rc kernels and release kernels as two different packages, maybe due to the roadblock we encountered yesterday. Here is a PR to add rc kernel pkgbuild. You might have to remove existing kernel packages from your repo and re-build and add both. https://github.com/szclsya/x13s-alarm/pull/2
<szclsya[m]>
eh the current kernel is only intended for dev works anyway... I don't see a point to separate a dev kernel