19:12 <aka_[m]> lumag: how linaro/msm sheet work?

19:13 <aka_[m]> i see msm8939 says gcc is 5.12 but based on github it says 5.8 was tag with it

19:13 <aka_[m]> and its part of 5.10 lts

19:13 <konradybcio> aka_ it's purely manual

19:14 <aka_[m]> ?

19:14 <aka_[m]> i mean i know its parsed out of .md

19:14 <konradybcio> it's filled out by hand

19:14 <aka_[m]> which is filled by hand

19:14 <konradybcio> there's json or something

19:15 <aka_[m]> so entry data is wrong?

19:15 <konradybcio> very possibly

19:18 <lumag> aka_[m], patches and fixes are really appreciated

19:18 <aka_[m]> lumag: and its bit confusing

19:18 <aka_[m]> lets say cpufreq

19:19 <aka_[m]> do i assume if we use 8916 apcs driver we mention 8916 kernel version?

19:19 <lumag> huh?

19:19 <aka_[m]> like chart have parts of soc

19:20 <aka_[m]> and we mention when "support" for part was added?

19:20 <konradybcio> it's "what's the first kernel where the feature visibly works"

19:20 <aka_[m]> not when stuff was wired and working

19:20 <aka_[m]> konradybcio: so for most parts its time when first dts is added

19:20 <lumag> I was usually selecting 'wired and works', which means both the driver and dts

19:20 <konradybcio> exactly

19:20 <lumag> other devs might have other opinion.

19:20 <konradybcio> unless the dts was flawed from the start or something

19:20 <aka_[m]> so we do when stuff was wired

19:20 <konradybcio> which happens every nwo and then

19:21 <konradybcio> e.g. when 8550? was introduced, an abi-breaking rework of llcc happened and llcc never worked until i noticed some time later

19:21 <aka_[m]> well i guess starting with "its wired and works" is much easier than finding when exactly support for regulator setup for specific soc was added

21:56 <z3ntu> bamse: gentle ping about my tqftpserv patches https://github.com/andersson/tqftpserv/pull/13

22:11 <phh> z3ntu: Hello. Since you mention mobile data work, dual data connectivity work as well? (internet + ims, or even + second's sim ims?) calls are working? including volte? (i'm curious if a floss software volte stack could be useful there)

22:13 <z3ntu> phh: DSDS (dual sim dual standby) is apparently not supported in modemmanager yet, IMS neither. 2G/3G calls are working (without audio right now because device support is missing), mobile data also

22:15 <phh> k so software volte wouldn't fix calls, they are already working (though just less ideally). thanks. my question with dual data connectivity wasn't dsds though, it's having internet data connectivity APN and ims data connectivity APN of the same sim up

22:15 <phh> (I'm really just speaking of ims data connectivity, not IMS features at all)

22:17 <mgonzalez> Ayo, does anyone know if there's a dedicated channel for ath10k (the one that's in the msm8998) ?

22:19 <mgonzalez> #linux-wireless on libera sounds like a good bet

22:20 <z3ntu> phh: I think Dylan Van Assche might have an idea, I haven't looked into IMS at all yet

22:22 <phh> roger that, thanks. For the context, I'm working on a floss software VoLTE+VoWifi implementation for Android (first because some devices don't have VoLTE in modem, then because VoWifi, then features/carriers support, then for security), that's not really applicable to mainline/Linux, but I've dug enough to help people who would want to work on that on gnu/linux (there is doubango as a C ims stack that should be possible to integrate)

22:32 <z3ntu> sounds great!