Changes between Version 36 and Version 37 of boot_procedure
- Timestamp:
- Jun 29, 2018, 1:32:39 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
boot_procedure
v36 v37 44 44 45 45 The values given in this array are configuration parameters, that can be redefined in the '''boot_config.h''' file. 46 This memory is only used for temporary storage : when the boot_loader completes, and transfer control to the kernel_init procedure,47 the kernel code (i.e. the code and data segments) has been copied at physical address 0x4000 in all clusters.48 The four pages (16 Kbytes) reserved for the prelloader are only used in cluster 0 and can be saved if the preloader is stored in an external ROM.46 This memory is only used for temporary storage : when the TSAR boot_loader completes, and transfer control to the kernel_init procedure, 47 the kernel code (i.e. the code and data segments) has been copied - in each cluster - in the lowest part of the cluster physical memory. 48 The four pages (16 Kbytes) reserved for the prelloader are only used in cluster 0. 49 49 50 50 … … 52 52 In all clusters, the core with local index 0 is called ''CP0''. 53 53 54 54 We describe below the four boot phases : 55 55 56 56 Le chargement d'ALMOS-MK sur l'architecture TSAR se fait donc en 4 phases décrites ci-dessous … … 116 116 117 117 At this point, the boot-loader completed its job: 118 * The kernel code ''kcode'' and ''kdata'' segments are are loaded - in all clustersin the first ''offset'' physical pages.118 * The kernel code ''kcode'' and ''kdata'' segments are loaded - in all clusters - in the first ''offset'' physical pages. 119 119 * The hardware architecture described by the '''arch_info.bin'''file has been analyzed, and copied - in each cluster - in the '''boot_info_t''' structure, stored in the kdata segment. 120 120 * Each local kernel instance can use all the physical memory that is not used to store the kernel ''kcode'' and ''kdata'' segments themselves.