Author(s):	Peter Chubb
Location	C001
Date	jan Wed 18	Days Raw Files
Start	15:40	First Raw Start	error-in-template
Duration	0:50:00	Offset	None
End	16:30	Last Raw End
Chapters
Total cuts_time	None min.

http://lca2012.linux.org.au/schedule/49/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Linux_as_a_Boot_Loader.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Once upon a time, you could put a floppy disk with the Linux kernel on it into a PC and it would boot. Nowadays, you have to use a separate program (LILO, GRUB, U-Boot, Blob, LART, RedBoot, etc., etc.) to load Linux, set up some parameters, and then start it running. When you have new hardware, this sucks. You have to port not one but two programs that have intimate knowledge of the hardware. And you generally have to port USB stacks, Network drivers, etc., to an environment that's only used at boot time. Linux has a feature, kexecboot, that allows a running kernel to replace itself with another. This has been used in the Zaurus OpenEmbedded port to use Linux as a second-stage bootloader. So here's the plan: to use Linux with a small carefully-crafted initial ramdisk as a generic bootloader. The advantages should be obvious: port drivers only once; have a feature-rich pre-boot environment; not have to learn yet another low-level programming environment, and be able to boot anything (not just Linux) that you can get into the machine's memory. We currently have a plan, and a body to work on this. By December, we should have something reasonable for people to play with. In this talk, we'll go through the problems involved in getting from bare hardware to a running system, (i.e., what a bootloader does) and the challenges and experience of making a small, custom linux system that can boot not just Linux, but other operating systems such as L4 or Windows, and that works on a wide variety of platforms (ARM, X86, M68k, etc). markdown
Comment:	production notes