HOWTOs: Difference between revisions
From TUDOS-Wiki
Jump to navigationJump to search
Line 18: | Line 18: | ||
** Boot from [[TFTP server]] | ** Boot from [[TFTP server]] | ||
* serial console | * serial console | ||
* [[GRUB]] | * Booting | ||
** [[building patched grub]] | ** [[GRUB]] | ||
** [[menu.lst]] | *** [[building patched grub]] | ||
*** [[menu.lst-Examples]] | *** [[menu.lst]] | ||
** Enhanced GRUB1 [http://os.inf.tu-dresden.de/~adam/grub/ patches] | **** [[menu.lst-Examples]] | ||
*** This grub1 version is maintained. You can send patches. | *** Enhanced GRUB1 [http://os.inf.tu-dresden.de/~adam/grub/ patches] | ||
** [[GRUB2]] | **** This grub1 version is maintained. You can send patches. | ||
*** [[GRUB2]] | |||
** Images | |||
*** Call 'make help' in the l4/ root directory to get a listing of possible image generation targets | |||
*** See l4/conf/Makeconf.boot.example for more information on customization | |||
*** u-boot: | |||
**** Call 'make uimage E=entry' to generate an uImage | |||
**** Load into u-boot (tftpboot, usb-stick, flash, ...) | |||
**** bootm .... | |||
*** ELF images: make elfimage E=name | |||
**** loadable with any loader that understand ELF (including GRUB, Lauterbach, ARM RVDS, QEmu) | |||
*** Raw images: make rawimage E=name | |||
**** copy into RAM at the start address, set PC to start address and run | |||
**** On ARM the images relocate itself to their linked address, i.e. they can be put anywhere in RAM (copying them to the right place will make booting faster of course). | |||
** Qemu | |||
*** Go to obj-dir root | |||
*** Call 'make qemu E=entry' | |||
*** For Qemu customization (esp. on ARM) see l4/conf/Makeconf.boot.example and add options to your l4/conf/Makeconf.boot | |||
** Virtualbox | |||
*** Go to obj-dir root | |||
*** Call 'make vbox E=entry' | |||
*** You need a configuration virtual machine in vbox for that to work. Check l4/conf/Makeconf.boot.example to see how to configuration vbox specifics. | |||
** You may omit the E=entry which will present you a menu to choose the entry to generate/start from. | |||
== Miscellaneous How-Tos == | == Miscellaneous How-Tos == |
Revision as of 15:15, 9 January 2011
Building Fiasco and L4Re components
Running and using Fiasco and L4Re components
- Systems to use
- hardware requirements
- virtual machines
- QEmu
- Fiasco-UX
- VMware
- Virtualbox
- Boot from CD
- Boot from TFTP server
- serial console
- Booting
- GRUB
- building patched grub
- menu.lst
- Enhanced GRUB1 patches
- This grub1 version is maintained. You can send patches.
- GRUB2
- Images
- Call 'make help' in the l4/ root directory to get a listing of possible image generation targets
- See l4/conf/Makeconf.boot.example for more information on customization
- u-boot:
- Call 'make uimage E=entry' to generate an uImage
- Load into u-boot (tftpboot, usb-stick, flash, ...)
- bootm ....
- ELF images: make elfimage E=name
- loadable with any loader that understand ELF (including GRUB, Lauterbach, ARM RVDS, QEmu)
- Raw images: make rawimage E=name
- copy into RAM at the start address, set PC to start address and run
- On ARM the images relocate itself to their linked address, i.e. they can be put anywhere in RAM (copying them to the right place will make booting faster of course).
- Qemu
- Go to obj-dir root
- Call 'make qemu E=entry'
- For Qemu customization (esp. on ARM) see l4/conf/Makeconf.boot.example and add options to your l4/conf/Makeconf.boot
- Virtualbox
- Go to obj-dir root
- Call 'make vbox E=entry'
- You need a configuration virtual machine in vbox for that to work. Check l4/conf/Makeconf.boot.example to see how to configuration vbox specifics.
- You may omit the E=entry which will present you a menu to choose the entry to generate/start from.
- GRUB