| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |\ |
|
| |/
|
|
| |
This modification has been made to both build systems.
|
| |\ |
|
| | | |
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| | |
The SeaGRUB floppy image has a FAT12 filesystem and GRUB needs
to be able to read it in order to load modules stored there.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Related issue #553
Determining the byte offset of core.img on the SeaGRUB floppy
is accomplished using grub_bo(), though it is memory bound as it
requires reading hex dumps for the pattern and comparand into memory.
The blocklists that are stored in the boot record and core.img are
sector numbers. Of particular note is the blocklist written
to core.img is always the location of its *second*
sector--not the first.
Blocklists are used because floppy disks DO NOT have an MBR or
MBR gap as the filesystem spans the entire disk. Consequently, the
core.img cannot be stored in the usual ~1MiB gap. Unfortunately,
using blocklists means they will have to be updated whenever
core.img is moved.
New functions added to grub-helper:
* grub_bo
* grub_bo_dump
* grub_bo_search
* grub_blocklist_format
* grub_blocklist_generate
* grub_floppy_image_make_bootable
* grub_floppy_image_update_blocklists
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Related issue #553
Previously, the GRUB boot image and core image were concatenated
together and padding added to create a (pseudo) floppy image.
However, testing revealed that GRUB has issues dynamically loading
modules from $prefix if $prefix is not located on the same device
from which GRUB booted.
In order to get around this issue, a proper 2.88MiB floppy image is
created using mkfs.fat with GRUB modules copied to directories on
the filesystem (i.e, /boot/grub/i386-pc). The 2.88MiB filesystem
size is necessary to be able to fit all modules onto the image.
New functions added to grub-helper:
* grub_floppy_image_mmd (create directories on image using mtools mmd)
* grub_floppy_image_mcopy (copy files to image using mtools mcopy)
|
| |\ |
|
| |/
|
|
|
| |
Libreboot's build system is neither fully-automated nor does it
perform any automated installations.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The fc-lang symlink has been added to the .gitignore file in order
to allow creating the symlink once after the initial download of
dejavu-fonts. This avoids the otherwise necessary step of
recreating the symlink before each build (as it could have been
removed by the project's clean() action).
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The path contained in the symlink has been made relative for
reproducibility reasons.
Also, it just makes more sense to create the symlink during the
download() action vs. build(). The `-f` flag was added to avoid
an error if the link already exists (i.e., download() has been
executed previously).
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the dejavu-fonts script pulled in the latest versions
of UnicodeData.txt and Blocks.txt files from
https://www.unicode.org/Public/UNIDATA/ which are unversioned.
This is an issue because the files at this URI will change over time
as new UCD versions are released, making reproducible builds of
dejavu-fonts impossible.
The solution to this issue is to simply download the requisite files
from https://www.unicode.org/Public/$ucd_version/ucd/ where
$ucd_version is the version specified in
projects/dejavu-fonts/configs/unicode/ucd-version
|
| |/
|
|
|
|
|
|
|
| |
fontforge was not able to create fonts in a reproducible manner
until upstream revision 69e561773b91e37096a855f0353b1d6781a61250
Requiring at minimum a fontforge built from source on 2017-12-20
(the date the aforementioned revision was made) ensures that dejavu
fonts are reproducible in Libreboot's build system.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
(fd0) should be the proper device for SeaGRUB. $prefix is set using
(fd0) as the device considering modules will be placed onto the
floppy image--not in CBFS.
grub.cfg is still sourced from (cbfsdisk)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Module "biosdisk" is necessary for GRUB to boot from the floppy
image we're working to create. If this module is not included in
core.img it will simply not load.
Module "minicmd" has been added in order to provide the commands
"lsmod" and "rmmod" which are useful for listing loaded modules
and unloading them, respectively (especially great for testing).
|
| | |
| |
| |
| |
| | |
All modules listed in a given target's modules-minimal file are
preloaded so there's no need to specifically load any.
|
| |\ \ |
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
|
| | | |
| | |
| | |
| | |
| | | |
If quoted and $bootstrap_flag expands to an empty string, make
interprets it as an invalid file name and errors out.
|
| | | |
| | |
| | |
| | |
| | | |
Paul Kocialkowski was not retained as the original author due
to the triviality of the patch.
|
| | |/
| |
| |
| |
| |
| |
| | |
The revision currently used has an issue building crossgcc due to
a libelf bug. Upstream no longer depends on libelf when building
crossgcc (since afda56e1ad8719a1) so using a more recent revision
sidesteps this issue.
|
| |\ \
| |/
|/| |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The cbfs module must be loaded before trying to source grub.cfg
from CBFS, for obvious reasons.
The test module is bundled into all images in order to avoid the
situation where grub gets stuck in a loop trying to locate the
module during parsing of grub.cfg. This could happen if a user
removes the module or moves it, so it's best to avoid a brick
by just bundling it into the image.
For the bios target, biosdisk has been removed as it doesn't seem
to provide any benefit and memdisk has been added to eliminate
an error printed by GRUB upon load.
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The only difference between the previous "bios" and "vgabios"
targets was whether or not a VGA BIOS binary was built along with
SeaBIOS.
It seemed needless to compile twice in the event that you
want both the SeaBIOS payload and its VGA BIOS when you can compile
once and make the decision yourself whether to use the produced
vgabios.bin
|
| |/
|
|
|
|
| |
New options enabled (set to their default values):
CONFIG_NVME=y
CONFIG_SERCON=y
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
Z61t ROMs can now be built with either SeaBIOS or GRUB as
a default payload, e.g.:
'./libreboot build coreboot z61t textmode 2mb seabios'
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
2MiB flash is the default for this board. A 16MiB config is
included for those looking to modify their board with a larger flash
chip.
Also, text mode is the only display mode available for this board;
as such, inclusion of the textmode subtarget serves only to
explicitly indicate the display mode when packaging ROMs upon
release.
Z61t Coreboot ROMs can be built with, e.g.:
'./libreboot build coreboot z61t textmode 2mb'
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This function will return the correct build path for libpayload
built for depthcharge targets nyan and veyron. Without this
function, and using project_build_path() instead, LIBPAYLOAD_DIR
would be set to "$root/$BUILD/libpayload-depthcharge-nyan-big"
instead of the proper "$root/$BUILD/libpayload-depthcharge-nyan",
for example.
|
| |/
|
|
|
| |
There's no need to build for each supported veyron model since the
libpayload veyron config is just for veyron in general.
|
| |\ |
|
| |/ |
|
| |\ |
|
| | | |
|
| |\ \ |
|
| |/ / |
|
| |\ \ |
|
