Changes

Jump to navigation Jump to search
980 bytes added ,  20:30, 16 February 2017
no edit summary
Line 27: Line 27:     
Exactly 4 functions were added(includes the func for SVC 0x59 and the actual func for it). Exactly 14 functions were updated, 13 if not including the kernel-flags-parser func which verifies the exheader kernel-version etc(which only had compiler(?)-related changes minus version constant).
 
Exactly 4 functions were added(includes the func for SVC 0x59 and the actual func for it). Exactly 14 functions were updated, 13 if not including the kernel-flags-parser func which verifies the exheader kernel-version etc(which only had compiler(?)-related changes minus version constant).
 +
 +
Code addrs listed below are from the Old3DS kernel.
    
* A new [[SVC]] was implemented: 0x59. See [[SVC|here]] for the kernel implementation. This is used by the updated GSP-module.
 
* A new [[SVC]] was implemented: 0x59. See [[SVC|here]] for the kernel implementation. This is used by the updated GSP-module.
Line 33: Line 35:  
* The two functions that either add a [[KTimeableInterruptEvent]] instance to the global queue of pending [[KTimeableInterruptEvent]] (see [[KTimerAndWDTManager]]), or remove one from it, now return a boolean indicating whether the interrupt event already is/was in the queue (if that is true, the function that adds the interrupt event will now update the timer registers in that case as well). This is especially used for the below fixes.
 
* The two functions that either add a [[KTimeableInterruptEvent]] instance to the global queue of pending [[KTimeableInterruptEvent]] (see [[KTimerAndWDTManager]]), or remove one from it, now return a boolean indicating whether the interrupt event already is/was in the queue (if that is true, the function that adds the interrupt event will now update the timer registers in that case as well). This is especially used for the below fixes.
 
* When adding a timer to that queue, its reference count is incremented (if it wasn't already in the queue). It is only decremented when needed, after actually signaling the timer by the interrupt-handling code.
 
* When adding a timer to that queue, its reference count is incremented (if it wasn't already in the queue). It is only decremented when needed, after actually signaling the timer by the interrupt-handling code.
* A new vtable funcptr was added for certain classes, this just returns 1.
+
* L_fff20d28(Prev ver @ L_fff20b40): Added a call to L_fff1bb74() before calling L_fff1d514(), in two locations.
* 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.
+
* 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_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]]. 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 135: 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==

Navigation menu