<konradybcio>
hopefully not another housewarmer :)
<vknecht[m]>
what's its real name ? 8gen1 seems to be sm8450 and 8+gen1 == sm8475 are the latest according to wikipedia list of qcom SoCs
<vknecht[m]>
other than that, commercial hype feels depressing, like, it was the same kind of press releases 8 years ago (and more) and where are those products, how are they supported now ?
<vknecht[m]>
so... trm, hrd, docs, schematics, or it didn't happen :-)
cxl000 has quit [Quit: Leaving]
<vknecht[m]>
(right msm8916 is the exception)
<ndec>
vknecht[m]: it's next gen soc, so name is sm8550
Souradeep has quit [Quit: Ping timeout (120 seconds)]
rnayak has quit [Quit: Ping timeout (120 seconds)]
rnayak has joined #linux-msm
Souradeep has joined #linux-msm
Daanct12 has joined #linux-msm
Daaanct12 has joined #linux-msm
Daanct12 has quit [Quit: Quitting]
Daaanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-msm
Daanct12 has quit []
Daanct12 has joined #linux-msm
cxl000 has joined #linux-msm
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-msm
Daanct12 has quit [Ping timeout: 480 seconds]
Daanct12 has joined #linux-msm
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
jhovold has joined #linux-msm
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-msm
Daanct12 has quit [Read error: Connection reset by peer]
Daanct12 has joined #linux-msm
<z3ntu>
sm8450 is already a year old? wow..
<z3ntu>
So then are the sm8550 patches flying in? ;)
<lumag>
konradybcio, regarding smmu. I don't have a clear picture of -smmu-v2 entries. If I remember correctly some of them are more broken ('secured') than others are.
<konradybcio>
yes, that's the case
<konradybcio>
630 vs 8996/8 vs 845 (vs i want to add 6350)
<lumag>
For qcom-smmu-500 the picture is more clear, all of them appear to be the same
<lumag>
So, I'd say, we have to live with per-SoC entries for -v2 entries, while all qcom 500 entries can be handled by the generic compat.
<lumag>
Unless the platform has some peculiarities (e.g. sdm845)
<konradybcio>
okay, sounds good
<aka_[m]>
konradybcio: any idea if latest rc work now?
<aka_[m]>
or next
<konradybcio>
idk i have next 20221115 and Brian's patch picked into my tree
<aka_[m]>
i should rebase dpu patches and compile test them
<aka_[m]>
but tree was quite broken
<aka_[m]>
so "day one" support mean 5.15 msm fork will come within days?
<aka_[m]>
yes we are here about mainline, but i seen some notes about qcom doing 5.15 ds quite fancy
<aka_[m]>
including support for Khaje
<konradybcio>
last time xiaomi released 5.10 faster than caf iirc
pespin_ has joined #linux-msm
pespin has quit [Ping timeout: 480 seconds]
pevik has joined #linux-msm
pevik has quit [Quit: Lost terminal]
<aka_[m]>
Flagships Inc
<aka_[m]>
Right
<aka_[m]>
Shouldn't qcom release caf trees day one
<konradybcio>
well gpl requires they do once you receive the compiled copy
pespin_ has quit [Remote host closed the connection]