Changes between Version 46 and Version 47 of boot_procedure


Ignore:
Timestamp:
Feb 28, 2019, 10:55:14 AM (8 months ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • boot_procedure

    v46 v47  
    3232
    3333The TSAR boot-loader uses an OS-independent '''pre-loader''', stored in an addressable but non-volatile device, that load the TSAR
    34 '''boot-loader''' code from an external block-device to the memory. This preloader is specific for the TSAR architecture, but independent on the Operating System. It is used by ALMOS-MKH, but also by LINUX, NetBSD, ALMOS_MKH, or the GIET-VM. 
    35 
    36 The TSAR boot_loader allocates - in each cluster containing a physical memory bank - five fixed size memory zones, to store various
     34'''boot-loader''' code from an external block-device to the cluster 0 physical memory. This preloader is specific for the TSAR architecture, but independent on the Operating System. It is used by ALMOS-MKH, but also by LINUX, NetBSD, ALMOS_MKH, or the GIET-VM. 
     35
     36The TSAR boot_loader allocates - in each cluster containing a physical memory bank - six fixed size memory zones, to store various
    3737binary files or data structures. The two first zones are permanently allocated: The PRE_LOADER zone is only defined in cluster 0. The KERNEL_CODE zone containing the ''kcode'' and ''kdata'' sgments is directly used by the kernel when the boot_loader transfers control - in each cluster - to the kernel_init procedure. The BOOT_ICODE, ARCH_INFO, KERNEL_ELF, and BOOT_CODE zones are temporary: they are only used - in each cluster - by the boot-loader code, and the corresponding physical memory can be freely used and re-allocated by the local kernel instance.
    3838