R!ck
前往频道在 Telegram
"...the world is full of idiots that don’t understand what’s important." -RS ¡ǝɯ dlǝɥ ǝsɐǝld 'uᴉɐd ʇɐǝɹƃ uᴉ ɯɐ ᴉ
显示更多307
订阅者
无数据24 小时
无数据7 天
无数据30 天
帖子存档
Tutor matiin aod woy Mati total tapi nyala gimana sih https://t.me/NusantaraOT/22289
gw gatau, gw ga buka link di tweet reply nya https://twitter.com/thesheeppppp/status/1315989614486667264?s=19
Starting with the 845 generation, Qualcomm introduced a hardware clock manager dubbed OSM (Operating State Manager). Early during the SoC's development, the kernel was responsible for initializing OSM and the in-kernel OSM driver was much more sophisticated as it held the sole responsibility of configuring OSM for all the CPUs as well as the shared L3 system cache.
In July of 2017, Qualcomm decided to prevent the kernel from modifying these values and designated OSM initialization to the TrustZone secure world instead. Here's the kernel commit marking the change. Reverting that commit will NOT unlock it as the change was made to the secure world's firmware. The commit mentions being locked out from the HLOS, which stands for High-Level OS — Linux in this case.
After that change, the kernel simply reads the frequency table out of the few OSM registers it is allowed to access and exposes them to the clk framework as well as cpufreq for the rest of the kernel to use. To initiate a frequency switch, the kernel writes the index of the desired frequency to a special OSM register in memory and then TrustZone/OSM handles the rest based on the table programmed into it. TrustZone reads the tables from the QFPROM, which cannot be mutated by the kernel.
Here is proof that the overclock is fake, since the CPU can't possibly run at 10 GHz with no issues.
Oiya ada yg ikut Giveaway gak lur?
https://twitter.com/MrNotingHill/status/1311908640673071104?s=19
+1backcover gesture(?)
https://github.com/KieronQuinn/TapTap/releases/tag/0.8.1_beta
