FILO - Revision history

PatrickGeorgi: /* Building */ svn bad. git good.

2013-03-20T18:35:51Z

‎Building: svn bad. git good.

2012-06-22T09:35:59Z

Removed obsolete FILO-0.5 subversion link

2012-06-21T15:41:28Z

Switch from Subversion to Git commands and links

2011-04-03T21:45:38Z

‎Installation: renamed to "Building", removed duplicate lines and added a build script

2011-04-03T21:21:21Z

Making all clear

2010-08-04T14:35:22Z

2010-08-03T16:30:39Z

2010-08-03T16:15:05Z

‎Requirements

2010-08-03T16:14:43Z

‎Requirements

2010-04-22T18:29:41Z

+example

@@ Line 86: / Line 86: @@
    $ ./build.sh
-Here is the short listing how to build FILO from svn
+Here is the short listing how to build FILO from git
   cd coreboot/payloads
   git clone http://review.coreboot.org/p/filo.git

← Older revision		Revision as of 09:35, 22 June 2012
Line 12:		Line 12:

	$ git clone http://review.coreboot.org/p/filo.git		$ git clone http://review.coreboot.org/p/filo.git
−
−	~~Alternatively you may still download the obsolete filo 0.5.6 release at~~
−
−	~~$ svn co svn://coreboot.org/filo/branches/filo-0.5~~

	You can also browse the source code online at		You can also browse the source code online at

@@ Line 9: / Line 9: @@
 == Download FILO ==
-Download the latest version of FILO from Subversion with
+Download the latest version of FILO from Git with
-  $ svn co svn://coreboot.org/filo/trunk/filo
+  $ git clone http://review.coreboot.org/p/filo.git
 Alternatively you may still download the obsolete filo 0.5.6 release at
@@ Line 18: / Line 18: @@
 You can also browse the source code online at
-http://tracker.coreboot.org/trac/filo/browser/trunk
+http://review.coreboot.org/gitweb?p=filo.git
 == Features ==
@@ Line 92: / Line 92: @@
 Here is the short listing how to build FILO from svn
   cd coreboot/payloads
-  svn co svn://coreboot.org/filo/trunk/filo
+  git clone http://review.coreboot.org/p/filo.git
   cd filo
   make config

@@ Line 75: / Line 75: @@
 This will run menuconfig twice -- the first time for libpayload, the second time for FILO.
-== Installation ==
+== Building ==
-Then running make again will build filo.elf, the ELF boot image of FILO.
+Then running make will build filo.elf, the ELF boot image of FILO.
    $ make
-If you are compiling on an AMD64 platform, instead of "make" you need to write
+If you are compiling on an AMD64 platform and compiler complains, instead of "make" you need to write
    $ make CC="gcc -m32" LD="ld -b elf32-i386" HOSTCC="gcc" AS="as --32"
-Use build/filo.elf as your payload of coreboot, or a boot image for
+Use '''build/filo.elf''' as your payload of coreboot, or a boot image for
 [[Etherboot]].
 Alternatively, you can build libpayload and FILO in one go using the build.sh script, with the drawback that you'll get the default options for both of them:
    $ ./build.sh
 == Credits ==

@@ Line 39: / Line 39: @@
 been made to get FILO running on PPC. Contact the [[Mailinglist|coreboot mailinglist]]
 for more information.
 Recent version of GNU toolchain is required to build.
@@ Line 48: / Line 45: @@
 make 3.79.1), Debian/sid (gcc 3.3.2, binutils 2.14.90.0.6,
 make 3.80) and different versions of SUSE Linux from 9.0 to 11.0.
 FILO will use the coreboot crossgcc if you have it built and it can be found.
-FILO uses coreboot's libpayload. It is easiest to locate and build FILO in the coreboot/payloads directory.
+FILO uses coreboot's '''libpayload'''. It is easiest to locate and build FILO in the '''coreboot/payloads''' directory.
 == Preparation ==

@@ Line 57: / Line 57: @@
 == Preparation ==
-This step is not required if you locate FILO in the coreboot/payloads directory. FILO will configure and build libpayload.
+Before you can build FILO, you have to build libpayload.  If your filo directory is located inside the coreboot/payloads directory, you don't have to do anything special.  If for some reason you want to compile FILO of the coreboot/payloads directory, you will need to tell the makefile where libpayload is.  Open filo/Makefile in your favorite text editor and change this line
-You need to compile libpayload (included in coreboot)
+  export LIBCONFIG_PATH := $(src)/../libpayload
-  $ cd ../coreboot/payloads/libpayload
+to match the location of the libpayload directory on your system:
-  $ make defconfig
-  $ make
-  $ make DESTDIR=../../../filo/build install
-  $ cd ../../../filo
-If you are compiling on an AMD64 platform, instead of "make" you need to write
+  export LIBCONFIG_PATH := /home/YOUR_USER_NAME/PATH_TO_COREBOOT/payloads/libpayload
 == Configuration ==
@@ Line 75: / Line 70: @@
    $ make menuconfig
 == Installation ==
@@ Line 80: / Line 77: @@
 Then running make again will build filo.elf, the ELF boot image of FILO.
    $ make
 Use build/filo.elf as your payload of coreboot, or a boot image for

@@ Line 49: / Line 49: @@
 make 3.80) and different versions of SUSE Linux from 9.0 to 11.0.
-On AMD64 for Debian install the gcc-multilib package. FILO will use the coreboot crossgcc if you have it built and it can be found.
+On AMD64 for Debian install the gcc-multilib package.
 == Preparation ==

← Older revision		Revision as of 18:29, 22 April 2010
Line 121:		Line 121:

	* 'boot_devices' can contain a list of boot devices seperated by semicolons. FILO will try to load filo.lst / menu.lst from any of these devices.		* 'boot_devices' can contain a list of boot devices seperated by semicolons. FILO will try to load filo.lst / menu.lst from any of these devices.
		+	Example how to set:
		+	nvramtool -w "boot_devices=hda1:/boot/filo;hdc:"