Changes between Version 6 and Version 7 of arch_info
- Timestamp:
- Jul 20, 2016, 2:03:12 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
arch_info
v6 v7 6 6 7 7 All relevant parameters describing the clustered multi-core architecture must be defined in the binary '''arch_info.bin''' file. 8 This binary file is exploited by the ALMOS-MK boot loader to configure ALMOS-MK. It can be generated by a specific '''arch .py''' python scrip, for each target architecture.8 This binary file is exploited by the ALMOS-MK boot loader to configure ALMOS-MK. It can be generated by a specific '''arch_info.py''' python scrip, for each target architecture. 9 9 10 10 == 1) Cluster and cores identification == … … 30 30 31 31 For ALMOS-MK, the target hardware architecture is described in the binary file '''arch_info.bin'''. 32 This file is loaded from disk by the ALMOS-MK boot-loader. This boot-loader uses the informations found in '''arch_info.bin''' to build one '''boot_info_t''' structure in each cluster. This generic '''boot_info_t''' structure is the hardware abstraction used by the ALMOS kernel to build in each cluster its own representation of the hardware.32 This file is loaded from disk by the ALMOS-MK boot-loader. 33 33 34 34 === 2.1) General assumptions === … … 63 63 64 64 This section defines the python constructs that can be used to generate the '''arch_info.bin''' binary file. 65 66 == 3) The boot_info_t structure == 67 68 The ALMOS-MK boot-loader uses the informations found in '''arch_info.bin''' to build one '''boot_info_t''' structure in each cluster. This generic '''boot_info_t''' structure is used by the ALMOS kernel to build in each cluster its own representation of the hardware. 69 Therefore, the '''boot_info_t''' structure defines the generic (hardware independent) interface between the hardware specific boot-loader and the kernel. 70 71 It is defined in the [source:almos-work/kernel/libk/boot_info.h] file.