Editing Coreboot

{{Short description|Open-source computer firmware}}
{{Use dmy dates|date=July 2019}}
{{Lowercase title}}
{{Infobox software
| name = coreboot
| logo = File:Coreboot full.svg
| logo alt = Graphic of a running hare in black and white above text "coreboot" in lowercase sans-serif font
| logo size = 150px
| screenshot =
| caption =
| author = Ronald G. Minnich, Eric Biederman, Li-Ta (Ollie) Lo, Stefan Reinauer, and the coreboot community
| developer =
| released = {{Start date and age|df=yes|1999}}
| latest release version = {{Wikidata|properties|references|edit|P348|P548=Q2804309}}
| latest release date    = {{Start date and age|{{Wikidata|qualifier|single|P348|P548=Q2804309|P577}}}}<ref name="coreboot-downloads">{{Cite web |url=https://www.coreboot.org/releases |title=Releases |date=n.d. |website=coreboot}}</ref>
| programming language = Mostly [[C (programming language)|C]], about 1% in [[Assembly language|assembly]] and optionally [[SPARK (programming language)|SPARK]]
| platform = [[IA-32]], [[x86-64]], [[ARMv7]],<ref>{{cite web|url=https://www.coreboot.org/ARM |title=ARM |publisher=coreboot |date=15 October 2013 |access-date=1 February 2014}}</ref> ARMv8, [[RISC-V]], POWER8
| genre = [[Firmware]]
| license = [[GPLv2]]-only<ref>{{Cite web|url=https://github.com/coreboot/coreboot/blob/master/COPYING|title=coreboot's licence|date=1991|website=github.com|access-date=2018-10-13}}</ref>
}}

'''coreboot''', formerly known as '''LinuxBIOS''',<ref>{{cite web
|url=http://coreboot.org/pipermail/coreboot/2008-January/029135.html
|title=&#91;LinuxBIOS&#93; Welcome to coreboot
|date=12 January 2008
}}</ref> is a software project aimed at replacing proprietary [[firmware]] ([[BIOS]] or [[UEFI]]) found in most computers with a lightweight firmware designed to perform only the minimum number of tasks necessary to load and run a modern [[32-bit]] or [[64-bit]] [[operating system]].

Since coreboot initializes the bare hardware, it must be ported to every [[chipset]] and [[motherboard]] that it supports. As a result, coreboot is available only for a limited number of hardware platforms and motherboard models.

One of the coreboot variants is [[Libreboot]], a [[software distribution]] partly free of [[binary blob|proprietary blobs]], aimed at end users.

== History ==
The coreboot project began with the goal of creating a BIOS that would start fast and handle errors intelligently.<ref>{{cite web |author=Anton Borisov |url=http://www.h-online.com/open/features/The-Open-Source-BIOS-is-Ten-An-interview-with-the-coreboot-developers-746525.html?view=print |title=The Open Source BIOS is Ten. An interview with the coreboot developers |website=[[The H]] |date=2009 |archive-url=https://web.archive.org/web/20120916212555/http://www.h-online.com/open/features/The-Open-Source-BIOS-is-Ten-An-interview-with-the-coreboot-developers-746525.html?view=print |archive-date=16 September 2012 |url-status=dead}}'</ref> It is licensed under the terms of the [[GNU General Public License]] version 2 (GPLv2). Main contributors include [[Los Alamos National Laboratory|LANL]], [[Silicon Integrated Systems|SiS]], [[Advanced Micro Devices|AMD]], Coresystems and Linux Networx, Inc, as well as motherboard vendors [[Micro-Star International|MSI]], [[Gigabyte Technology|Gigabyte]] and [[Tyan]], which offer coreboot alongside their standard BIOS or provide specifications of the hardware interfaces for some of their motherboards. [[Google]] partly sponsors the coreboot project.<ref>{{Cite web|url=http://google-code-updates.blogspot.com/2006/11/google-sponsors-linuxbios-project.html|title=Google Sponsors the LinuxBIOS project|access-date=29 September 2023|archive-date=6 February 2012|archive-url=https://web.archive.org/web/20120206205540/http://google-code-updates.blogspot.com/2006/11/google-sponsors-linuxbios-project.html|url-status=bot: unknown}}</ref> [[CME Group]], a financial public company, began supporting the coreboot project in 2009.<ref>{{cite web|url=http://www.wallstreetandtech.com/it-infrastructure/showArticle.jhtml?articleID=217400294|title=CME Group Dives Into Coreboot and Other Linux Open Source Projects|work=Wall Street & Technology|access-date=23 September 2015|archive-url=https://web.archive.org/web/20100812092429/http://www.wallstreetandtech.com/it-infrastructure/showArticle.jhtml?articleID=217400294|archive-date=12 August 2010|url-status=dead}}</ref>

Other than the first three models, all [[Chromebook]]s run coreboot.<ref>{{cite web |url=http://www.coreboot.org/Chromebooks |title=Chromebooks |publisher=coreboot |date=16 January 2014 |access-date=17 February 2014 |archive-url=https://web.archive.org/web/20160508225442/https://www.coreboot.org/Chromebooks |archive-date=8 May 2016 |url-status=dead }}</ref> Code from [[Das U-Boot]] has been assimilated to enable support for processors based on the [[ARM architecture|ARM instruction set]].<ref>{{cite web|url=http://blogs.coreboot.org/blog/2011/06/05/gsoc2011week-1-analysis-of-u-boot-arm-boot-code/ |title=GSoC2011(Week 1): Analysis of U-boot ARM boot code &#124; coreboot developer blogs|date=5 June 2011 |access-date=12 April 2014}}</ref>

In June 2019, coreboot began to use the [[NSA]] software [[Ghidra]] for its [[reverse engineering]] efforts on [[Firmware|firmware-specific]] problems following the release of the suite as [[free and open source software]].<ref>{{Cite web |title=Coreboot nutzt NSA-Tool zum Reverse Engineering |url=https://www.golem.de/news/ghidra-coreboot-nutzt-nsa-tool-zum-reverse-engineering-1906-141746.html |access-date=2023-05-04 |website=[[Golem.de]]}}</ref>

== Supported platforms ==
CPU architectures supported by coreboot include [[IA-32]], [[x86-64]], [[ARM architecture family|ARM]], [[AArch64|ARM64]], [[MIPS architecture|MIPS]] and [[RISC-V]]. Supported [[system-on-a-chip]] (SOC) platforms include AMD [[Geode (processor)|Geode]], starting with the Geode GX processor developed for the [[One Laptop per Child|OLPC]]. Artec Group added Geode LX support for its [[ThinCan]] model DBE61; that code was adopted by AMD and further improved for the OLPC after it was upgraded to the Geode LX platform, and is further developed by the coreboot community to support other Geode variants. coreboot can be flashed onto a Geode platform using [[Flashrom (utility)|Flashrom]].

From that initial development on AMD Geode based platforms, coreboot support has been extended onto many AMD processors and chipsets. The processor list includes Family 0Fh and 10h ([[AMD K8|K8]] core), and recently Family 14h ([[Bobcat (microarchitecture)|Bobcat]] core, [[AMD APU|Fusion APU]]). coreboot support also extends to AMD chipsets: [[AMD 690 chipset series|RS690]], [[AMD 700 chipset series|RS7xx]], [[AMD 580 chipset series|SB600]], and SB8xx.

In AMD Generic Encapsulated Software Architecture ([[AGESA]]){{mdashb}}a [[Bootstrapping|bootstrap]] protocol by which system devices on AMD64 mainboards are initialized{{mdashb}}was open sourced in early 2011, aiming to provide required functionality for coreboot system initialization on AMD64 hardware.<ref>{{cite web | title = Technical details on AMD's coreboot source code release | url = http://community.amd.com/community/amd-blogs/business/embedded-systems/blog/2011/02/28/technical-details-on-amd-s-coreboot-source-code-release |publisher =[[Advanced Micro Devices|AMD]] |date=28 February 2011 | archive-url=https://web.archive.org/web/20140325040416/http://community.amd.com/community/amd-blogs/amd-business/blog/2011/02/28/technical-details-on-amd-s-coreboot-source-code-release | archive-date=25 March 2014 | access-date=1 February 2016 | url-status=dead }}</ref> However, as of 2014 such releases never became the basis for future development by AMD, and were subsequently halted.<ref>{{cite web|url=https://mail.coreboot.org/pipermail/coreboot/2014-November/078892.html |title=AMD's binary-only AGESA libraries | first=Bruce |last=Griffith |date=2014-11-05 |access-date=2017-05-08 }}</ref>

Devices that could be preloaded with coreboot or one of its derivatives include:  

;[[Lenovo]]/[[IBM]]:The Libreboot T400 and X200 (rebranded ThinkPad T400 and X200, respectively, available from Minifree, previously known as Gluglug).<ref>{{cite web |title=Minifree |url=http://minifree.org/ |archive-date=25 September 2015 |access-date=24 September 2015 |website=Ministry of Freedom - Products|archive-url=https://web.archive.org/web/20150925120409/http://minifree.org/ }}</ref><ref>{{cite web|url=https://www.fsf.org/resources/hw/endorsement/gluglug|title=The Gluglug|work=fsf.org|access-date=23 September 2015|archive-url=https://web.archive.org/web/20150923124716/https://www.fsf.org/resources/hw/endorsement/gluglug|archive-date=23 September 2015|url-status=dead}}</ref>

;Artec Group: [[ThinCan]] models DBE61, DBE62 and DBE63, and fanless server/router hardware manufactured by [[PC Engines]].<ref>{{cite web|url=https://github.com/pcengines/coreboot|title=pcengines/coreboot|website=[[GitHub]] |access-date=16 September 2019}}</ref>  
; [[Purism (company)|Purism]]: [[Librem]] laptops come with coreboot.<ref>{{cite web |title=coreboot Firmware on Purism Librem devices |url=https://puri.sm/coreboot/ |access-date=19 June 2020}}</ref><ref>{{cite web |title=Purism Laptops To Use 'Heads' Firmware To Protect Against Rootkits, Tampering (Updated) |date=27 February 2018 |url=https://www.tomshardware.com/news/purism-heads-rootkit-tampering-protection,34128.html |access-date=19 June 2020}}</ref>
;Others
:Some [[System76]] PCs use coreboot TianoCore firmware, including open source [[Embedded Controller]] firmware.
:Dasharo offers an alternative coreboot-based firmware distribution for computers from [[Micro-Star International|MSI]], [[NovaCustom]] and [[Nitrokey]], among others.<ref>{{cite web |title=New Dasharo v1.1 Firmware For The MSI Z690 Board - Phoronix |date=22 November 2022 |url=https://www.phoronix.com/news/Dasharo-1.1-MSI-Z690-Board |access-date=27 October 2023}}</ref><ref>{{cite web |title=NovaCustom-Dasharo October-2023 Firmware Update (ADL v1.7.0 & TGL v1.5.0) - NovaCustom|date=19 September 2023 |url=https://configurelaptop.eu/novacustom-dasharo-october-2023-firmware-update-adl-v1-7-0-tgl-v1-5-0/ |access-date=27 October 2023}}</ref><ref>{{cite web |title= The NitroPC Pro is Qubes-Certified! - Nitrokey |date=24 September 2023 |url=https://www.nitrokey.com/news/2023/nitropc-pro-qubes-certified |access-date=27 October 2023}}</ref>
:StarLabs Systems use coreboot firmware, as an alternative.<ref>[https://fossbytes.com/starbook-mk-v-from-star-labs-review/ Starbook mk v review] - fossbytes </ref>
:Some [[Tesla Model 3]] cars have adopted [[Ryzen Embedded]] or [[Intel Atom]] processor on the car computer, and adopted coreboot as the bootloader.{{citation needed|date=February 2025}}

== Design ==
Coreboot typically loads a [[Linux kernel]], but it can load any other [[standalone program|stand-alone]] [[Executable and Linkable Format|ELF]] executable, such as [[iPXE]], [[gPXE]] or Etherboot that can boot a Linux kernel [[Network booting|over a network]], or [[SeaBIOS]]<ref>[http://www.coreboot.org/SeaBIOS SeaBIOS] (previously known as LegacyBIOS) is an open-source legacy BIOS implementation</ref> that can load a Linux kernel, [[Windows 2000]] and later, and BSDs; Windows 2000/[[Windows XP|XP]] and [[OpenBSD]] support was previously provided by ADLO.<ref>{{Cite web|url=http://www.coreboot.org/ADLO|archiveurl=https://web.archive.org/web/20101125130605/http://www.coreboot.org/ADLO|url-status=dead|title=coreboot Add-on Layer (ADLO)|archivedate=25 November 2010}}</ref><ref>{{cite web |url=http://www.missl.cs.umd.edu/sebos_phase2.html |title=SEBOS, Security Enhanced Bootloader for Operating Systems, Phase 2 |archive-url=https://web.archive.org/web/20070619101948/http://www.missl.cs.umd.edu/sebos_phase2.html |archive-date=19 June 2007 |url-status=dead}} - adding PC BIOS Services to coreboot via Bochs BIOS</ref> coreboot can also load a [[Kernel (operating system)|kernel]] from any supported device, such as Myrinet, Quadrics, or SCI [[Computer cluster|cluster]] interconnects. Booting other kernels directly is also possible, such as a [[Plan 9 from Bell Labs|Plan 9]] kernel. Instead of loading a kernel directly, coreboot can pass control to a dedicated boot loader, such as a coreboot-capable version of [[GNU GRUB]] 2.

Coreboot is written primarily in [[C (programming language)|C]], with a small amount of [[assembly code]]. Choosing C as the primary programming language enables easier [[code audit]]s when compared to contemporary PC BIOS that was generally written in assembly,<ref>{{cite web |url=https://phoenixts.com/blog/uefi-vs-legacy-bios/ |title=Comparison of UEFI and legacy BIOS}} pronouncing that same advantage for UEFI</ref> which results in improved security. There is build and runtime support to write parts of coreboot in [[Ada (programming language)|Ada]]<ref>{{cite web |url=https://review.coreboot.org/cgit/coreboot.git/commit/src/lib/gnat?id=e0ed9025cf7453212e5e5a845e34e0b7ecfa3eb9 |title=commit}} adding that support</ref> to further raise the security bar, but it is currently only sporadically used. The source code is released under the [[GPL version 2|GNU GPL version 2]] license.

Coreboot performs the absolute minimal amount of hardware initialization and then passes control to the [[operating system]]. As a result, there is no coreboot code running once the operating system has taken control. A feature of coreboot is that the [[x86]] version runs in [[32-bit]] mode after executing only ten instructions<ref>{{Cite web |url=http://lxr.linux.no/coreboot-v3+r777/arch/x86/geodelx/stage0.S |title=coreboot v3 early startup code |access-date=17 August 2008 |archive-url=https://archive.today/20120710041412/http://lxr.linux.no/coreboot-v3+r777/arch/x86/geodelx/stage0.S |archive-date=10 July 2012 |url-status=dead }}</ref> (almost all other x86 BIOSes run exclusively in [[16-bit]] mode). This is similar to the modern [[UEFI]] firmware, which is used on newer PC hardware.

=== Initializing DRAM ===
The most difficult hardware that coreboot initializes is the [[Memory controller|DRAM controller]]s and [[Dynamic random-access memory|DRAM]]. In some cases, technical documentation on this subject is [[Non-disclosure agreement|NDA]] restricted or unavailable. RAM initialization is particularly difficult because before the RAM is initialized it cannot be used. Therefore, to initialize DRAM controllers and DRAM, the initialization code may have only the CPU's [[Processor register|general purpose registers]] or Cache-as-RAM as temporary storage.

romcc, a [[C (programming language)|C]] [[compiler]] that uses registers instead of RAM, eases the task. Using romcc, it is relatively easy to make [[System Management Bus|SMBus]] accesses to the [[Serial presence detect|SPD]] ROMs of the DRAM [[DIMM]]s, that allows the RAM to be used.

With newer x86 processors, the processor cache can be used as RAM until DRAM is initialized. The processor cache has to be initialized into Cache-as-RAM<ref>{{cite web |url=http://rere.qmqm.pl/~mirq/cache_as_ram_lb_09142006.pdf |title=CAR: Using Cache as RAM in Linux BIOS |date=15 January 2009 |access-date=25 February 2014 |author1=Yinghai Lu |author2=Li-Ta Lo |author3=Gregory R. Watson |author4=Ronald G. Minnich |publisher=qmqm.pl |archive-url=https://web.archive.org/web/20160303223305/http://rere.qmqm.pl/~mirq/cache_as_ram_lb_09142006.pdf |archive-date=3 March 2016 |url-status=dead }}</ref><ref>{{Cite web|url=http://www.coreboot.org/images/6/6c/LBCar.pdf|title=A Framework for Using Processor Cache as RAM (CAR)}}</ref> mode as well, but this needs fewer instructions than initializing DRAM. Also, the Cache-as-RAM mode initialization is specific to CPU architectures, thus more generic than DRAM initialization, which is specific to each chipset and mainboard.

For most modern x86 platforms, closed source binary-only components provided by the vendor are used for DRAM setup.  For Intel systems, FSP-M is required, while AMD has no current support. Binary AGESA is currently used for proprietary UEFI firmware on AMD systems, and this model is expected to carry over to any future AMD-related coreboot support.<ref>{{cite web|url=https://mail.coreboot.org/pipermail/coreboot/2014-November/078892.html|title=[coreboot] AMD's binary-only AGESA libraries|last=Griffith|first=Bruce|date=5 November 2014|access-date=2019-09-08}}</ref>

== Developing and debugging coreboot ==
[[File:Hacking Coreboot.jpg|thumb|Hacking coreboot at Denver 2008 summit.]]

There are also CPU [[emulator]]s that either replace the [[Central processing unit|CPU]] or connect via a [[JTAG]] port, with the Sage SmartProbe<ref>{{Cite web|url=http://www.se-eng.com/|archiveurl=https://web.archive.org/web/20110315080000/http://www.se-eng.com/|url-status=usurped|title=Sage Electronic Engineering - SmartProbe JTAG debugger, Sage EDK, coreboot and Embedded Systems and Software Engineering|archivedate=15 March 2011|website=www.se-eng.com}}</ref><ref>{{cite web | url=http://www.loper-os.org/?p=1887 | title=Sage SmartProbe FAQ | publisher=S.Datskovskiy | access-date=30 April 2021}}</ref> being an example. Code can be built on, or downloaded to, BIOS emulators rather than flashing the BIOS device.

== Payloads ==
[[File:Coreboot+seaBIOS+on-x60.JPG|thumb|upright|SeaBIOS payload running on a Lenovo [[ThinkPad]] X60]]

coreboot can load a payload, which may be written using the {{Mono|libpayload}} helper library. Existing payloads include the following:
* Depthcharge is used by Google for [[ChromeOS]]<ref>{{cite web
 | url = https://docs.google.com/presentation/d/1pH8ltQ3cGKy9dRaTxHtZbA50QLZCw6HE8LDoi1y_gcs/pub?start=false&loop=false&delayms=3000#slide=id.p
 | title = Depthcharge: The ChromeOS bootloader
 | access-date = 26 October 2015
 | website = docs.google.com
}}</ref>
* A branch of [[Das U-Boot]] was used by Google for [[ChromiumOS]] in the past<ref>{{cite web
|url=https://groups.google.com/a/chromium.org/group/chromium-os-reviews/browse_thread/thread/8daf5b5ffe245c1d/0eda7e414407a923
|title=Modify u-boot code to allow building coreboot payload. &#91;chromiumos/third_party/u-boot-next : chromeos-v2011.03&#93;
|date=24 July 2011
}}</ref>

== {{Anchor|European Coreboot Conference|ECC}} European Coreboot Conference ==
One physical meeting is the European Coreboot Conference which was organized in October 2017 and lasted for three days.

=== Conference history ===
{| class="wikitable" style="font-size:90%;"
! Event and year !! Date !! Host city !! Venue !! Resources !! Themes
|-
| ECC2017 || 26.10. – 29.10 || [[Bochum]], Germany || [[Ruhr University Bochum|RUB]] Convention Center || https://ecc2017.com ||
|-
|}

== {{Anchor|LIBREBOOT}}Variants ==

coreboot has a number of variants from its original code base each with slightly different objectives:.
* [[Libreboot]] - A variant with a primary focus to remove some<ref>{{Cite web |date=2023-11-01 |title=Binary Blob Reduction Policy |url=https://libreboot.org/news/policy.html |access-date=2023-11-01 |archive-url=https://web.archive.org/web/20231101164256/https://libreboot.org/news/policy.html |archive-date=1 November 2023 }}</ref> binary blobs.
* osboot - A variant similar to Libreboot that scrapped its only some blobs policy to increase hardware support and stability.<ref>{{Cite web |date=2021-03-15 |title=osboot project |url=https://osboot.org/ |access-date=2023-05-26 |archive-url=https://web.archive.org/web/20210315131008/https://osboot.org/ |archive-date=15 March 2021 }}</ref> Merged with libreboot as of November 2022.<ref>{{Cite web |date=2022-12-19 |title=Libreboot – Osboot is now part of Libreboot |url=https://libreboot.org/news/merge.html |access-date=2023-05-26 |archive-url=https://web.archive.org/web/20221219054437/https://libreboot.org/news/merge.html |archive-date=19 December 2022 }}</ref>
* MrChromebox has developed a modified version of coreboot for ChromeOS based devices.<ref>{{Cite web |date=2022-04-17 |title=How to install ChromeOS Flex on a Chromebook |url=https://www.androidpolice.com/install-chromeos-flex-chromebook-explainer/ |access-date=2023-05-30 |website=Android Police |language=en}}</ref>
* GNU Boot - A variant with a primary focus to remove all binary blobs.<ref>{{Cite web |date=2023-10-30 |title=GNU Boot Summary |url=https://savannah.gnu.org/projects/gnuboot |access-date=2023-10-30 |archive-url=https://web.archive.org/web/20231030210812/https://savannah.gnu.org/projects/gnuboot/ |archive-date=30 October 2023 }}</ref>
* Canoeboot<ref>{{Cite web |date=16 November 2023 |title=Canoeboot project |url=https://canoeboot.org/ |access-date=16 November 2023 |archive-url=https://web.archive.org/web/20231116233556/https://canoeboot.org/ |archive-date=16 November 2023 }}</ref>
* Dasharo - A distribution based on coreboot developed by 3mdeb.<ref>{{Cite web | date=2024-01-29 | title=3mdeb Sp. z o.o. — Embedded Firmware development consultancy | url=https://3mdeb.com | access-date=2024-02-16 | archive-url=https://web.archive.org/web/20240216093245/https://3mdeb.com | archive-date=2024-02-16 }}</ref> They aim to make it easy for manufacturers to ship products with coreboot.<ref>{{Cite web | date=2023-10-22 | title=Dasharo • GitHub | url=https://github.com/Dasharo | access-date=2024-02-16 | archive-url=https://web.archive.org/web/20240216085150/https://github.com/Dasharo | archive-date=2024-02-16 }}</ref><ref>{{Cite web | date=2024-02-09 | title=About Dasharo - Dasharo Universe | url=https://docs.dasharo.com | access-date=2024-02-16 | archive-url=https://web.archive.org/web/20240216090043/https://docs.dasharo.com/ | archive-date=2024-02-16 }}</ref>
* Skulls - A variant aimed at ease of installation.<ref>{{Citation |last=Kepplinger-Novakovic |first=Martin |title=merge/skulls |date=2024-05-28 |url=https://github.com/merge/skulls |access-date=2024-05-29}}</ref>
* Heads - A variant aimed at physical security and usage of free software, recommended for use with [[QubesOS]].<ref>{{Cite web |title=About Heads |url=https://osresearch.net/ |access-date=2024-05-29 |website=Heads |language=en-US}}</ref><ref>{{Citation |title=linuxboot/heads |date=2024-05-28 |url=https://github.com/linuxboot/heads |access-date=2024-05-29 |publisher=LinuxBoot}}</ref>{{Citation needed|date=July 2024|reason=The documentation and sources linked dont say that it is recommended for use with qubesOS}}
* oreboot - a fork rewritten in Rust<ref>{{Citation |title=oreboot/oreboot |date=2025-03-27 |url=https://github.com/oreboot/oreboot |access-date=2025-03-31 |publisher=oreboot}}</ref>

== See also ==
{{Portal|Free and open-source software}}
* [[Beowulf cluster]]
* [[LinuxBoot]]
* [[Open-source hardware]]
* [[Rapid Boot]]

== References ==
{{Reflist}}

== Further reading ==
* [https://developer.ibm.com/articles/l-linuxboot/ Inside the Linux boot process], by M. Jones, IBM
* [https://web.archive.org/web/20170104233908/https://www.ibm.com/developerworks/linux/library/l-bios/ Open BIOSes for Linux], by Peter Seebach (archive only)
* [https://web.archive.org/web/20070110135736/http://www.linux.com/article.pl?sid=06%2F11%2F30%2F199208 LinuxBIOS ready to go mainstream], by Bruce Byfield
* [https://lkml.org/lkml/2007/2/21/490 First desktop motherboard supported by LinuxBIOS: GIGABYTE M57SLI-S4], by Brandon Howard
* [https://web.archive.org/web/20070928142218/http://ftp.belnet.be/mirrors/FOSDEM/2007/FOSDEM2007-LinuxBios.ogg Video recording of Ron Minnich's LinuxBIOS talk from FOSDEM 2007]
* [http://www.linuxjournal.com/magazine/coreboot-your-service Coreboot Your Service], [[Linux Journal]], October 2009
* [https://media.ccc.de/search?q=Peter+Stuge media.ccc.de - Search for "Peter Stuge"]

== External links ==
* {{commonscatinline}}
* {{Official website}}

{{Firmware and booting}}

[[Category:Custom firmware]]
[[Category:Firmware]]
[[Category:Free BIOS implementations]]
[[Category:Software related to embedded Linux]]