ChanServ 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
kalebris_ has joined #aarch64-laptops
kalebris has quit [Ping timeout: 480 seconds]
kalebris_ is now known as kalebris
hexdump02 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
neggles has quit [Remote host closed the connection]
neggles has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
witcher01 has joined #aarch64-laptops
jglathe_t14s has joined #aarch64-laptops
<steev> tobhe[m]: does the ubuntu kernel have v3 of the ec driver in it?
jglathe_volterra has quit [Remote host closed the connection]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
ungeskriptet has quit [Remote host closed the connection]
SpieringsAE has joined #aarch64-laptops
ungeskriptet has joined #aarch64-laptops
<SpieringsAE> deathmist: yes I do read the logs when I get back online :) I don't recall having issues on plasma wayland
vfdkjted has quit [Ping timeout: 480 seconds]
<SpieringsAE> it has been a while since I had the hdmi connected maybe some new plasma bug, I've been getting an odd bug on my work pc lately where one display stays black for quite a while
<SpieringsAE> cursor is visible on it though during that time, so it is properly connected
vfdkjted has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
shoragan has joined #aarch64-laptops
Gnappo85 has joined #aarch64-laptops
<deathmist> SpieringsAE: turns out it was some local crap for a pre-release kwin, so it may or may not break in 6.5, I should check if mater is ok ig later..
<deathmist> thanks
<SpieringsAE> np
Gnappo85 has quit []
jhovold has joined #aarch64-laptops
mosasaur has joined #aarch64-laptops
FANTOM has quit [Ping timeout: 480 seconds]
FANTOM has joined #aarch64-laptops
<tobhe[m]> steev: haven't added the ec driver yet
fantom_ has joined #aarch64-laptops
FANTOM has quit [Ping timeout: 480 seconds]
ravikant_ has quit [Ping timeout: 480 seconds]
Gnappo85 has joined #aarch64-laptops
Gnappo85 has quit [Quit: Textual IRC Client: www.textualapp.com]
ravikant_ has joined #aarch64-laptops
paulk-bis has joined #aarch64-laptops
paulk has quit [Read error: Connection reset by peer]
<anthony25> akhilpo: I played a bit with the scheduler and idle latency (with pm_qos_resume_latency_us), and I realized it helped a lot on the animations stutter on hyprland, and I think I figured out a better scenario to replicate the problem
<anthony25> I tried scx scheds, and I realized that they lowered the stutters
<anthony25> but the power consumption pretty much doubled on most of them, that or it was really laggy
<anthony25> I understood that it was linked to the idle QoS latency, that some scheds set
<anthony25> so I tried to set it manually, and setting pm_qos_resume_latency_us to lower than 1000 helps (but it makes it harder for the cores to idle, if I understand correctly)
<anthony25> so what I found to work the best, is using scx_lavd in balance mode, and setting a core preference list to 1 core, and lowering the pm_qos_resume_latency_us for this core
<anthony25> sorry: I meant setting a core preference to: "8,9-11,4-7,0-3", so it'll prefer core 8, and I bias the idle time for it
<anthony25> also, I realized that the stutters happen only when there is a "heavy" app to render
<anthony25> and they seem to happen only for workspace switching
<anthony25> so it happens when I have firefox on one workspace, thunderbird on another one, and switching between the 2 creates some CPU load by the thunderbird or firefox process
<anthony25> I'll try to replicate that on gnome, but it didn't seem to happen last time I tried
<anthony25> could it be that the slim 7x set a high qos idle latency?
<anthony25> also, using lavd (with the settings I listed above) doesn't increase the power consumption, it seems to be the same or lower than with EEVDF
paulk-bis has quit []
paulk has joined #aarch64-laptops
<anthony25> <anthony25> could it be that the slim 7x set a high qos idle latency? <<< I mean, it doesn't seem to be the only problem, I still have way less stutter using lavd than with EEVDF and a low qos idle latency
<anthony25> and it's interesting with thunderbird/firefox, if I switch to an empty tab, the animations don't stutter
ema has quit [Quit: reboot]
ema has joined #aarch64-laptops
hightower3 has joined #aarch64-laptops
<robclark> hmm, /sys/devices/system/cpu/cpu*/power/pm_qos_resume_latency_us is all 0 for me ... idk if something in userspace/gnome is adjusting those?
<anthony25> robclark: by default, for me too, but 0 is using the default platform value (I don't know what sets it?)
<robclark> hmm, ok.. me neither..
hightower2 has quit [Ping timeout: 480 seconds]
<\[m]> tobhe https://github.com/WOA-Project/Qualcomm-Reference-Drivers can get from here? not sure
programmerin-wonderland has joined #aarch64-laptops
<programmerin-wonderland> Hey super sorry but can someone with working bluetooth on a snapdragon x1e80100 laptop give me their full dmesg
<programmerin-wonderland> trying to cross reference with a working example
<programmerin-wonderland> I'm realizing nothing in my laptop ever seems to call https://github.com/torvalds/linux/blob/76eeb9b8de9880ca38696b2fb56ac45ac0a25c6c/drivers/bluetooth/btqca.c so I'm trying to see whats the last consistent bluetooth log I have with a working example
krei-se has quit [Quit: ZNC 1.9.1 - https://znc.in]
jglathe_t14s has quit [Remote host closed the connection]
jglathe_t14s has joined #aarch64-laptops
krei-se has joined #aarch64-laptops
<anthony25> I can send that to you by this evening (I have a slim 7x, it has a wcn7850)
<programmerin-wonderland> would be amazing, thanks!
<programmerin-wonderland> I think its possible I may be causing my own struggles and simply forgot to compile in BT_HCIUART_QCA
<programmerin-wonderland> if thats the case, wow, embarassing for me but the fix should be easy
<programmerin-wonderland> CONFIG_BT_HCIUART_QCA=y nope def did that
<programmerin-wonderland> 👍
jglathe_t14s has quit [Ping timeout: 480 seconds]
jglathe_t14s has joined #aarch64-laptops
programmerin-wonderland has quit [Read error: Connection reset by peer]
<JensGlathe[m]> Should be implicit, but not sure if this is an edge case with Surface
SpieringsAE has quit [Quit: SpieringsAE]
<anthony25> (they left, "connection reset")
Gnappo85 has joined #aarch64-laptops
<\[m]> @programmerin-wonderland https://hastebin.ianhon.com/7eb5
<\[m]> how to enable touchscreen for t14s?
programmerin-wonderland has joined #aarch64-laptops
programmerin-wonderland has quit [Quit: programmerin-wonderland]
mosasaur has quit [Quit: Leaving]
<JensGlathe[m]> should be in the dt, except you have the second source one
<JensGlathe[m]> /* TODO: second-sourced touchscreen @ 0x41 */
<\[m]> oh
<\[m]> I don't have this comment in my dts
* travmurav[m] gets ready to advertize dtbloader's code based fixup features where he already has code to get t14ss touchscreen vid/pid from frimware mailbox
jhovold has quit [Quit: WeeChat 4.5.2]
ravikant_ has quit [Ping timeout: 480 seconds]
jglathe_ has joined #aarch64-laptops
jglathe_t14s has quit [Ping timeout: 480 seconds]
jglathe_ has quit [Remote host closed the connection]
jglathe_t14s has joined #aarch64-laptops
jglathe_t14s has quit [Remote host closed the connection]
jglathe_t14s has joined #aarch64-laptops
jglathe_t14s has quit [Remote host closed the connection]
jglathe_t14s has joined #aarch64-laptops
<JensGlathe[m]> Hmm not available?
<maz> definitely available here for £480... Guess I need to click the button...
<JensGlathe[m]> aaargh why
<JensGlathe[m]> you do have a devkit no
<JensGlathe[m]> its €800 or so here
<maz> I do have a devkit. but that's to replace my home "pile everything that runs" box.
<JensGlathe[m]> And I had it in the cart maybe 4 times or so
<JensGlathe[m]> That's a good excuse tbh
Gnappo1985 has joined #aarch64-laptops
<rfs613> kinda pricy considering its missing screen, keyboard and battery ;-)
<JensGlathe[m]> it has sort of decent cooling
Gnappo1985 has quit []
<valpackett> wait for ebay refurbished (?)
<JensGlathe[m]> no way
<JensGlathe[m]> Waiting for black week
<valpackett> i guess mini pcs don't get returned as much as laptops anyway
<maz> "Oops! Error happens here: query order failed"
<maz> order went through though.
<maz> supposed to ship in 6/9 days.
<robclark> let us know how it is.. a nuc type form factor would probably be more useful for CI farm..
ravikant_ has joined #aarch64-laptops
<akhilpo> robclark: Probably the 0 values you see for CPU nodes could be due to the hardened CPU dcvs. I think Oryon cores have hw implementation of dcvs.
<akhilpo> Yeah, if cpu idling is very aggressive, that can cause issues.
<robclark> hmm, could be.. I've not looked closely at cpufreq on these things
ravikant_ has quit []
<akhilpo> konradybcio: I suppose you might have better grip on this topic
<ellyq> tobhe[m]: looks like i forgot to add this channel to my quassel client - no, none of my chromebooks run CrOS :D
<ellyq> as soon as i finish grabbing logs for development, i nuke it and replace it with linux
ellyqw has joined #aarch64-laptops
jglathe_t14s has quit [Remote host closed the connection]
<tobhe_> heh I almost expected that :)
tobhe_ is now known as tobhe
pbrobinson has quit [Ping timeout: 480 seconds]
pbrobinson has joined #aarch64-laptops
sgerhold has quit [Quit: Ping timeout (120 seconds)]
minecrell has quit [Quit: Ping timeout (120 seconds)]
minecrell has joined #aarch64-laptops
sgerhold has joined #aarch64-laptops
hexa- has quit [Quit: Disconnected]
hexa- has joined #aarch64-laptops
mbuhl has quit [Remote host closed the connection]
mbuhl has joined #aarch64-laptops
<clover[m]> Is this room dead?
<dgilmore> nah