11.3.0-36: Difference between revisions

Emufan4568 (talk | contribs)
mNo edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 38: Line 38:
* L_fff2131c(Prev ver @ L_fff21124): Same changes as L_fff20d28.
* L_fff2131c(Prev ver @ L_fff21124): Same changes as L_fff20d28.
* L_fff26348(Prev ver @ L_fff2631c): Same changes as L_fff20d28 except with four locations.
* L_fff26348(Prev ver @ L_fff2631c): Same changes as L_fff20d28 except with four locations.
* A new vtable funcptr was added for certain classes, this just returns 1.
* L_fff28058(Prev ver @ L_fff27e28): Same changes as L_fff20d28 except with just one location.
* L_fff28058(Prev ver @ L_fff27e28): Same changes as L_fff20d28 except with just one location.
* A virtual method was added to the definition of abstract class [[KTimeableInterruptEvent]], which returns <code>static_cast<KAutoObject *>(this)->referenceCount != 1</code> for KTimer instances and <code>true</code> for KThread instances. Prior to (re)adding timer interrupt events (as well as some other objects) to the queue, objects with a refcount of 1 are removed from it.
* A virtual method was added to the definition of abstract class [[KTimeableInterruptEvent]]. Prior to (re)adding KTimer instances as interrupt events (and some other objects) to the queue, objects of the queue with this method returning <code>false</code> are removed from it. Its implementations are the following:
** For [[KTimer]] instances, returns <code>static_cast<KAutoObject *>(this)->referenceCount != 1</code> (L_fff2c37c)
** For instances of [[KThread]] and the dummy subclass of KTimerAndWDTManager+0x10: returns <code>true</code> (L_fff26790).


===Modules===
===Modules===
Line 141: Line 142:
   Balance:  
   Balance:  
   Credit-Card Funding
   Credit-Card Funding
==New issue==
This update, even on systems not running modded-FIRM apparently, caused a slowdown in certain cases in some game(s). For example, with Sheikah Stones in "The Legend of Zelda: Ocarina of Time 3D", there's noticeable audio issues.
This was caused by the NATIVE_FIRM ARM11-kernel changes: when running v11.2 NATIVE_FIRM with v11.3-nandimage(with the required patches to get NATIVE_FIRM to run with v11.3-nandimage), this new issue doesn't occur.


==See Also==
==See Also==
Line 146: Line 152:
* [https://yls8.mtheall.com/ninupdates/reports.php?date=02-06-17_07-00-38&sys=ctr]
* [https://yls8.mtheall.com/ninupdates/reports.php?date=02-06-17_07-00-38&sys=ctr]
* [https://yls8.mtheall.com/ninupdates/reports.php?date=02-06-17_07-00-47&sys=ktr]
* [https://yls8.mtheall.com/ninupdates/reports.php?date=02-06-17_07-00-47&sys=ktr]
[[Category:Firmware Versions]]