ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
<steev> 6.0-rc1 tagged, go go go
<steev> (not by me, linus)
<HdkR> \o/
<steev> god i hate how gnome will suspend even if something is running in a terminal
<bamse> i really miss the "hot corner" feature in osx...where i would have one corner be "lock now" and the other "disable sleep"
<bamse> i guess that some day it will have annoyed me enough to go figure out how this wayland thing actually works...
falk689 has quit [Remote host closed the connection]
<bamse> woho!
<steev> it's apparently already in arch
<steev> dunno if that translates to alarm too or not though
<bamse> we do rust, so worst case i'll just have to makepkg -A
<steev> i do all my rust stuff manually because debian packaging for it is a pita since you have to package the dependencies too
<bamse> sweet, got some battery stats on sc8180x primus as well now :)
<steev> nice!
<steev> flex too?
<steev> my f5 key is gonna break checking patchwork :P
<bamse> writing the code on the flex, so i don't want to test it
<bamse> how about i tell you when there's patches on the list for you to look at? ;)
<steev> heh
<steev> and johan is back from vacation too, so this is gonna be a good week i think
<bamse> isn't he out one more week?
<bamse> i might just have lost track of time though
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
<steev> Oh I thought it was only one but maybe it was two, maybe it has been two, I lose track of time too. My calendar and alarms only go so far
amstan has joined #aarch64-laptops
tinybronca[m] has joined #aarch64-laptops
Guest66 has joined #aarch64-laptops
psydroid[m] has joined #aarch64-laptops
travmurav[m] has joined #aarch64-laptops
clover[m] has joined #aarch64-laptops
Votes78 has quit [Killed (NickServ (Too many failed password attempts.))]
Votes78 has joined #aarch64-laptops
qzed has joined #aarch64-laptops
qzed is now known as Guest77
steevdave[m] has joined #aarch64-laptops
robertmader[m] has joined #aarch64-laptops
szclsya[m] has joined #aarch64-laptops
harvests[m] has joined #aarch64-laptops
harvestz[m] has joined #aarch64-laptops
AlexMarty[m] has joined #aarch64-laptops
davidebeatrici[m] has joined #aarch64-laptops
Guest66 is now known as go4godvin
abc123bac2[m] has joined #aarch64-laptops
Guest77 is now known as qzed
mahmoudajawad[m] has joined #aarch64-laptops
danielt has joined #aarch64-laptops
ungeskriptet[m] has joined #aarch64-laptops
jenneron[m] has joined #aarch64-laptops
Penguinpee_ has joined #aarch64-laptops
Penguinpee has quit [Ping timeout: 480 seconds]
Sobek[m] has joined #aarch64-laptops
Lucy[m] has joined #aarch64-laptops
<gwolf> steev: You are a good citizen!
<gwolf> (if you do your personal packaging following the Debian guidelines ;-) )
Penguinpee_ is now known as Penguinpee
<steev> when i package, i do :) if it's just a quick rust app... i usually just compile it to test it, if i keep using it, i try to get it into debian
<gwolf> Thanks for doing things right (-:
<steev> it's just better than filling up /usr/local or worse, spitting things all over the filesystem that aren't tracked
<gwolf> Right. Been there, done that... (-:
luxio_39[m] has joined #aarch64-laptops
cmeerw[m] has joined #aarch64-laptops
jelly has quit []
jelly has joined #aarch64-laptops
arisu has joined #aarch64-laptops
Lucanis has joined #aarch64-laptops
<steev> AlexMarty[m]: you have issues with wifi yeah?
<steev> connects and then disconnects and/or times out and/or connects but no traffic?
Erisa4 has joined #aarch64-laptops
Erisa4 is now known as Erisa
<bamse> steev: you don't happen to know what ballpark number we'd expect from POWER_SUPPLY_CURRENT_NOW?
<steev> 4642mAh
<steev> roughly
<steev> that's going based on a google of the L21M4P76 that showed up in HdKR's picture's of the battery
<steev> oh derp
<steev> i'm an idiot
<steev> it says 6400 on it
<bamse> so that would be a CHARGE_FULL_DESIGN of 6400000
<bamse> uAh
<steev> or 6210? i dunno what all the chinese stuff says, unfortunately. i learned russian and ukrainian, not chinese
<bamse> but the firmware tells me the current rate is -5560 something...
<bamse> i have full, min and current charge and get a plausible percentage out of that (in i3status)
<bamse> but the time-to-empty it calculates is just not right
<steev> when it comes to maths, i am absolutely positively, not your guy
<steev> amstan: ^^ thoughts
<steev> maybe we're dividing by the wrong amount? i think we were, roughly, with some-battery
<amstan> how big is your battery?
<amstan> well, so... if you want to do time math, you should use the W/Wh numbers
<amstan> A is more for load on your charger, Ah is... kinda useless since you have to do an integral across all voltages
<amstan> 5.5A sounds reasonable for a charging current for that kind of battery, ~1 hour to charge?
<bamse> amstan: it's negative, i.e. i'm on battery
<amstan> then it sounds like you'll get 1 hour battery life? seems rather high
<bamse> so i wouldn't be surprised to se 556mA
<amstan> or watch it be in W instead
<amstan> i have seen that before, where the battery stores both W and A in the same register and to switch between them there's another bit somewhere else
<bamse> yeah, that's seems to be how acpi does things
<amstan> then you get a multi master situation without locks, so you get one master setting it to A, then the other reads the register thinking it's reading W
<bamse> i suspect the problem might rather be that i don't know what the unit that POWER_SUPPLY_CURRENT_NOW is supposed to be
<bamse> because it's not described in the documentation afaict
<amstan> you could always modify your battery to allow you to measure current
<amstan> it's what we do on chromebooks sometime
<amstan> solder a current shunt in series with the battery, then you can measure both voltage and current(using that shunt)
<amstan> and you could correlate to your register reading
<bamse> my sc8180x runs off a power supply, so i can read the value from there...
<bamse> but what unit is POWER_SUPPLY_PROP_CURRENT_NOW supposed to report, uA?
<bamse> ahh, reading i3status source code indicates that i should report POWER_NOW, instead of CURRENT_NOW
<amstan> yep, i don't think window managers should use current for anything
<bamse> no, but it would be good if power_supply_class.rst told me that i'm wrong ;)
<bamse> and could it be that POWER_NOW should be a the absolute value of the change, and the sign is derrived from the status?
<bamse> hmm, seems i3status is as confused as i am about this abi
<qzed> bamse: AFAIK POWER_SUPPLY_PROP_CURRENT_NOW is uA and POWER_SUPPLY_PROP_POWER_NOW is uW, always positive
<qzed> at least that's what the ACPI spec + ACPI battery driver says
<qzed> or does
<qzed> what of those you should use depends on what the battery reports
<qzed> in case it supports both, I think power is preferred