... | @@ -7,8 +7,7 @@ But even if you think you have not enough technical skill to deal directly with |
... | @@ -7,8 +7,7 @@ But even if you think you have not enough technical skill to deal directly with |
|
there are some task as much important you may do!
|
|
there are some task as much important you may do!
|
|
|
|
|
|
|
|
|
|
## Hack the kernel!
|
|
## Hack the kernel
|
|
|
|
|
|
This is the most evident kind of task : help us to improve the kernel code, to make it faster,
|
|
This is the most evident kind of task : help us to improve the kernel code, to make it faster,
|
|
smarter, more stable, or portable accross other hardware platforms.
|
|
smarter, more stable, or portable accross other hardware platforms.
|
|
Of course, writing code for the kernel need to *master* at least the C language, and depending
|
|
Of course, writing code for the kernel need to *master* at least the C language, and depending
|
... | @@ -18,8 +17,7 @@ of FiXos are really generics and do not deal at all with the hardware). |
... | @@ -18,8 +17,7 @@ of FiXos are really generics and do not deal at all with the hardware). |
|
More informations to be ready are available in the wiki : [Resources about kernel hacking](kernel-hacking) and [Some documentation of FiXos internals](fixos-internals).
|
|
More informations to be ready are available in the wiki : [Resources about kernel hacking](kernel-hacking) and [Some documentation of FiXos internals](fixos-internals).
|
|
|
|
|
|
|
|
|
|
## Test it!
|
|
## Test it
|
|
|
|
|
|
Writing a kernel which work well on a given platform is cool.
|
|
Writing a kernel which work well on a given platform is cool.
|
|
Writing a kernel which work perfectly on **many** platforms is better!
|
|
Writing a kernel which work perfectly on **many** platforms is better!
|
|
|
|
|
... | @@ -28,7 +26,6 @@ would like to improve it *indirectly*, by testing and [reporting bugs](bug-repor |
... | @@ -28,7 +26,6 @@ would like to improve it *indirectly*, by testing and [reporting bugs](bug-repor |
|
|
|
|
|
|
|
|
|
## Improve documentation
|
|
## Improve documentation
|
|
|
|
|
|
Kernel documentation is *very* important, but at this time it really lacks.
|
|
Kernel documentation is *very* important, but at this time it really lacks.
|
|
Helping us to create documentation, both for kernel and userspace hackers, and helping to correct and
|
|
Helping us to create documentation, both for kernel and userspace hackers, and helping to correct and
|
|
improve it is *not* less useful than writing code!
|
|
improve it is *not* less useful than writing code!
|
... | @@ -38,7 +35,6 @@ many things to correct in the documentation, in this wiki, and maybe elsewhere! |
... | @@ -38,7 +35,6 @@ many things to correct in the documentation, in this wiki, and maybe elsewhere! |
|
|
|
|
|
|
|
|
|
## Hack the userspace!
|
|
## Hack the userspace!
|
|
|
|
|
|
Userspace is less delicate, and maybe more fun if you like to interract with the user instead of with the hardware.
|
|
Userspace is less delicate, and maybe more fun if you like to interract with the user instead of with the hardware.
|
|
A kernel alone is as useless as a nice coffee cup without coffee (sorry, first analogy I found).
|
|
A kernel alone is as useless as a nice coffee cup without coffee (sorry, first analogy I found).
|
|
|
|
|
... | | ... | |