1 |
3 |
drasko |
OpenRisc Codezero Microkernel Port
|
2 |
2 |
drasko |
|
3 |
3 |
drasko |
03.05.2010. Drasko DRASKOVIC
|
4 |
|
|
|
5 |
|
|
This project represents effort in porting Codezero L4 Microkernel
|
6 |
|
|
(http://l4dev.org/) to the OpenRisc 1000 (http://opencores.org/project,or1k)
|
7 |
|
|
architecture.
|
8 |
|
|
|
9 |
|
|
|
10 |
|
|
|
11 |
2 |
drasko |
Codezero Microkernel v0.2 Release
|
12 |
|
|
|
13 |
|
|
Copyright (C) 2007 - 2009 Bahadir Bilgehan Balban
|
14 |
|
|
|
15 |
|
|
|
16 |
|
|
1.) What is Codezero?
|
17 |
|
|
|
18 |
|
|
Codezero is an L4 microkernel that has been written from scratch. It targets
|
19 |
|
|
embedded systems and its purpose is to act as a secure embedded hypervisor. It
|
20 |
|
|
aims to become the most modern L4 implementation by evolving the L4 microkernel
|
21 |
|
|
API into the future. In a nutshell, Codezero provides all the basic mechanism
|
22 |
|
|
to abstract away the hardware, build OS services, isolate applications and
|
23 |
|
|
fine-grain security in a single package.
|
24 |
|
|
|
25 |
|
|
|
26 |
|
|
2.) Why the name Codezero?
|
27 |
|
|
|
28 |
|
|
The project philosophy is to create the simplest and leanest microkernel that
|
29 |
|
|
is generic and applicable to many different applications. Feature creep is what
|
30 |
|
|
we don't have in Codezero. Simple, elegant design is the project philosophy.
|
31 |
|
|
|
32 |
|
|
|
33 |
|
|
3.) Why use Codezero?
|
34 |
|
|
|
35 |
|
|
Codezero aims to be technically cutting-edge. It's design is open and improves
|
36 |
|
|
by evolution. It is also easy-to-use, well-documented and portable, mostly
|
37 |
|
|
maturing on the ARM architecture. These might be the appealing reasons from a
|
38 |
|
|
technical point-of-view. It is also backed by a responsive team, in case you
|
39 |
|
|
have more demanding requirements.
|
40 |
|
|
|
41 |
|
|
|
42 |
|
|
4.) What is the license?
|
43 |
|
|
|
44 |
|
|
The current release is distributed under GNU General Public License Version 3.
|
45 |
|
|
For contributions we ask for a copyright share agreement and you may freely
|
46 |
|
|
contribute to the project this way. We also have commercial licensing options
|
47 |
|
|
available. This is our current model for keeping the project design and
|
48 |
|
|
development completely open, while thriving it by professional funding. If you
|
49 |
|
|
feel this is too restrictive, feel free to mention your ideas in our mailing
|
50 |
|
|
list.
|
51 |
|
|
|
52 |
|
|
The third party source code under the directories loader/ tools/ libs/c
|
53 |
|
|
libs/elf have their own copyright and licenses, separate from this project. All
|
54 |
|
|
third party source code is open source in the OSI definition. Please check
|
55 |
|
|
these directories for their respective licenses.
|
56 |
|
|
|