Flameman/os - Revision history

Legacy: /* Prex */

2012-04-18T01:21:12Z

‎Prex

Legacy: /* Prex */

2012-04-18T01:06:21Z

‎Prex

Legacy: /* embedded kernel */

2012-04-18T01:05:02Z

‎embedded kernel

Cschalle: Add categories

2011-10-28T07:49:55Z

Add categories

Flameman: /* embedded kernel = */

2011-07-28T12:35:11Z

‎embedded kernel =

Flameman: /* picoOS */

2010-02-03T15:22:34Z

‎picoOS

Flameman: /* Practice = */

2009-10-13T14:42:00Z

‎Practice =

Flameman: /* picoOS */

2009-10-13T14:41:30Z

‎picoOS

Flameman: /* what is an OS ? */

2009-10-13T14:40:58Z

‎what is an OS ?

Flameman: /* Safety Critical Products */

2009-08-19T16:30:15Z

‎Safety Critical Products

← Older revision		Revision as of 01:21, 18 April 2012
Line 48:		Line 48:

	Prex Design The Prex microkernel provides only fundamental features for task, thread, memory, IPC, exception, and synchronization. The other basic OS functions - process, file system, application loading, and networking, are provided by the user mode servers. In addition, Prex provides a POSIX emulation layer in order to utilize existing *NIX applications. This design allows the system to perform both of the native real-time task and the generic POSIX process simultaneously without degrading real-time performance. It also helps platform designers to construct OS by choosing suitable system servers for their target requisition.		Prex Design The Prex microkernel provides only fundamental features for task, thread, memory, IPC, exception, and synchronization. The other basic OS functions - process, file system, application loading, and networking, are provided by the user mode servers. In addition, Prex provides a POSIX emulation layer in order to utilize existing *NIX applications. This design allows the system to perform both of the native real-time task and the generic POSIX process simultaneously without degrading real-time performance. It also helps platform designers to construct OS by choosing suitable system servers for their target requisition.
		+
		+
		+	Si tratta sostanzialmente di un sistema operativo Real Time, compatibile POSIX, multithreaded, molto leggero (gira addirittura su un GameBoy) e adatto per i processori ARM, PowerPC e x86.
		+
		+	La particolarità di questo sistema è il doppio memory model, funziona in pratica con e senza MMU.
		+
		+	Funzionamento con MMU
		+	Ogni processo ha il suo address space separato, ad ogni context switch avviene anche la riprogrammazione della MMU e il flush del TLB. Non implementa memoria virtuale e/o paginazione, ma sarebbe abbastanza triviale implementarlo data la struttura del kernel.
		+
		+	Funzionamento senza MMU
		+	Ogni processo viene rilocato ad un indirizzo fisico come se fosse una libreria, non essendoci MMU ogni processo può influire sugli altri, simile per certi versi al memory model di AROS / AmigaOS.
		+

@@ Line 50: / Line 50: @@
-Prex has the following features:
+=== features ===
 * Task & Thread Control: preemptive priority scheduling with 256 priority levels
-( Memory Management: memory protection, virtual address mapping, shared memory, MMU or MMU-less configuration
+* Memory Management: memory protection, virtual address mapping, shared memory, MMU or MMU-less configuration
 * IPC: object name space, synchronous message passing between threads
 * Exception: fault trapping, framework for POSIX signal emulation
@@ Line 83: / Line 83: @@
 * arm-integrator/ARM9/Integrator/CP/QEMU
 * ppc-prep/PowerPC/PReP (MMU-less)/QEMU
 == Category ==

@@ Line 41: / Line 41: @@
 * ERIKA is OSEK/VDX
-[[Category:Flameman]]
-[[Category:Embedded Dictionary]]

← Older revision		Revision as of 07:49, 28 October 2011
Line 40:		Line 40:
	* ucosII has its custom API		* ucosII has its custom API
	* ERIKA is OSEK/VDX		* ERIKA is OSEK/VDX
		+
		+	[[Category:Flameman]]
		+	[[Category:Embedded Dictionary]]

@@ Line 35: / Line 35: @@
-== embedded kernel ===
+== embedded kernel ==
 * shark is POSIX/PSE51
 * ucosII has its custom API
 * ERIKA is OSEK/VDX

@@ Line 29: / Line 29: @@
 = Practice: where can i see a good kernel ? =
-== picoOS ==
+== mips, xinu is a picokernel ==
 XINU (MIPS oriented) http://xinu.mscs.mu.edu/Main_Page

← Older revision		Revision as of 14:40, 13 October 2009
Line 25:		Line 25:

	INTEGRITY-178B http://www.ghs.com/products/safety_critical/integrity-do-178b.html		INTEGRITY-178B http://www.ghs.com/products/safety_critical/integrity-do-178b.html
		+
		+
		+	== picoOS ==
		+
		+	XINU (MIPS oriented) http://xinu.mscs.mu.edu/Main_Page

@@ Line 13: / Line 13: @@
 == Safety Critical Products ==
 === INTEGRITY®-178B RTOS ===
 The INTEGRITY®-178B operating system is the most secure operating system in the world having been certified by the NSA-managed NIAP lab to EAL6+ High Robustness. No other commercial operating system has attained his level of security. No other commercial operating system has entered into an evaluation at EAL6+ High Robustness.
 In the past, Safety Critical software systems with multiple levels of safety criticality have been deployed on federated systems, where each function executes on a dedicated processor. The need to lower maintenance costs and reduce the size/weight/power of older embedded computer systems, combined with the availability of modern processor technology, has created the demand for a commercial run-time system that permits multiple programs at different safety levels to execute on a single processor. In addition, the run-time system must be certifiable to a level of criticality as high or higher than that of any program running on the processor.