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
<JesusChrist>
[JesusChrist] Corpus Loaded With 818 Messages
<JesusChrist>
[JesusChrist] Training Neural Network...
<JesusChrist>
[Chat] Sup
<JesusChrist>
[JesusChrist] Pretend its just to
<JesusChrist>
[JesusChrist] just full. wandering in it, New Server smh lying temporary
<JesusChrist>
[JesusChrist] well world from
JesusChrist has quit [Read error: Connection reset by peer]
JesusChrist has joined #aarch64-laptops
pabs has quit [Read error: No route to host]
<JesusChrist>
[JesusChrist] Corpus Loaded With 820 Messages
<JesusChrist>
[JesusChrist] Training Neural Network...
pabs has joined #aarch64-laptops
<JesusChrist>
[Chat] Set the send message time to 3-5 Minutes
<lynxy>
oh, shut up
chrisl has joined #aarch64-laptops
<Jasper[m]>
Somebody spamming again on one end?
<Jasper[m]>
It's not visible on Matrix
<travmurav[m]>
yeah the puppet was murdered but not for poor irc users xD
<Jasper[m]>
Oh no
JesusChrist has quit [autokilled: This host violated network policy. Contact support@oftc.net for further information and assistance. (2025-07-21 08:44:46)]
JesusChristLLM has joined #aarch64-laptops
JesusChristLLM has quit [autokilled: This host violated network policy. Contact support@oftc.net for further information and assistance. (2025-07-21 08:45:34)]
chrisl has quit [Ping timeout: 480 seconds]
<alexVinarskis[m]>
sign to migrate the group to Matrix? 👀
xorAxAx has left #aarch64-laptops [#aarch64-laptops]
PDiddyLLM has joined #aarch64-laptops
PDiddyLLM has quit [autokilled: channel. - Contact support@oftc.net for help. (2025-07-21 08:57:24)]
chrisl has joined #aarch64-laptops
PDiddyAI has joined #aarch64-laptops
PDiddyAI has quit [autokilled: channel. - Contact support@oftc.net for help. (2025-07-21 08:58:20)]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
martiert_work has quit [Quit: WeeChat 4.6.3]
martiert_work has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
OFTCLLM has joined #aarch64-laptops
OFTCLLM has quit [autokilled: channel. - Contact support@oftc.net for help. (2025-07-21 09:35:21)]
chrisl has quit [Ping timeout: 480 seconds]
<bryanodonoghue>
Hamoa - rc6 + CAMSS on Lenovo t14s, slim7x Dell Inspiron 14p and XPS - plus Iris encoder/decoder
<bryanodonoghue>
anthony25 h265 and vp9 should have encoder support on that branch now too
<valpackett>
previously it just didn't and the 4ghz state was just not used
<valpackett>
woah encoder!!
<bryanodonoghue>
valpackett I took the i2c address for the touchscreen from the schematics
<bryanodonoghue>
btw my touchscreen doesn't work so quite possible that is the wrong address
<bryanodonoghue>
there are a number of inaccuracies in the schematic I have
<bryanodonoghue>
probably an old version
<valpackett>
bryanodonoghue: ohhhh well try 0x09 and if it works submit a patch that moves the 0x09 one to the common dtsi
<valpackett>
i've had to spend some time reading the DSDT to figure it out
<bryanodonoghue>
tbh it probably is at the discovered address from the community
<valpackett>
it uses some weird method to dynamically assign 0x09 to the thing, lemme open that again
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<valpackett>
right, there's this "OperationRegion (DSMP, SystemMemory, 0xD5EF7000, 0x01A3)" and that's where the i2c addr and the compatible string come from for the touchscreen
<valpackett>
the _DSM for i2c-hid setup returns TPLH which comes from that region.. the _HID also is set from there by _INI
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hightower3 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<deathmist>
chrisl: any chance to fix the constant network reconnects? it's been happening for a few weeks at least
<valpackett>
uh oh, rebooted into new kernel to test multiple patches and both remoteprocs failed to load fw
<valpackett>
"Failed to load program segments: -22" hmm
vfdkjted has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hightower3 has quit [Ping timeout: 480 seconds]
<valpackett>
added an extra log print and it's the mdt header not being valid 0.o hmm did f2fs finally show a sign of the supposed infamous unreliability?
<valpackett>
and i even had archived the fw to potentially send to someone and it's the same sha as the unarchived one..
chrisl has joined #aarch64-laptops
<valpackett>
nope shasum is identical to the windows drive..
<valpackett>
and now testing two gpu power-saving improvements (IFPC + GMU-bandwidth-voting), and iris fixes/encoder..
<valpackett>
and the PCIe ASPM fix enables ASPM for the SSD as well since there's nothing to block it… uh oh (since at least with some 3rd party SSDs this causes random hangs)