LinuxBIOS: Difference between revisions
(initial stub of the page with some info) |
(*minor* spelling: s/flas/flash) |
||
Line 19: | Line 19: | ||
===Boot from NAND Flash=== |
===Boot from NAND Flash=== |
||
This is the normal case for the laptop. Simply loading a kernel off the NAND flash and then using kexec() to load that new kernel into memory and jump to it. This requires having a driver for the NAND flash and being able to locate the kernel on the internal NAND |
This is the normal case for the laptop. Simply loading a kernel off the NAND flash and then using kexec() to load that new kernel into memory and jump to it. This requires having a driver for the NAND flash and being able to locate the kernel on the internal NAND flash. |
||
===Boot from USB Devices=== |
===Boot from USB Devices=== |
Revision as of 23:06, 20 July 2006
Overview
We're using LinuxBIOS in place of a proprietary BIOS on the Laptop board. We're doing this for a number of reasons:
1. Cost. Per-machine royalties add to the cost of the laptop. Every cent we have to spend for each machine means some number of kids that don't get laptops.
2. Transparency. We want kids to be able to get all the way down to the bare metal on these machines. The transparency that LinuxBIOS gives us is matched by no others.
3. Functionality. Some parts of the design scenarios listed below are unique to this laptop. We would only be able to do this with the community and LinuxBIOS.
Hardware Limitations
We are limited to the 1MB of serial flash that's available in the OLPC board.
Design Goals
We have some pretty specific design goals with LinuxBIOS on on the Laptop hardware. We need to support a few re-install scenarios via the BIOS to enable kids in remote areas to be able to reflash their machines. The scenarios are outlined below.
Boot from NAND Flash
This is the normal case for the laptop. Simply loading a kernel off the NAND flash and then using kexec() to load that new kernel into memory and jump to it. This requires having a driver for the NAND flash and being able to locate the kernel on the internal NAND flash.
Boot from USB Devices
Another common system for booting the machine to recover it is to use a USB Flash Drive or use a USB Hard Drive to start an install process. This requires having decent USB drivers for flash drives and hard drives.
Boot from Wireless
This is the most interesting scenario, and one that is unique to this laptop. This feature could allow a kid in a remote area to get a boot image via a wireless network. This requires no external hardware (flash drives are expensive!) and you can use another machine as the image from which you would like to install. This requires including a wireless driver, the wireless firmware, networking and a small program that accepts the kernel image, loads it into ram and executes it.
Included Modules
- Kernel
- (MSRs?)
- Networking stack
- Basic HID USB drivers
- Marvell Driver
- Marvell Firmware
- Installer stub
- DirectFB driver
- NAND Flash driver
People
The following people are heavily involved with the LinuxBIOS project. Please contact them on the devel@laptop.org mailing list.
- Ronald Minnich
- Marcelo Tosatti
- Ray Tseng
- Roger Huang
- Morse Chen
- Jordan Crouse
- Michael Lin