Uwe Hermann | A slightly paranoid Debian developer

The coreboot project (previously known as LinuxBIOS) is taking part in the Google Summer of Code™ 2008 program. This year, the project has been assigned two slots/students who will work on the following projects:

• All Virtual All The Time (AVATT):

  This project aims to integrate into the coreboot BIOS a payload consisting of a minimalist KVM-aware Linux kernel along with an initrd image that contains the tools needed for creating and starting guest virtual machines installed on top of it. The resulting system could host any x86(or x86-64) OS that can run over KVM (almost any major OS does), and there is a great challenge to make it as small as possible, so that it can fit in a 2MB flash image.

• SCSI booting in coreboot:

  Currently coreboot can not boot from an arbitrary SCSI controller. There are two solutions for the problem: (1) Use Linux and Kexec. This requires to keep the SCSI driver in the flash chip. (2) Use x86emu/vm86/ADLO and the int13 method. This would allow to use the PCI option rom available on all modern SCSI controllers. So we obviously need a solution based on the latter. This could as well be implemented as a Linux program, as an intermediate payload, or as a shared library. At this point of time, I would like to implemente it as a daemon program. The program needs to catch the int13 interrupt vector that the SCSI option rom installs and make it available to arbitrary (firmware/payload) code trying to load something from disk.

This should make for an interesting summer with nice improvements for coreboot.

Public Service Announcement: The LinuxBIOS project, a Free Software project which intends to replace the proprietary BIOS found in most computers these days, has been renamed to coreboot.

The old name has become quite a misnomer in recent years; the name LinuxBIOS created the impression that it's a drop-in BIOS-replacement and that it's using Linux or is Linux-specific in any way. Neither is the case.

• coreboot is not a BIOS in the sense that it provides the legacy BIOS callbacks / interrupt routines. Instead, coreboot is just a small hardware initialization firmware. It does some basic hardware init, then hands over control to one of many possible payloads. This can be a boot loader such as FILO (or GRUB2, which shall ultimately replace FILO) if you want to boot from disk, or Plan 9, or memtest86, or a Linux kernel, or OpenBIOS/OpenFirmware/SmartFirmware, or...
• coreboot is not Linux or Linux-specific. Yes, it can indeed use Linux kernels as payload (i.e., you put the Linux kernel in your flash ROM chip together with coreboot) or boot a Linux kernel indirectly using FILO/GRUB2. But as mentioned above it can also be used (together with the fitting payload) to boot other OSes or systems such as Plan 9, Windows, FreeBSD, and others.

The initial author and project leader of LinuxBIOS/coreboot, Ron Minnich, explains in more detail why the renaming was done in his original announcement on the coreboot mailing list.

Since the "World's First Motherboard Using LinuxBIOS Released" hype at the beginning of this year (which was incorrect btw; it was not the first supported desktop board, there were many others before), LinuxBIOS hasn't been in the news very much. That doesn't mean that there was no progress, however. We've been working hard behind the scenes to improve the LinuxBIOS code, add support for new chipsets and boards, and advance the upcoming next-generation LinuxBIOSv3 version which will brings lots of great improvements in various areas.

Here's a random collection of stuff that happened in the last few months.

New chipsets:

• AMD K8 / NVIDIA MCP55, contributed by Yinghai Lu of AMD
• VIA VT82C686A/B southbridge, contributed by Corey Osgood
• AMD Geode LX / CS5536, contributed by Marc Jones and Jordan Crouse of AMD
• Intel 810 northbridge, contributed by Corey Osgood
• AMD K8 / VIA K8T890 / VT8237R, contributed by Rudolf Marek / Corey Osgood
• AMD K8 / SiS761GX / SiS966(L), contributed by Morgan Tsai of SiS

New mainboards:

