" />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.
GPG signing key
Download the key:
$ gpg --recv-keys
Download the SHA512 manifest and it's corresponding GPG signature for the release that you are using, and put them in a directory. Put the src, util and docs archives in the root of that directory, alongside the SHA512 manifest file. Put your ROM image archives under rom/ in that directory. Put your crossgcc tarballs under crossgcc/ in that directory.
After you've done this, verify the SHA512 checksums:
$ sha512sum -c sha512sum.txt
You can verify the downloaded SHA512 manifest as follows:
$ gpg --verify sha512sum.txt.gpg
HTTP mirrors (releases)
These releases are more rigorously tested. However, they might be out of date compared to the current development snapshots.
These archives are not updated very often, and will not receive any further changes.
Download from one of these mirrors.
The latest release has a version number of , and was released on .
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 . For a list of current tasks in , see ../docs/tasks.html.
Maintenance guides for can be found at ../docs/maintain/index.html and and ../docs/git/index.html.
How to download
Firmware (coreboot distribution):
$ git clone
You might not see a progress bar; it's still cloning, so just be patient.
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
If you are modifying an existing file, make sure to update the copyright license header
in that file; in source files or scripts, this would usually be at the top, and for documentation
it is typically at the bottom of the document. It is good practise to use your real name in the
commit logs.
Example: Copyright (C) 20XX John Doe <john@doe.com>
Generally speaking, using the same license as the file that you are modifying is much simpler. If you are submitting new files, please make sure that they are under a free license (copyleft preferred). You can find a list on https://www.gnu.org/licenses/license-list.html.
The project will not accept documentation released 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 "; ?>
Libreboot includes statically linked executables of utilities built from the libreboot source code. These are built on in Trisquel GNU/Linux. There were links to the Trisquel source ISO here, as a lazy way to provide CCS, but this was inefficient. Archives for only those dependencies that comprise the CCS will be added here later instead. If you need CCS, for now simply contact the libreboot project using the details on the home page, and the source for the version of Trisquel used to build that release (whichever version it is) will be provided. You can also get it on the Trisquel website.