<travmurav[m]>
ungeskriptet: I think you should add the ufs to the "parent" sc7180, I believe we already established that it works on 7c1
<travmurav[m]>
ungeskriptet: so, since sm7125 includes sc7180, adding the ufs to 7c would add it to both
junari_ has joined #linux-msm
junari has quit [Ping timeout: 480 seconds]
davidinux is now known as Guest2448
davidinux has joined #linux-msm
Guest2448 has quit [Ping timeout: 480 seconds]
matalama has quit [Read error: Connection reset by peer]
Paras has joined #linux-msm
Paras has left #linux-msm [Leaving]
<strongtz[m]>
Does anyone know what happened to SVE/SVE2 instructions on Qualcomm armv9 SoCs?
<strongtz[m]>
Is it disabled by firmware/hypervisor or what
<strongtz[m]>
Funnily enough, using clang to compile code with -march=native will produce program that will not run on "Qualcomm armv9"
<Adrian[m]1>
I'm not 100% sure. From my current knowledge SVE and SVE2 have buggy code generation in LLVM and therefore AOSP can't boot when compiled with SVE instructions (hence armv9-a+nosve works).
<strongtz[m]>
but it's really not there regardless of the compiler
<Adrian[m]1>
<strongtz[m]> "there's simply no SVE stated in..." <- you're right, no sve or sve2 on 8 gen 1 for me, huh
<Adrian[m]1>
I didn't even know that was possible since the ARMv9.0 spec should require SVE
<strongtz[m]>
yes, I think the firmware disabled all SVE instructions for some reason
<strongtz[m]>
the cpu hardware *should* support it
junari__ has joined #linux-msm
junari_ has quit [Ping timeout: 480 seconds]
Daaanct12 has joined #linux-msm
Daanct12 has quit [Ping timeout: 480 seconds]
Daaanct12 has quit [Ping timeout: 480 seconds]
junari_ has joined #linux-msm
junari__ has quit [Ping timeout: 480 seconds]
jhovold has quit [Quit: WeeChat 3.8]
junari has joined #linux-msm
junari_ has quit [Ping timeout: 480 seconds]
junari has quit [Ping timeout: 480 seconds]
jnn is now known as jn
<HappY[m]>
Dear all .. I am facing one issue with my device.. device randomly rebooting if I removed i2c, showing pmos logo , and then device rebooting.. and I don't have any recovery so I don't know how should I check ramoops log.. anyway to check log which causes this issue? It can be for Kernel panic or wrong kernel configuration?