alikateshethey[m] has quit [Server closed connection]
alikateshethey[m] has joined #linux-msm
fevv8[m] has quit [Server closed connection]
fevv8[m] has joined #linux-msm
jojo_autoboy[m] has quit [Server closed connection]
jojo_autoboy[m] has joined #linux-msm
z3ntu has quit [Server closed connection]
z3ntu has joined #linux-msm
<calebccff>
Any clues as to what might cause an SError kernel panic on sm6125 (derivative of sdm662)? It's caused by the UFS driver which we're trying to bring up, the only thing that I can think of would be the lack of smmu support on the platform
<calebccff>
but stuff like the sdhci probe just fine without it, so im not sure
Syboxez[m] has quit [Server closed connection]
Syboxez[m] has joined #linux-msm
mintphin has joined #linux-msm
undev[m] has quit [Server closed connection]
undev[m] has joined #linux-msm
vknecht[m] has quit [Server closed connection]
vknecht[m] has joined #linux-msm
wfranken[m] has quit [Server closed connection]
wfranken[m] has joined #linux-msm
hexdump0815 has joined #linux-msm
hexdump01 has quit [Ping timeout: 480 seconds]
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
DavidHeidelberg[m] has quit [Server closed connection]
DavidHeidelberg[m] has joined #linux-msm
MartinBotka[m] has quit [Server closed connection]
MartinBotka[m] has joined #linux-msm
mintphin has quit [Ping timeout: 480 seconds]
mintphin has joined #linux-msm
<lumag_>
calebccff: what kind of panic do you observe? Data abort?
<lumag_>
The trace should contain details, like the address, the kind of the error, etc
mintphin has quit [Ping timeout: 480 seconds]
<aka_[m]>
So, after week of pain yday i sent small patches and they turned out to be wrong formated.
<Mis012[m]>
Danct12: if you're interested, I also have other drivers that I didn't send out yet
<Danct12>
not now, i wanted to get fxtec pro1 to pmaports first before i can do anything :)
<Danct12>
calebccff, already know about the modem running, since i can see two sim slots has no sim card in there :D
<Mis012[m]>
calebccff: well, the sdm632 one should also come with ownership included, but that doesn't have SSC, so maybe it will only need edited devcfg
<Danct12>
so, any idea how i can get wifi to work? i remember got it working many months ago, but now i'm not sure if anything has changed since then
<calebccff>
am very curious about the new model
<Mis012[m]>
calebccff: it has cdsp though
<Mis012[m]>
so one can have fun with that
<calebccff>
sdm632 is sm6115 right?
* Mis012[m]
has no clue
<Mis012[m]>
I gave up after they stopped using msmXXXX :P
<calebccff>
Danct12: no clue im afraid, you should probably make sure your kernel is up to date and see if there are changes, msm8998 has seen a lot of noise over the last year or so
<Danct12>
weird, this is deathmist's kernel and i think he got wifi to work on his OP5
<calebccff>
you rebase fxtec stuff on top?
<calebccff>
probably missing some DT changes, like nodes which are now default disabled
<Mis012[m]>
Danct12: well, for the postmarketOS package, we might want to consider shipping the patched hypervisor
<Mis012[m]>
or more likely putting instructions in wiki
<Danct12>
calebccff, nothing much different, so /shrug
<Danct12>
the fxtec dts has a include to msm8998-mtp.dtsi, i don't see anything that's suggestive
<calebccff>
oof that's pretty cursed lol
<Mis012[m]>
yes
<Mis012[m]>
no clue how that got into mainline
<calebccff>
it did? damn
* calebccff
wants an 8998 fxtec now
<Mis012[m]>
can someone gift me an MTP so I can add stuff to the mtp dts that will break this atrocity? pls?
<Mis012[m]>
the fxtec is definitely not based on the MTP...
<calebccff>
is it based on qrd?
<Mis012[m]>
probably
<Mis012[m]>
what isn't :P
<calebccff>
op6 is actually based on mtp fwict
<Mis012[m]>
:doubt:
<calebccff>
go look at downstream!
<Mis012[m]>
naah
<calebccff>
other devices like the SHIFT6mq are based on QRD
<Mis012[m]>
pretty sure basing on MTP is incompatible with the linense for MTP design files
<Mis012[m]>
*license
<Mis012[m]>
they probably just copied mtp dts
<Mis012[m]>
and then used that as a base
<Mis012[m]>
I wouldn't expect the final design to resemble either with companies that like to NIH
<Danct12>
Mis012[m], hmm, do you have the noisy touch screen issue on your pro1?
<Mis012[m]>
everyone does
<Mis012[m]>
it's a hw problem
<Mis012[m]>
that they worked around with ugly hw hacks
<Mis012[m]>
*sw hacks
<Danct12>
which doesn't work too well for me :)
<Danct12>
or maybe even at all, since my touch screen is still jumpy as heck
<calebccff>
sw hacks missing in mainline?
<Mis012[m]>
sw hacks too ugly for mainline last time I heard
<Mis012[m]>
plus QUP noise rejection
<Danct12>
hmm, i thought qup noise rejection is the only sw hack?
<Mis012[m]>
don't think so
<Mis012[m]>
and it's not really sw
<Mis012[m]>
if they don't fix the hw for the sdm632 version I'll be pissed
<Mis012[m]>
Danct12: I guess you can solder some filtering capacitors yourself
<calebccff>
i guess it's their ODM to blame
<Mis012[m]>
kinda, but they should have complained