argos-research / documentation Goto Github PK

Description of behavior.
How to use dom0-HW and toolchain?

We need a more in depth documentation about the PXE setup

Write a documentation page about the multi-core specific features of genode and fiasco.oc and its interplay in general. Consider our several platforms e.g. Pandaboard or PBXA9

The Install documentation is lacking in several points.

• The documentation is more or less just a collection of bash scripts.
• The documentation seems to not be current anymore at parts
• ...

I suggest we improve the points and additionally describe how to execute the whole setup in qemu (pbxa9) with an example application (not necessarily dom0-HW) in our operating-system/vagrant setup, since most students/we won't execute the whole setup with real hardware if they/we are just implementing small features.

@seckl @DK87 @privatereese @Khesp @BugUser0815 @irgendwie please add a short description of your work to this page: https://argos-research.github.io/team.html
Should only be one/two sentences to get an overview on what you are doing (or have done in the past).

There is a required fix for qemu according to submodules - please document it

I'm completely missing a description of the Vagrant VM.
Especially interesting could be a description of which services need to / are run(ning) in the VM, what service need to run on the host? How is the network between VM and host handled? etc.

• Description of the project
• Documentation links (Wiki, IRC, etc.)
• Images ;)
• Getting Started?
• Information about the Team?

Most Wiki pages don't use the summary feature to describe what the whole page is about.

if you click on the link "plattform instructions" at the bottom of this page (https://argos-research.github.io/documentation/install.html) the 404 happens. @privatereese

The PXE documentation in its current state isn't very helpful.

Since @privatereese is currently working on integrating a DHCP service into the Vagrant VMs, why not explain in this part of the documentation the boot flow we have for the real boards:

1. Build Fiasco.OC/Genode OS in Vagrant
2. Provide *.elf or *.img via TFTP
3. Boot platforms via U-Boot
4. Receive ip address, tftp server ip address, tftp image via DHCP
5. Boot the OS on the platforms