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
weirdtreething has quit [Ping timeout: 480 seconds]
weirdtreething has joined #aarch64-laptops
tobhe has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
hipboi has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
hipboi is now known as Guest7485
hipboi has joined #aarch64-laptops
Guest7485 has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo has quit [Read error: Connection reset by peer]
<travmurav[m]> steev: v2 was silent for a month
<travmurav[m]> I see people discussing other things on the list so I have no idea if I just don't understand the process and it's "sliently accepted" or implicitly nacked/sent wrongly
<travmurav[m]> though v1 got comments immediately
<travmurav[m]> there is actually a "conficting" RFC to the same part of grub from canonical which got no replies too
<travmurav[m]> so who knows, maybe they just don't want to touch efi bits xD
<travmurav[m]> things from the list do seem to be selectively, silently applied sometimes tho so oh well...
<travmurav[m]> well I've tried to bump it, will see what happens https://lore.kernel.org/grub-devel/268ffc4b95fdc1e91bd3a275c2af394f@trvn.ru/
hipboi has quit [Quit: hipboi]
hipboi has joined #aarch64-laptops
srinik has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
<JensGlathe[m]> I would love to have this
<JensGlathe[m]> IMO the most logical way to get more versatile for odd(*) hardware enablements
<travmurav[m]> fwiw I think it wasn't tooooo hard for me to cross-compile latest grub to test that patch :^)
<steveej[m]> my x13s doesn't come back from sleep on 6.12-rc3. i don't use sleep mode often so i can't say which version introduced it. is this a known issue currently?
alfredo has quit [Quit: alfredo]
hightower3 has joined #aarch64-laptops
hightower3 has quit [Remote host closed the connection]
jhovold has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
hipboi has quit [Quit: hipboi]
<jhovold> steveej[m]: rc4 suspends just fine on the x13s here
<jhovold> if you're using an external display you may be hitting some of the old known bugs in the qualcomm display port driver
alfredo has quit [Ping timeout: 480 seconds]
<\[m]> how to delete this shit? we have OP?
<abby> eh?
<travmurav[m]> amstan: would you mind killing this on the matrix side?
<travmurav[m]> not sure if this would propagate to irc, I guess killing from the irc side would be better
<abby> we don't see anything on irc
<travmurav[m]> ah right oftc banned it I guess
<travmurav[m]> so then just amstan to kill here, and sad that bridge didn't propagate the ban via the portal
<travmurav[m]> (there is some mass crypto spam on matrix, with some user joining all big public rooms and repeating the message occasionally)
bumble[m] has joined #aarch64-laptops
<bumble[m]> yay
<steveej[m]> jhovold: i just updated to rc4 and seeing the same. probably something that i've done
<tobhe_> travmurav[m]: what would be the conflicting rfc? I can try to forward it to our grub people for review
<travmurav[m]> tobhe_: there is something about implementing boot shim support
<travmurav[m]> [PATCH v1 0/2] Draft: Support for shim loader protocol
<tobhe_> thx
<travmurav[m]> I appreciate the help too
<tobhe_> np, forwarded :)
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
hightower3 has joined #aarch64-laptops
jglathe_volterra has quit [Remote host closed the connection]
jglathe_volterra has joined #aarch64-laptops
whiskey9 has joined #aarch64-laptops
whiskey9 has quit [Remote host closed the connection]
<macc24> it's i2cdump of ec at address 0x5b which crashes it
<JensGlathe[m]> passive mode?
<JensGlathe[m]> I also see weird effects when scanning i2c
<macc24> JensGlathe[m]: i was literally unable to power on my laptop after that, keyboard froze up as well
<JensGlathe[m]> Living on the edge
<macc24> look, i WILL get that lid switch working
<macc24> i also have nothing better to do any my physics textbook scares me
<travmurav[m]> Sad iirc that device has no reset hole?
<macc24> yeah
<travmurav[m]> Unfortunate
<travmurav[m]> But poking random i2c often hangs the ec firmware, I had the same on mine
<travmurav[m]> But have the reset hole at least :p
tinako89 has joined #aarch64-laptops
<tinako89> Hi
<macc24> o/
tinako89 has left #aarch64-laptops [Leaving]
jhovold has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<kuruczgy[m]> (It does have a "novo button" hole, not sure if it resets the EC though)