Changes between Version 29 and Version 30 of boot_procedure


Ignore:
Timestamp:
May 3, 2017, 7:11:25 PM (5 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • boot_procedure

    v29 v30  
    77The ALMOS-MKH boot procédure can be decomposed in two phases:
    88 * The architecture dependent phase, implemented by an architecture specific '''boot_loader''' procedure.
    9  * The architecture indépendant phase, inplemented by a generis '''kernel-init''' procedure.
     9 * The architecture indépendant phase, inplemented by a generic '''kernel-init''' procedure.
    1010
    1111As the generic (i.e. architecture independent) kernel initialization procedure is executed in parallel by all kernel instances in all clusters containing at least one core and one memory bank, the main task of the boot-loader is to load - in each cluster - a local copy of
    12 the ALMOS-MKH kernel code, including a description of the hardware architecture, contained in the '''boot_info_t''' data-structure.
     12the ALMOS-MKH kernel code. This code includes a description of the hardware architecture, contained in the ''boot_info_t'' data-structure.
    1313
    14 This structure is build by the boot-loader and stored at the beginning of the local copy of the kdata segment. It contains both general and cluster specific informations:
    15  * general hardware architecture features : number of clusters, the topology, etc.
     14This fixed size ''boot_info_t'' structure is build by the boot-loader, and stored at the beginning of the local copy of the kdata segment. As it contains both general and cluster specific informations, the content depends on the cluster:
     15 * general hardware architecture features : number of clusters, topology, etc.
    1616 * available external (shared) peripherals : types and features.
    1717 * number of cores in cluster,
     
    2525in the file system root directory.
    2626
    27 This method allows -in principle - the boot_loader to check and reconfigure the hardware components, to guaranty that the generated boot_info_t structures contain only functionally tested hardware components.
     27This method allows the boot_loader to check and reconfigure the hardware components, to guaranty that the generated boot_info_t structures contain only functionally tested hardware components.
    2828
    2929We describe below the boot_loader for the TSAR architecture, the boot_loader for the I86 architecture, and the generic kernel initialization procedure.