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
hightower4 has joined #aarch64-laptops
hightower3 has quit [Ping timeout: 480 seconds]
neggles has quit [Ping timeout: 480 seconds]
neggles has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
neggles has quit [Ping timeout: 480 seconds]
neggles has joined #aarch64-laptops
Lucanis has quit [Quit: Leaving]
Lucanis has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
todi1 has quit [Ping timeout: 480 seconds]
todi has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
todi1 has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
todi1 has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
martiert has quit [Quit: WeeChat 4.0.2]
alfredo has joined #aarch64-laptops
martiert has joined #aarch64-laptops
<jhovold> jlinton: that too, handover still isn't seamless but now the edp phy is no longer powered off and on again during boot
todi has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
hightower4 has quit [Ping timeout: 480 seconds]
todi has joined #aarch64-laptops
todi has quit [Read error: Connection reset by peer]
todi has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
Stirl[m] has quit [Quit: Client limit exceeded: 20000]
hightower2 has joined #aarch64-laptops
todi has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
todi1 has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
todi1 has quit [Ping timeout: 480 seconds]
<qzed> jhovold: before I start bothering people on the mailing list
<qzed> it looks like https://github.com/torvalds/linux/commit/84a9582fd203063cd4d301204971ff2cd8327f1a breaks all UART transfers when suspending
<qzed> is there a way around that?
<qzed> or rather: breaks when the UART port has been runtime-suspended when entering system suspend
<qzed> but obviously that's not great
hightower2 has quit [Read error: Connection reset by peer]
hightower2 has joined #aarch64-laptops
<jhovold> qzed: not surprised to hear that unfortunately
<jhovold> i saw your question regarding serdev here the other week but forgot the reply
<jhovold> my suspicion was that it could be related to this
<jhovold> i didn't really have time to review that work expect for looking at some of the early revisions
<jhovold> but that series has caused quite an impressive list of issues already
<jhovold> i suggest you bring it up on the list, sounds like this broke a valid use case
<qzed> okay, will do that. thanks!
alfredo has quit [Quit: alfredo]
hightower2 has quit [Read error: Connection reset by peer]
hightower2 has joined #aarch64-laptops
hightower2 has quit [Read error: Connection reset by peer]
hightower2 has joined #aarch64-laptops
hightower2 has quit [Read error: Connection reset by peer]
hightower2 has joined #aarch64-laptops
Utkojhamela has joined #aarch64-laptops
mcbridematt has joined #aarch64-laptops
hightower2 has quit [Read error: Connection reset by peer]
Utkojhamela has quit [Read error: Connection reset by peer]
hightower2 has joined #aarch64-laptops
hightower2 has quit [Read error: Connection reset by peer]
<_[m]1> <Jasper[m]> "@[(⊙_◎)] are you still having..." <- I've been out of the house last weeks, probably at least another week
<Jasper[m]> _[m]1: Aha, well... I've been told getting out the house is sort of important
alfredo has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
hightower2 has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
heapify has joined #aarch64-laptops
heapify has quit []
iivanov has quit [Quit: Leaving]
alfredo has joined #aarch64-laptops
<clover[m]> steev: new rc soon?
<steev> last night
<steev> it's just what i already had pushed against johan's latest
<clover[m]> ah i see
<steev> i didn't announce it because i forgot :)
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
rmsilva has quit [Ping timeout: 480 seconds]
<clover[m]> oh ok np
alfredo1 has joined #aarch64-laptops
<push> this morning my x13s was dead even though it was on the charger, is it possible for pd-mapper or whatever to crash and disable charging?
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
<clover[m]> pd-mapper doesn't enable or disable charging, i think it just allows userspace to see the charge level. so i dont think so. did you make sure you were using the port furthest from you!
<steev> i believe if pd-mapper isn't running it *doesn't* charge it, it simply maintains power
<steev> but unplugging it and plugging it back in should start charging it when it's "dead"
alfredo has quit [Quit: alfredo]
<_[m]1> <Jasper[m]> "Aha, well... I've been told..." <- I almost bought a second laptop here, must contain myself 😉 that samsung looks nice but lol then I'll just have 2 mm
<_[m]1> the port closest to you has no power line?
<push> I had to check, at least under windows, both ports will charge it
<steev> both will in linux as well, but the one closest to screen is marked as the power port in pics
<konradybcio> push the charging sometimes hangs for no good reason
<konradybcio> replugging the cable always works for me
<konradybcio> at the same time, it seems to maintain the % it got stuck at
<steev> maybe the endianness fix will help?
hightower2 has quit [Remote host closed the connection]
hightower2 has joined #aarch64-laptops