Difference between revisions of "More about KRNP3"
From NitrOS-9
(Created page with "Once the Level 2 kernel has started, there is a distinctions between "system" calls and "user" calls. No additional system calls can be added. To allow customisation, the ini...") |
(typo) |
||
Line 1: | Line 1: | ||
− | Once the Level 2 kernel has started, there is a | + | Once the Level 2 kernel has started, there is a distinction between "system" calls and "user" calls. No additional system calls can be added. |
To allow customisation, the initialisation of KRNP2 includes a step where it attempts to locate and initialise a module named KRNP3. This module must be part of the Bootfile - it will not be searched for on disk. To maintain generality, KRNP3 can itself attempt to locate and initialise a module named KRNP4 (and so forth). | To allow customisation, the initialisation of KRNP2 includes a step where it attempts to locate and initialise a module named KRNP3. This module must be part of the Bootfile - it will not be searched for on disk. To maintain generality, KRNP3 can itself attempt to locate and initialise a module named KRNP4 (and so forth). | ||
The code-base contains an [https://sourceforge.net/p/nitros9/code/ci/default/tree/level2/modules/krnp3_perr.asm example] of a KRNP3 module and an [https://sourceforge.net/p/nitros9/code/ci/default/tree/level2/modules/krnp4_regdump.asm example] of a KRNP4 module. | The code-base contains an [https://sourceforge.net/p/nitros9/code/ci/default/tree/level2/modules/krnp3_perr.asm example] of a KRNP3 module and an [https://sourceforge.net/p/nitros9/code/ci/default/tree/level2/modules/krnp4_regdump.asm example] of a KRNP4 module. |
Latest revision as of 19:38, 9 June 2017
Once the Level 2 kernel has started, there is a distinction between "system" calls and "user" calls. No additional system calls can be added.
To allow customisation, the initialisation of KRNP2 includes a step where it attempts to locate and initialise a module named KRNP3. This module must be part of the Bootfile - it will not be searched for on disk. To maintain generality, KRNP3 can itself attempt to locate and initialise a module named KRNP4 (and so forth).
The code-base contains an example of a KRNP3 module and an example of a KRNP4 module.