This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see . */ ?> Download <?php echo $lbProjectName; ?>

" />

Download

Information about these releases can be found at ../docs/release.html. Documentation can be found at ../docs/index.html. A copy of /docs/ can also be found in the release archives.

Back to home page

GPG signing key

Download the key:
$ gpg --recv-keys

You can verify the downloaded archives as follows:
$ for signature in $(ls *.sig); do gpg --verify $signature; done

HTTP mirrors

Download libreboot from one of these mirrors.

FTP mirrors

Rsync mirrors (for mirroring )

Create a directory in your web server document root (e.g. /), and add one of these to your crontab:

0) { ?>

Main rsync mirror:

$ rsync -avxP --delete --stats /path/to/docroot//

1) { ?>

Backup rsync mirrors:

$ rsync -avxP --delete --stats /path/to/docroot//

No mirrors available yet.

Are you running a mirror? Contact the project (details are on the home page), and the link will be added here.

Git repositories (development)

The git repositories are intended for developing . ROM images built from the git repository are untested, and therefore not recommended for general use (you should assume that they will brick your computer).

Snapshots (preview releases) of the git repository can be found at ../git/.

Documentation for from git can be found in the git repository itself (under /docs/), or a live version can be found at ../gitdocs/index.html.

How to download

Firmware (coreboot distribution):
$ git clone

website:
$ git clone

Backup repositories can be found at #gitbackup.

Submitting patches to

The git documentation describes how to use git.

Make sure that you configured git so that your name and email address appear in the commits that you create:
$ git config --global user.name "Your Name"
$ git config --global user.email your@emailaddress.com

The following is also useful:
$ git config --global core.editor nano
$ git config --global color.status auto
$ git config --global color.branch auto
$ git config --global color.interactive auto
$ git config --global color.diff auto

Clone the git repository, and make your desired changes. You can make one or several commits (as many as you like). Generally speaking, you should create separate commits on top of each other, for each kind of change.

Once you have made your change(s), you can use this to check the status:
$ git status

Make sure to update all relevant copyright license headers. In source files or scripts, these are usually mentioned at the top, or at the bottom in documentation. Releasing your change under the same license that the original file used is usually simpler. If you are submitting new files, make sure to use a free license (note: the project will not accept documentation under the GNU Free Documentation License, because we do not want to endorse or support the Invariant clauses that this license allows. Changes submitted under this license will be rejected, even if it contains no Invariant sections).

The status command will show any untracked files that you have. Add them using git add path/to/file. You should also add any other files that are listed as modified in the git status. If there are deleted files in the git status, you can use git rm path/to/file. As long as you have added all the untracked files, it is generally easier to use:
$ git commit -a
(instead of git commit)

If you need to make a change to the current commit, you can do so with:
$ git commit --amend
or:
$ git commit -a --amend

In your local git tree, you can use this to check your commits:
$ git log

Shortened git logs showing the short commit ID and the commit title, plus info about what branch you are on, and where all your remotes/heads are:
$ git config --global --add alias.lol "log --graph --decorate --pretty=oneline --abbrev-commit --all"
From then on, you can use:
$ git lol
This is like git log, but on steroids.

Method 1: host a repository

One way of contribiting a patch for review is to host a repository containing your modified branch. Give the checkout details to the project, along with information on which commits in what branch contain your changes. Contact the project using the details on the home page.

Method 2: git format-patch -N

Use this method (replace N with the number of commits that you made) and send the .patch files to the project, along with details on what branch and revision these were made on top of. Contact the project using the details on the home page.

Backup repositories

Generally speaking, you should use the main repositories. These repositories are provided as backups, in case the main repositories are down.

Firmware (coreboot distribution)

$ git clone "; ?>

website

$ git clone "; ?>