I never managed to build working normal image for epia-m though. Fallback works fine, and vga bios too. The only odd behaviour is that my epia-m2 has about 12sec delay before it runs the coreboot image.
here's my config.lb: (57344 is my vga bios rom size)
------------------------------------------------------
target via_epia-m mainboard via/epia-m option MAXIMUM_CONSOLE_LOGLEVEL=8 option DEFAULT_CONSOLE_LOGLEVEL=8 option CONFIG_CONSOLE_SERIAL8250=1 option CONFIG_CONSOLE_VGA=1 option ROM_SIZE=0x40000-57344 option HAVE_OPTION_TABLE=1 option CONFIG_ROM_PAYLOAD=1 option HAVE_FALLBACK_BOOT=1 option CONFIG_COMPRESSED_PAYLOAD_NRV2B=0 option _RAMBASE=0x00004000 option FALLBACK_SIZE=0x40000-57344
romimage "fallback" option USE_FALLBACK_IMAGE=1 option ROM_IMAGE_SIZE=0x10000 payload /boot/filo/filo.elf end
buildrom ./coreboot.rom ROM_SIZE "fallback" ----------------------------------------------------------
On Sat, 2008-03-15 at 18:56 +0100, Uwe Hermann wrote:
On Sat, Mar 15, 2008 at 07:59:11PM +0530, jtd wrote:
What is the purpose of fallback.
It's a second, fallback, version of coreboot and payload that could be used for recovery.
It's not mandatory but is usually enabled by default.
Payload: 78064 coreboot: 65536 ROM size: 196608 Left space: 53008
That's one possibility to solve this, if you don't want/need two images )normal/fallback). But it's usually enough to make your FILO smaller, e.g. by disabling all filesystem support you don't need in FILO's 'Config' file, e.g. XFS, Minix, ReiserFS, whatnot.
Uwe.
http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org