Changes between Version 3 and Version 4 of Developer/Projects/Obsolete/Hypervisor


Ignore:
Timestamp:
Mar 26, 2010, 3:04:57 AM (10 years ago)
Author:
Cdcs
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Projects/Obsolete/Hypervisor

    v3 v4  
    2424
    2525The implementation of ARINC 653 interface in RTEMS was studied as part of a ESA project named AIR. This study was developed to "study of how the Real-Time Executive for Multiprocessor Systems (RTEMS) can be adapted to fullfill the requirements defined in the ARINC 653 standard". The project provided a proof of concept of the ARINC 553 implementation. The project page can be found [http://air.di.fc.ul.pt/ here].
    26  The final report can be found [http://air.di.fc.ul.pt/air/downloads/07-35.pdf here]. This document: (i) describes the main issues regarding the AIR architecture specification; (ii) addresses how space and time partitioning could be provided in an abstract processor infrastructure, as well as those requirements can be mapped into both SPARC ERC32/LEON and Intel IA-32 (80x86) architectures; (iii) describes how to achieve the mapping of the ARINC 653 service interface in RTEMS; (iv) identifies the most relevant module dependencies of RTEMS with regard to AIR implementations; (v) identifies a preliminary set of modifications to be introduced in the RTEMS application production chain for the implementation of AIR-based systems (exemplified through a proof of concept prototype)[ Quoted from  http://hdl.handle.net/10455/2982 ].
     26 The final report can be found [http://air.di.fc.ul.pt/air/downloads/07-35.pdf here]. "This document: (i) describes the main issues regarding the AIR architecture specification; (ii) addresses how space and time partitioning could be provided in an abstract processor infrastructure, as well as those requirements can be mapped into both SPARC ERC32/LEON and Intel IA-32 (80x86) architectures; (iii) describes how to achieve the mapping of the ARINC 653 service interface in RTEMS; (iv) identifies the most relevant module dependencies of RTEMS with regard to AIR implementations; (v) identifies a preliminary set of modifications to be introduced in the RTEMS application production chain for the implementation of AIR-based systems (exemplified through a proof of concept prototype)." Quoted from  http://hdl.handle.net/10455/2982 ).