Difference between revisions of "Services API"
Jump to navigation
Jump to search
m |
|||
| Line 7: | Line 7: | ||
* [[Process Services]] | * [[Process Services]] | ||
* [[Application Manager Services]] | * [[Application Manager Services]] | ||
| + | * [[Process Manager Services]] | ||
* [[NIM Services]] | * [[NIM Services]] | ||
* [[Config Services]] | * [[Config Services]] | ||
| Line 26: | Line 27: | ||
List of ports: | List of ports: | ||
| − | |||
* [[ErrDisp]] | * [[ErrDisp]] | ||
Revision as of 05:17, 2 May 2013
Nintendo provides application developers with an API, which behind the scenes communicate with certain services. Services in this sense are system processes running in the background which wait for incoming requests. When a process wants to communicate with a service, it first needs to get a handle to the named service, and then it can communicate with the service via interprocess communication. Each service has a name up to 8 characters, for example "nim:u".
Handles for services are retrieved from the service manager port, "srv:". Services are an abstraction of ports, they operate the same way except regular ports can have their handles retrieved directly from a SVC.
List of services:
- Filesystem services
- Process Services
- Application Manager Services
- Process Manager Services
- NIM Services
- Config Services
- NS and APT Services
- RO Services
- NDM Services
- GSP Services
- IR Services
- I2C Services
- HID Services
List of PXI services:
- Filesystem services PXI
- Process Services PXI
- Application Manager Services PXI
- Process Manager Services PXI
- Development Services PXI
- Gamecard Services PXI
List of ports: