Downloads: Difference between revisions
Jump to navigation
Jump to search
(0.9.9) |
|||
Line 14: | Line 14: | ||
'''Manual installation from source:''' | '''Manual installation from source:''' | ||
If you just want to use the latest stable release, [http://download.flashrom.org/releases/flashrom-0.9. | If you just want to use the latest stable release, [http://download.flashrom.org/releases/flashrom-0.9.9.tar.bz2 download flashrom 0.9.9 (source) here] [http://download.flashrom.org/releases/flashrom-0.9.9.tar.bz2.asc (GPG signature)]. Older releases can be found [http://download.flashrom.org/releases/?C=M;O=D here]. | ||
If you want the latest source code (for developers), check out our code from subversion: | If you want the latest source code (for developers), check out our code from subversion: | ||
Line 134: | Line 134: | ||
= Releases = | = Releases = | ||
* [[Flashrom/0.9.9|flashrom 0.9.9 release notes]] | |||
* [[Flashrom/0.9.8|flashrom 0.9.8 release notes]] | * [[Flashrom/0.9.8|flashrom 0.9.8 release notes]] | ||
* [[Flashrom/0.9.7|flashrom 0.9.7 release notes]] | * [[Flashrom/0.9.7|flashrom 0.9.7 release notes]] |
Revision as of 18:05, 13 March 2016
You can browse the flashrom source code online, or download and install flashrom and/or its source code as explained below.
Installation from source
Requirements:
- pciutils development package (pciutils-dev/libpci-dev/pciutils-devel, depending on OS/distribution)
- zlib development package (zlib1g-dev/zlib-devel, depending on OS/distribution)
- libftdi development package (libftdi-dev), optional support for various external FT2232SPI flashers
- libusb development package (libusb-dev), optional support for various USB-based programmers
- various build utilities like make, gcc etc. (build-essential or similar depending on OS/distribution)
- subversion (if you checkout the source and build manually)
Manual installation from source:
If you just want to use the latest stable release, download flashrom 0.9.9 (source) here (GPG signature). Older releases can be found here.
If you want the latest source code (for developers), check out our code from subversion:
$ svn co svn://flashrom.org/flashrom/trunk flashrom $ cd flashrom $ make # The next step is optional! $ sudo make install
The sudo make install is optional: you can run flashrom from its subversion directory with sudo ./flashrom.
You can also download source code snapshots here.
If you are behind a corporate firewall which does not let the native svn protocol through, you can check out the code over https:
$ svn co https://code.coreboot.org/svn/flashrom/trunk flashrom
Binary packages
IRC nicknames are mentioned in parentheses.
- ALT Linux:
- Installation: ?
- Maintainer: ?
- package overview, bugreports
- Arch Linux:
- Installation: pacman -S flashrom
- Maintainer: Giovanni Scafora
- package overview, bugreports, git repo
- Debian:
- Installation: sudo aptitude install flashrom
- Maintainer: Uwe Hermann (uwe_ / uw3)
- package overview, build logs, more build logs, package popularity, bugreports
- DOS:
- Installation: For instructions on how to cross-compile using Linux see DOS.
- Alternatively, you may find usable DOS binaries in our buildbot archive. However, they are usually untested and not recommended to be trusted blindly.
- DragonFly BSD:
- Installation: pkg_add flashrom
- Maintainer: Jonathan Kollasch (jakllsch)
- ?
- Fedora:
- Installation: sudo yum install flashrom
- Maintainer: Peter Lemenkov
- package overview, bugreports, git repo, build logs, package updates
- FreeBSD:
- Installation from ports: cd /usr/ports/sysutils/flashrom && make install clean
- Installation using a package: pkg_add -r flashrom
- Maintainer: Alexander Logvinov
- The version from subversion's trunk (latest revision while editing is r1416) is usable as well. To checkout and compile the source code you need to install devel/gmake, devel/libpci, devel/subversion and sysutils/dmidecode, either from ports or using "pkg_add -r". The subversion URI is at the top of this page. Compile with "gmake".
- Gentoo:
- Install: emerge flashrom
- Maintainer: Mart Raudsepp (leio), Christian Ruppert (idl0r), Peter Stuge (CareBear\)
- package overview, bugreports, forums, upstream scanner
- Mandriva:
- Installation: urpmi flashrom
- Maintainer: Alexander Khryukin
- svn repo, bugreports
- NetBSD:
- Installation: pkg_add flashrom
- Maintainer: Jonathan Kollasch (jakllsch)
- package overview, netbsdpkgsrc info, CVS repo
- OpenBSD:
- Installation: ?
- Maintainer: ?
- TODO: Are there any ports or binary packages for OpenBSD? Building from source is supported as per README.
- OpenELEC:
- Installation: ?
- Maintainer: Stephan Raue
- git repo
- openSUSE:
- Installation: yast -i coreboot-utils
- Maintainer: Stefan Reinauer (Stepan)
- package overview, flashrom packages, coreboot-utils packages, requests, bugreports
- OpenWRT
- Installation: ?
- Maintainer: ?
- package overview, svn repo
- PC-BSD
- Installation: currently there is no PBI (http://www.pbidir.com/bt/category/sysutils) but the installation instructions to install on FreeBSD can be used. See ftp://ftp.pcbsd.org/pub/handbook/handbook_en_ver8.2.html#__RefHeading__223_1034146141
- Maintainer: ?
- ?
- Source Mage GNU/Linux:
- Installation: cast flashrom
- Maintainer: Quentin Rameau (quinq)
- package files
- T2 SDE
- Installation from source: Emerge-Pkg flashrom
- Installation of binaries: mine -i flashrom-0.9.1.tar.bz2
- Maintainer: ?
- ?
- Ubuntu:
- Installation: sudo aptitude install flashrom
- Maintainer: ?, migration happens automatically or semi-automatically from the Debian package
- package overview
- You can also install daily builds of flashrom's development source from a special PPA. Please note that these are experimental binaries that may or may not be safe to use. We try to do our best to let dangerous bugs not slip into this, but it may sometimes happen. Usually it is safer to use those than very old (<=0.9.2) stable releases.
- Windows:
- Installation: See Windows. Only a limited number of programmers are supported so far.
- There were some attempts to create a full Windows port of the flashrom utility but none really succeeded and made it into the source code.