Changes

67 bytes removed ,  14:32, 26 August 2017
no edit summary
Line 123: Line 123:  
| 609 || Returns 0x10-byte output. Takes a ContentPath? ||  
 
| 609 || Returns 0x10-byte output. Takes a ContentPath? ||  
 
|-
 
|-
| 620 || SetSdCardEncryptionSeed ||  
+
| 620 || [[#SetSdCardEncryptionSeed]] || 0x19, 1
 
|-
 
|-
 
| 800 || GetAndClearFileSystemProxyErrorInfo ||  
 
| 800 || GetAndClearFileSystemProxyErrorInfo ||  
Line 359: Line 359:     
The input u64 high-byte must be non-zero, otherwise an [[Error_codes|error]] is returned(0xE02).
 
The input u64 high-byte must be non-zero, otherwise an [[Error_codes|error]] is returned(0xE02).
 +
 +
== SetSdCardEncryptionSeed ==
 +
Takes 0x10-bytes of input.
    
== SetGlobalAccessLogMode ==
 
== SetGlobalAccessLogMode ==
Line 375: Line 378:  
User-processes only use this when the value previously loaded from [[#GetGlobalAccessLogMode]] has bit1 set.
 
User-processes only use this when the value previously loaded from [[#GetGlobalAccessLogMode]] has bit1 set.
   −
GetGlobalAccessLogMode and OutputAccessLogToSdCard are usable without special permissions, however SetGlobalAccessLogMode requires that. When bit1 in GlobalAccessLogMode is clear, FS-module will just return 0 for OutputAccessLogToSdCard. However even with that set the log doesn't show up SD, unknown why.
+
When bit1 in GlobalAccessLogMode is clear, FS-module will just return 0 for OutputAccessLogToSdCard. However even with that set the log doesn't show up SD, unknown why.
    
The input buffer is written to the "$FsAccessLog:/FsAccessLog.txt" file, where "$FsAccessLog" is the SD-card mount-name. It's written to the current end of the file(appended).
 
The input buffer is written to the "$FsAccessLog:/FsAccessLog.txt" file, where "$FsAccessLog" is the SD-card mount-name. It's written to the current end of the file(appended).