summaryrefslogtreecommitdiffstats
path: root/src/core/hle/kernel/svc.h (follow)
Commit message (Collapse)AuthorAgeFilesLines
* svc: Clarify enum values for AddressSpaceBaseAddr and AddressSpaceSize in svcGetInfo()Lioncash2018-10-151-2/+2
| | | | | | | | | | | | | So, one thing that's puzzled me is why the kernel seemed to *not* use the direct code address ranges in some cases for some service functions. For example, in svcMapMemory, the full address space width is compared against for validity, but for svcMapSharedMemory, it compares against 0xFFE00000, 0xFF8000000, and 0x7FF8000000 as upper bounds, and uses either 0x200000 or 0x8000000 as the lower-bounds as the beginning of the compared range. Coincidentally, these exact same values are also used in svcGetInfo, and also when initializing the user address space, so this is actually retrieving the ASLR extents, not the extents of the address space in general.
* Add & correct miscellaneous things (#470)greggameplayer2018-05-261-0/+3
| | | | | | | | | | | | * add some InfoType * correct OpenApplicationProxy cmd number * add IDisplayController functions * fix clang-format * add more system languages
* svc: Add additional fields to MemoryInfo struct.bunnei2018-01-191-0/+4
|
* SVC: Add 4.0.0+ comment to GetInfoType enum values.Subv2018-01-171-0/+1
|
* Added more svcGetInfo pairsDavid Marcec2018-01-161-0/+13
|
* yuzu: Update license text to be consistent across project.bunnei2018-01-131-1/+1
|
* Threads: Added enum values for the Switch's 4 cpu cores and implemented svcGetInfo(AllowedCpuIdBitmask)Subv2018-01-101-0/+1
|
* kernel: Rename Semaphore to ConditionVariable.bunnei2018-01-091-1/+1
|
* hle: Move SVC code to kernel namespace.bunnei2018-01-031-0/+38