Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-msm
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-msm
Daaanct12 has joined #linux-msm
Daanct12 has quit [Ping timeout: 480 seconds]
ivoszbg[m] has joined #linux-msm
Daaanct12 has quit [Quit: Leaving]
Guest66 is now known as go4godvin
JoelSelvaraj[m] has joined #linux-msm
jnn has joined #linux-msm
jn has quit [Ping timeout: 480 seconds]
<mal>
has anyone had issues with iommu on 5.19? I had to patch iommu.c to get it to work again, my patched qcom_iommu used to work in 5.18 but unrelated changes in 5.19 in this part https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/iommu/iommu.c#n2092 causes issues, I have to add checks that default_domain and blocking_domain are valid before comparing those to domain value
ichernev[m] has joined #linux-msm
z3ntu has joined #linux-msm
ungeskriptet[m] has joined #linux-msm
konradybcio has joined #linux-msm
RayyanAnsari[m] has joined #linux-msm
mint[m] has joined #linux-msm
<lumag>
ichernev[m], aka_[m]: yes, a quirk is fine for now. However I'd prefer if we can sort this out properly. I mean, tested on 660, etc.
<lumag>
Regarding the downstream. I trust it up to some degree. It is not uncommon that they add code that works only for the models supported by this particular kernel set.
vknecht[m] has joined #linux-msm
flamingradian[m] has joined #linux-msm
pevik_ has quit [Ping timeout: 480 seconds]
pevik_ has joined #linux-msm
abhinav__2 is now known as abhinav__
IvanBelokobylskiy[m] has joined #linux-msm
cmeerw[m] has joined #linux-msm
Tooniis[m] has joined #linux-msm
sepkov[m] has joined #linux-msm
Syboxez[m] has joined #linux-msm
Newbyte has joined #linux-msm
FieryFlames[m] has joined #linux-msm
<aka_[m]>
<mal> "has anyone had issues with iommu..." <- maybe this is related?