robclark changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
djakov has quit [Remote host closed the connection]
djakov has joined #aarch64-laptops
<agl> steev & bamse: The following files have I installed:
<agl> binutils_2.42-4_arm64.deb
<agl> binutils-aarch64-linux-gnu_2.42-4_arm64.deb
<agl> binutils-arm-linux-gnueabihf_2.42-4_arm64.deb
<agl> binutils-common_2.42-4_arm64.deb
<agl> cpp-13_13.2.0-25_arm64.deb
<agl> cpp-13-aarch64-linux-gnu_13.2.0-25_arm64.deb
<agl> g++-13_13.2.0-25_arm64.deb
<agl> g++-13-aarch64-linux-gnu_13.2.0-25_arm64.deb
<agl> gcc-13_13.2.0-25_arm64.deb
<agl> gcc-13-aarch64-linux-gnu_13.2.0-25_arm64.deb
<agl> gcc-13-base_13.2.0-25_arm64.deb
<agl> libbinutils_2.42-4_arm64.deb
<agl> libbinutils-dbg_2.42-4_arm64.deb
<agl> libctf0_2.42-4_arm64.deb
<agl> libctf-nobfd0_2.42-4_arm64.deb
<agl> libgcc-13-dev_13.2.0-25_arm64.deb
<agl> libgprofng0_2.42-4_arm64.deb
<agl> libsframe1_2.42-4_arm64.deb
<agl> libstdc++-13-dev_13.2.0-25_arm64.deb
echanude has joined #aarch64-laptops
earl has joined #aarch64-laptops
earl has quit [Quit: Page closed]
<adamcstephens> agl: please use a paste site when more than a few lines
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
possiblemeatball has quit [Remote host closed the connection]
<krei-se> jenneron: i have a google-kevin and try to flash libreboot on it. wp screw is removed, added tape. flashrom still returns error MEMUNLOCK
Lucanis has quit [Ping timeout: 480 seconds]
Lucanis has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
rz has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
iivanov has quit []
iivanov has joined #aarch64-laptops
ungeskriptet has quit [Quit: Contact links: https://david-w.eu]
ungeskriptet has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
smpl has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
broonie has quit [Remote host closed the connection]
broonie has joined #aarch64-laptops
olv has quit [Ping timeout: 480 seconds]
jonmasters has quit [Ping timeout: 480 seconds]
sskras has quit [Ping timeout: 480 seconds]
lvrp16_ has quit [Ping timeout: 480 seconds]
steev has quit [Ping timeout: 480 seconds]
lool has quit [Ping timeout: 480 seconds]
pundir has quit [Ping timeout: 480 seconds]
ldts has quit [Ping timeout: 480 seconds]
jbowen has quit [Ping timeout: 480 seconds]
dgilmore has quit [Ping timeout: 480 seconds]
KhazAkar has quit [Ping timeout: 480 seconds]
CosmicPenguin has quit [Ping timeout: 480 seconds]
arnd has quit [Ping timeout: 480 seconds]
eric_engestrom has quit [Ping timeout: 480 seconds]
ardb has quit [Ping timeout: 480 seconds]
dianders has quit [Ping timeout: 480 seconds]
robher has quit [Ping timeout: 480 seconds]
_alice has quit [Ping timeout: 480 seconds]
ndec has quit [Ping timeout: 480 seconds]
alx___ has quit [Ping timeout: 480 seconds]
robclark has quit [Ping timeout: 480 seconds]
leiflindholm has quit [Ping timeout: 480 seconds]
jlinton has quit [Ping timeout: 480 seconds]
jhugo has quit [Ping timeout: 480 seconds]
broonie has quit [Ping timeout: 480 seconds]
jonmasters has joined #aarch64-laptops
CosmicPenguin has joined #aarch64-laptops
lvrp16_ has joined #aarch64-laptops
_alice has joined #aarch64-laptops
robclark has joined #aarch64-laptops
jhugo has joined #aarch64-laptops
eric_engestrom has joined #aarch64-laptops
olv has joined #aarch64-laptops
arnd has joined #aarch64-laptops
steev has joined #aarch64-laptops
ldts has joined #aarch64-laptops
broonie has joined #aarch64-laptops
KhazAkar has joined #aarch64-laptops
ndec has joined #aarch64-laptops
lool has joined #aarch64-laptops
dianders has joined #aarch64-laptops
jbowen has joined #aarch64-laptops
jlinton has joined #aarch64-laptops
ardb has joined #aarch64-laptops
pundir has joined #aarch64-laptops
alx___ has joined #aarch64-laptops
sskras has joined #aarch64-laptops
dgilmore has joined #aarch64-laptops
robher has joined #aarch64-laptops
leiflindholm has joined #aarch64-laptops
broonie has quit [Read error: Connection reset by peer]
broonie has joined #aarch64-laptops
broonie has quit [Read error: Connection reset by peer]
broonie has joined #aarch64-laptops
leiflindholm has quit [Ping timeout: 480 seconds]
leiflindholm has joined #aarch64-laptops
<jhovold> Here's an updated wip branch for the X13s:
<jhovold> Changes include:
<jhovold> - fix cpu thermal throttling stuck at low frequency again (6.10-rc1 regression)
<jhovold> - fix serial console hard lockup (6.10-rc1 regression)
<jhovold> - fix serial console soft lockups
<Jasper[m]> >again
<Jasper[m]> That sounds like some hair pulling annoyance
<kalebris> awesome, thanks jhovold and thanks to everyone working on the x13s linux thing
<adamcstephens> i see Microsoft is letting you customize up to 64GB memory on the surface laptop 7. $2399 for fully loaded 🙂
<kalebris> but only in black?
<adamcstephens> for 64GB apparently yes
<adamcstephens> and 32GB is black only. the pastels aren't really for me anyway
<kalebris> weird marketing, but ok :) but I suspect it would get less support than t14s g6 or if/when x13s gen2 comes
<adamcstephens> it's microsoft so that seems a safe assumption
<kalebris> I would have thought that with the whole WSL thing they kinda came around to open up a bit, but that would be in the opposite direction
minecrell75 has joined #aarch64-laptops
minecrell7 has quit []
minecrell754 has joined #aarch64-laptops
minecrell75 has quit [Ping timeout: 480 seconds]
possiblemeatball has joined #aarch64-laptops
possiblemeatball has quit [Remote host closed the connection]
possiblemeatball has joined #aarch64-laptops
alex_ has joined #aarch64-laptops
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #aarch64-laptops
<steev> jhovold: fwiw, i hadn't seen the new one, JensGlathe[m] did. not sure how he was hitting it but i wasn't
<jhovold> steev: it sounded on rafael like you could hit it after a suspend cycle (e.g. suspending while throttled perhaps?)
<steev> i've been stuck compiling big stuff (like gcc) so i haven't really had a chance to suspend lately :(
possiblemeatball has quit [Remote host closed the connection]
possiblemeatball has joined #aarch64-laptops
zdykstra has quit [Read error: No route to host]
zdykstra has joined #aarch64-laptops
alex_ has quit [Ping timeout: 480 seconds]
<JensGlathe[m]> I saw it after a build run, it cooled down, but frequency only increased to 940800 only. Even after a long time.
<JensGlathe[m]> With the patch it comes back when skin temp goes below 55°C (the threshold for "cooling"). This is what I would expect. It is the lowest alert point for this thermal zone, so no cooling required.
<JensGlathe[m]> s/only//
<jhovold> previous patch also worked here, so some additional condition was required to have it stuck again
<jhovold> rafel said something about after a suspend cycle
<jhovold> but nevermind, new fix also works
<JensGlathe[m]> could be that I also suspended (laptop was moving around), but anyway, it works now
hightower4 has joined #aarch64-laptops
hightower3 has quit [Ping timeout: 480 seconds]
srinik has quit [Ping timeout: 480 seconds]
<agl> steev: The following files have I downloaded from snapshot.d.o to have the gcc with which you can compile a kernel: https://paste.debian.net/hidden/d816e315/
<steev> agl: i already know them :) thank you though. it's a debian bug, and not something that i can or will do anything about
<agl> steev: At this moment i have compiled jhovold's 6.10.0-rc5. All works what i need.
<steev> sounds good :)
<agl> steev: It's 6 hours ago where jhovold push it on github.com.
<steev> yes, i'm aware, he announced it
<bluerise> anyone tried the GIC-ITS/MSI on X1E80100?
iivanov has quit [Quit: Leaving...]
<jenneron[m]> krei-se: not sure if i can help with that
<jenneron[m]> my kevin is on depthcharge
<jenneron[m]> decided to keep it, good enough for pmOS
<freekurt[m]> does anyone publish compiled x13s kernels to share with the class here, or is everyone supposed to do their own homework?
<JensGlathe[m]> Good Q. I could put up the debs on Google Drive at least
<abby> https://devspace.voidlinux.org/abby/x13s/ (.xbps is just .tar.zst)
<JensGlathe[m]> https://drive.google.com/drive/folders/1Lps5o3FXroAJFDiKj18vutJbC1uld49s?usp=sharing I would put these here. 6.9.6 with Ubuntu devkit_defconfig is uploaded.
<JensGlathe[m]> Same package can be installed on wdk and x13s
<JensGlathe[m]> el2 variant is also up
alfredo has joined #aarch64-laptops
<craftyguy> jhovold: thanks a lot for continuing to push updates to your x13s kernel :D
<craftyguy> I should really try raw, unmodified mainline on my x13s... I just don't have the time/patience right now to face "regressions" from unlanded patches :(
<craftyguy> is anyone here running an unpatched mainline kernel on their x13s?
<Jasper[m]> As unpatched as the Fedora distro kernel
<abby> i run mainline* 6.8
<abby> * one patch (in-kernel pd-mapper)
<craftyguy> is that in-kernel pd-mapper patch something that is already in >6.8?
<abby> no, it's unlanded
<craftyguy> there's some pd-mapper thing running in userspace on my system, does it require that patch in the kernel or is that completely separate?
* craftyguy doesn't know how pd-mapper works
<abby> this kernel patch replaces the userspace daemon
<craftyguy> ahhh cool
<abby> i only carry it because having some versions require the daemon and some not might cause issues
<craftyguy> ya that makes sense
lumag has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
<Jasper[m]> Ayyy @lumag is merging aarch64-laptops MR's. Thanks!
<lumag> Well, I just needed several ACPI dumps. Guess, what happened next?
<Jasper[m]> lumag: Hahaha well, I'm happy it happened
<craftyguy> so we'll no longer need to run the userspace pd-mapper daemon?
<abby> at some point
<kalebris> there's a mention of a binary cache for nixos in https://codeberg.org/adamcstephens/nixos-x13s but I'm either not using it right or just too impatient to wait for the cache to get populated
<craftyguy> abby: I mean, after you get a kernel with that patch in it (6.11?)
<abby> after that, yeah
<craftyguy> nice :D
<abby> no clue when it would land
<craftyguy> someone applied it somewhere (per that mailing list you linked), so I'm kinda assuming it would show up after the next merge window for 6.11. or it was merged directly into 6.10.r6(?) but maybe that's unlikely. /me just kinda making this up based on light observations
<abby> yeah, i have no clue where it ended up
possiblemeatball has quit [Remote host closed the connection]
possiblemeatball has joined #aarch64-laptops
<steev> abby: v9 is out iirc
<steev> oh you got it
<abby> :D
<steev> hadn't made my way down in scroll back
<steev> 6.11 or 6.12, i am not sure if the pre 6.11 window closes? bamse could answer since it's his tree
smpl has quit [Ping timeout: 480 seconds]
<bamse> mix-next-week
<bamse> mid*-next-week
<craftyguy> so this patch will be in 6.11 then?
<bamse> which is "this patch"?
<abby> pd-mapper
<bamse> ahh, yeah i merged it yesterday...so expect it to show up in v6.11
<bamse> hmm, might have been this morning...
<bamse> it's merged
<craftyguy> bamse: np thanks, I was just trying to understand the process :)
<bamse> craftyguy: process is that the patches has now landed on qcom/drivers-for-6.11 and remoteproc/rproc-next...and as we approach the merge window i will send a pull request to soc@vger.kernel.org whom will merge that into a soc branch and then as the merge window opens soc maintainers will send that to torvalds, and i will send the remoteproc piece to torvalds
<craftyguy> nice, thanks for the details! :D
<steev> it's a lot of moving parts, that end up in (hopefully) a working system
<bamse> craftyguy: the bigger picture is that we do "feature development" leading up to the merge window, maintainers integrate patches into feature branches, these are during the merge window perculated through pull requests up to torvalds whom after the two weeks creates the -rc1...then we're all expected to test this, report bugs/regressions etc, and by the 8th or so weekly such release all issues has been resolved and w
<craftyguy> ya I have no experience with it directly, and it's interesting to learn about. I've kinda inferred a lot of this just by casually watching from the sidelines :P