• Sun Ultra40, contributed by Ronald G. Minnich (LinuxBIOS project founder)
• K9SD Master-S2R (MS-9185), contributed by Bingxun Shi of MSI
• K9SD Master Series (MS-9282), contributed by Bingxun Shi of MSI
• GIGABYTE GA-M57SLI-S4, contributed by Yinghai Lu of AMD
• NVIDIA l1_2pvv, contributed by Yinghai Lu of AMD
• Supermicro H8DMR, contributed by Yinghai Lu of AMD
• Tyan S2912, contributed by Yinghai Lu of AMD
• Tyan S1846, contributed by myself
• AMD Norwich (AMD Geode LX reference platform), contributed by Marc Jones and Jordan Crouse of AMD
• IGEL Winnet III thin client, contributed by myself
• ASUS A8N-E, contributed by Phillip Degler
• IEI JUKI-511P, contributed by Nikolay Petukhov
• IEI ROCKY-512, contributed by Nikolay Petukhov
• AMD DB800 (a.k.a. Salsa), contributed by Marc Jones and Jordan Crouse of AMD
• ASUS MEW-VM, contributed by Corey Osgood
• Artec Group DBE61, contributed by Marc Jones and Jordan Crouse of AMD
• PC Engines ALIX.1C, contributed by Ronald G. Minnich
• MSI MS-6178, contributed by myself
• MSI MS-7260 (K9N Neo), contributed by myself
• IGEL-316 thin client, contributed by Jürgen Beisert
• AXUS TC320 thin client, contributed by Jürgen Beisert
• GIGABYTE GA-2761GXDK (Churchill), contributed by Morgan Tsai of SiS
• And a bunch of older Intel 440BX based boards, contributed by myself with some help by testers via IRC: ASUS P2B/P2B-F/P3B-F, A-Trend ATC-6220, AZZA PT-6IBD, Biostar M6TBA, Compaq Deskpro EN SFF P600, GIGABYTE GA-6BXC
• ASUS A8V-E SE, contributed by Rudolf Marek

Note that not all of these may be 100% supported, some may still be work in progress with some TODO items left... Check the LinuxBIOS wiki or ask on the mailing list for details.

The future

Most work will probably go into LinuxBIOSv3 in the future, in order to make it suitable for productive use.
Of course, work on new chipsets and boards will continue, too. For example the VIA CN700 chipset (plus Jetway J7F2WE board using it) is being worked on right now, probably also several others I don't know about.

Call for board testers

If you're interesting in trying out LinuxBIOS, please check the list of supported motherboards. If your board is not listed there, but the chipset is already supported we can probably add support for your board relatively easy with some testing help from you.

Please contact us on IRC or preferrably on the mailing list if you want to help get your board supported!

An (incomplete) list of good candidate boards for future support is available in the wiki.

Thanks!

We're very grateful for the many contributors who have helped us with testing and fixing existing code, or who even contributed code for new chipsets and motherboards. Thanks a lot!

Many thanks especially to all hardware vendors who have been supporting us or even actively contributed by submitting code for their chipsets or boards (recently or in the past), including AMD, SiS, VIA, MSI, Tyan, Artec Group, and many others. Your efforts are very appreciated. Thanks!

Highly recommended for anybody who might be even remotely interested in LinuxBIOS:

There's a video recording (OGG, 234 MB) of the LinuxBIOS talk at FOSDEM 2007 by LinuxBIOS-founder Ron Minnich.

The talk is about LinuxBIOS, its history, how it works, what the main challenges are, where it's used today and what the future will likely hold. Watch it, you won't regret it.

And if you want to know more, or maybe even consider contributing, head over to linuxbios.org or contact the mailing list.

A few interesting interviews with speakers at the upcoming FOSDEM 2007 have been published.

I especially recommend reading the interview with Ronald G. Minnich, the founder of the LinuxBIOS project.

Here are the questions he was asked:

• What's your goal for your talk at FOSDEM?
• We saw the mention on the LinuxBIOS website about one million devices shipped with LinuxBIOS. Could you tell us more about these devices?
• What kind of support have you received from chipset and motherboard manufacturers so far?
• Could LinuxBIOS theoretically replace all BIOSes, of are there certain limitations to be taken into account?
• Could you tell us a bit more about the BIOS side of the OLPC laptop?
• What exactly is the difference between "easy" hardware to write a BIOS for, and the "tough" hardware?
• What are your thoughts on the Extensible Firmware Interface (EFI)?

Answers here ;-)