Download coreboot: Difference between revisions

From coreboot
Jump to navigation Jump to search
(→‎Repositories on coreboot.org: svn bad. git good.)
(71 intermediate revisions by 12 users not shown)
Line 1: Line 1:
= GNU Arch Repository =
__NOTOC__
'''Note: These snapshots are for people, who use Linux as operating system and are able to build software from the source code.'''


There is an experimental [http://www.gnuarch.org/ GNU arch] tree available which is likely to become the main repository soon. You may need to install arch. You can find a tar at ftp://ftp.gnu.org/pub/gnu/gnu-arch/.
There is no ''easy to install package'' for people who want to quickly try out a new BIOS on their computer, yet. However, we provide some images for the [[QEMU]] emulator to test coreboot (and some [[Payloads|payloads]]) on your Linux, Mac OS X, and Windows computers (without having to do any hardware changes). But please note that these images can '''not''' be used on any mainboard, they will only work in [[QEMU]]!


== Anonymous access ==
== Snapshots ==
 
You can check it out as follows (instead of tla you can also use baz):
 
<code><pre>
  % # get gpg key for checking signed archives
  % wget \
      http://wiki.linuxbios.org/data/arch/linuxbios-developers-keyring.gpg
  % gpg --import < linuxbios-developers-keyring.gpg
  % # now do some one time registrations
  % tla my-id "John Doe <doe@example.com>" # Add your email address here
  % tla register-archive \
        ftp://openbios.org/pub/arch/linuxbios@linuxbios.org--devel
  % # now check out the archive
  % tla get linuxbios@linuxbios.org--devel/freebios--devel--2.0 freebios2
</pre></code>
 
== Developer Access ==
 
=== Prerequisites ===
If you want to get write access to the LinuxBIOS repository, you need the following:
 
* GnuPG key (can be created with gpg --gen-key)
* SSH v2 key (can be created with ssh-keygen -t dsa)
 
=== Gentoo users ===
 
If you are running Gentoo you are going to need to `emerge tla`
 
=== Preparation ===
 
* Get the arch key I created for the import from CVS.


  $ wget 'http://wiki.linuxbios.org/data/arch/linuxbios-developers-keyring.gpg'
There is an archive of coreboot snapshots available at [http://qa.coreboot.org/ qa.coreboot.org]. A new tar.bz2 file is created whenever the repository changes.
  $ gpg --import linuxbios-developers-keyring.gpg


*  Prepare GNU arch for LinuxBIOS
= Git =


  # Set your default id:
coreboot has switched to using Git for version control. Please see the [[Git]] page for much useful information on how to work with Git and gerrit in coreboot.
  $ tla my-id "John Doe <doe@example.com>"
 
  # similar to cvs login, tell gnuarch where to find the archive:
  $ tla register-archive sftp://lxbios@openbios.org/srv/arch/linuxbios@linuxbios.org--devel
 
  # prepare gnupg signature checking:
  $ mkdir -p ~/.arch-params/signing
  $ echo "gpg --clearsign" > ~/.arch-params/signing/\=default
  $ echo "gpg --verify-files -" > ~/.arch-params/signing/\=default.check


=== Check out ===
Old subversion repository references that still apply will continue to be kept here.


  $ tla get linuxbios@linuxbios.org--devel/freebios--devel--2.0 freebios2
== Git clone ==


=== Working on the tree ===
coreboot keeps its development tree in a [http://git-scm.com/ Git] repository.


Now you can start editing the files. The following applies for symlinks and directories as well.
=== Anonymous access ===


*  New files are added with
To clone the coreboot repository (ca. 120 MB data as of 04/2012):
  $ tla add filename


* files can also be renamed using:
   $ git clone http://review.coreboot.org/p/coreboot
   $ tla mv fileA fileB
 
* files can also be renamed using:
  $ tla mv fileA fileB


* files can be deleted:
If you want the <span style="color: #ff0000">obsolete, unsupported, and experimental</span> '''coreboot v3''' tree (ca. 18 MB data as of 11/2009):
  $ tla rm file


When you're done editing/patching:
  $ svn co svn://coreboot.org/repository/coreboot-v3


* Look at your changes:
If you want the '''old, unmaintained and unsupported coreboot v1''' tree (ca. 47 MB data as of 10/2008):
  $ tla changes
or
  $ tla changes --diffs


* Check the tree:
  $ svn co svn://coreboot.org/coreboot/branches/coreboot-v1


You can do consistency checks on your tree with:
=== Developer access with write permission ===
  $ tla tree-lint
  $ tla inventory -Bu


Check if your tree is current:
Please see our wiki page about [[Git]] for all the details.
  $ tla missing
 
This will output a list of missing changesets in your local tree, ie:
 
  patch-15
  patch-16
  patch-17
  patch-18
 
In which case you should do a
  $ tla update
before you commit.
 
=== Commiting ===
 
Write a changelog. PLEASE DO NOT CREATE EMPTY CHANGELOG MESSAGES:
  $ $EDITOR $( tla make-log )
 
Commit your local tree
  $ tla commit
 
This will ask you for your gpg passphrase (and possibly your ssh key
password if you set one). Then it will create a new revision in the
repository.


== Source code browsing ==
== Source code browsing ==


You can also [http://www.openbios.org/cgi-bin/viewarch.cgi/linuxbios@linuxbios.org--devel browse the LinuxBIOS arch repository online].
You can browse the coreboot Git repository online using [http://review.coreboot.org/gitweb?p=coreboot.git gitweb] including its [http://review.coreboot.org/gitweb?p=coreboot.git;a=tree tree view] for accessing the files.
 
== Snapshots ==
 
To be done
 
== Source code browsing ==
 
http://www.openbios.org/cgi-bin/viewarch.cgi
 
== Mirroring the repository ==
 
This is very simple. Do:
 
  wget -m ftp://ftp.openbios.org/pub/arch
 
Which gives you a snapshot in time of the archive.
To create a mirror usable by arch:


  tla register-archive linuxbios@linxubios.org--devel-SOURCE ftp://openbios.org/pub/arch/linuxbios@linuxbios.org--devel                                                         
== Repositories on coreboot.org ==
  tla register-archive linuxbios@linuxbios.org--devel ~/{archives}/linuxbios@linuxbios.org--devel
                                                                                                                                                                                                                                                                                                                                                           
  echo gpg --clearsign > ~/.arch-params/signing/=default
  echo gpg --verify-files - > ~/.arch-params/signing/=default.check
  echo linuxbios@linuxbios.org--devel--SOURCE > ~/.arch-params/signing/linuxbios@linuxbios.org--devel


To update the mirror with the most recent contents:
'''coreboot current Git tree:'''
  tla archive-mirror linuxbios@linuxbios.org --devel
* <nowiki>http://review.coreboot.org/coreboot.git</nowiki>


Just don't do this in an account where you plan to commit to the upstream
'''coreboot v1 (obsolete):'''
archive.
* svn://coreboot.org/coreboot/branches/coreboot-v1
* <nowiki>https://svn.coreboot.org/coreboot/branches/coreboot-v1</nowiki>


== Creating a branch you can edit in local archive ==
'''coreboot v3 (obsolete):'''
* svn://coreboot.org/repository/coreboot-v3
* <nowiki>https://svn.coreboot.org/repository/coreboot-v3</nowiki>


  tla tag -S linuxbios@linuxbios.org--devel/freebios--devel--2.0 you@yourarchive/freebios--devel--2.0
'''[[FILO]]:'''
* <nowiki>http://review.coreboot.org/filo.git</nowiki>


== More on tla ==
'''[[Buildrom]]:'''
* svn://coreboot.org/buildrom/
* <nowiki>https://svn.coreboot.org/buildrom/</nowiki>


* http://www.openbios.org/experience/gnuarch.html
'''[[Distributed and Automated Testsystem]]:'''
* http://wiki.gnuarch.org/
* svn://coreboot.org/testsystem
* <nowiki>https://svn.coreboot.org/testsystem/</nowiki>

Revision as of 18:36, 20 March 2013

Note: These snapshots are for people, who use Linux as operating system and are able to build software from the source code.

There is no easy to install package for people who want to quickly try out a new BIOS on their computer, yet. However, we provide some images for the QEMU emulator to test coreboot (and some payloads) on your Linux, Mac OS X, and Windows computers (without having to do any hardware changes). But please note that these images can not be used on any mainboard, they will only work in QEMU!

Snapshots

There is an archive of coreboot snapshots available at qa.coreboot.org. A new tar.bz2 file is created whenever the repository changes.

Git

coreboot has switched to using Git for version control. Please see the Git page for much useful information on how to work with Git and gerrit in coreboot.

Old subversion repository references that still apply will continue to be kept here.

Git clone

coreboot keeps its development tree in a Git repository.

Anonymous access

To clone the coreboot repository (ca. 120 MB data as of 04/2012):

 $ git clone http://review.coreboot.org/p/coreboot

If you want the obsolete, unsupported, and experimental coreboot v3 tree (ca. 18 MB data as of 11/2009):

 $ svn co svn://coreboot.org/repository/coreboot-v3

If you want the old, unmaintained and unsupported coreboot v1 tree (ca. 47 MB data as of 10/2008):

 $ svn co svn://coreboot.org/coreboot/branches/coreboot-v1

Developer access with write permission

Please see our wiki page about Git for all the details.

Source code browsing

You can browse the coreboot Git repository online using gitweb including its tree view for accessing the files.

Repositories on coreboot.org

coreboot current Git tree:

  • http://review.coreboot.org/coreboot.git

coreboot v1 (obsolete):

coreboot v3 (obsolete):

FILO:

  • http://review.coreboot.org/filo.git

Buildrom:

Distributed and Automated Testsystem: