Changes

557 bytes added ,  00:22, 19 April 2020
→‎Kernel: why does out size not get the real parameter
Line 110: Line 110:  
** Next, the lambda is called with entry template = input entry template, bitflag parameter = 1. This changes all mappings to new permissions, and flushes data cache on all new mappings.
 
** Next, the lambda is called with entry template = input entry template, bitflag parameter = 1. This changes all mappings to new permissions, and flushes data cache on all new mappings.
 
** Finally, mappings are merged, and the function returns.
 
** Finally, mappings are merged, and the function returns.
 +
* SvcQueryIoMapping's ABI was changed.
 +
** Previously signature was Result QueryIoMapping(uintptr_t *out_address, PhysicalAddress physical_address, size_t size).
 +
** New signature is Result QueryIoMapping(uintptr_t *out_address, size_t *out_size, PhysicalAddress physical_address, size_t size);
 +
** For normal IO, out_size is just written with the input size parameter.
 +
** For special debug regions (mapped using 8.0.0+ memory region descriptor, queried by passing 1/2/3 as phys_addr parameter), out_size is written with the real size of the queried region.
 +
 
<check back for more diffs later>
 
<check back for more diffs later>