| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This is only used as a resource for building DejaVu fonts so there's
no need to do any building or installing with this project.
fontconfig could be cloned into DejaVu fonts' sources instead but
it'd be easier to maintain by keeping it as a separate project.
|
| |
|
|
|
|
| |
Without patching .gitignore, when `git clean -df` is run it will
remove files UnicodeData.txt and Blocks.txt. These files should be
preserved between builds to avoid needless refetching.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Will be used to build the DejaVu Sans Mono ttf file from source in
order to: cut down on the number of binary files added to the repo;
build from source wherever possible any software included in the final
Libreboot ROM.
These fonts take a non-significant amount of time to build and are
light on dependencies (fontforge, libfont-ttf-perl) so this shouldn't
be an issue.
|
| |
|
|
|
|
|
|
|
|
|
| |
'font-file' contains the filename (not path) of the font to use when
making a PF2-format GRUB font.
'font-project' contains the name of the project which built the
original font file.
These files are necessary to avoid hard-coding the font and/or the
path to the font as an argument to grub-mkfont.
|
| |
|
|
|
| |
A more flexible way of handling font files will be introduced in later
commits.
|
| |
|
|
|
|
| |
The idea is to build a font from source and then make a PF2 format
file from it using grub-mkfont. This cuts down on the number of
binary files committed to history in the repository.
|
| |
|
|
|
| |
Saving typing on one letter isn't really worth the trade-off in
readability.
|
| | |
|
| |
|
|
|
|
|
| |
Since backgrounds aren't included in the GRUB image it would make more
sense to move them to the GRUB install directory at
projects/grub/install/corebootfb instead (textmode ROMs won't have a
background image included, for obvious reasons).
|
| |
|
|
| |
Plurality is nice, sometimes.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Keylayouts are now compiled as part of the build process--keeping
binary keylayouts in the repo is unnecessary as a result.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
grub-mklayout was the intended program to use for generating compiled
GRUB keylayouts. Somewhere along the way grub-kbdcomp was erroneously
substituted in its place.
|
| |
|
|
|
|
|
| |
By building keymaps whenever a GRUB image is produced, there will be a
significant reduction in total time spent compiling Libreboot ROMs.
The previous build process for keymaps was hugely inefficient.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As with the BIOS/Coreboot targets, the modules listed in this file
will later be added to CBFS in order to avoid issues inherent to
bundling modules into the GRUB image.
Several modules have been excluded from the install list for reasons
of non-applicability to UEFI GRUB; namely:
* cmosdump
* cmostest
* efiemu
* mda_text
* pci
|
| |
|
|
|
|
|
| |
As with the BIOS/Coreboot targets' modules-minimal files, this file
lists the minimum necessary to complement a working, bootable image so
that it can read from other devices in addition to halting/rebooting
the machine.
|
| |
|
|
|
|
| |
Since GRUB images will be produced on a target-specific basis, the
target will need its own copy of the modules to include in either the
GRUB image itself or CBFS.
|
| |
|
|
|
|
|
|
|
| |
The added files (and, later, module lists) are mostly the same as
their BIOS/Coreboot targets counterparts because the base
configuration for each GRUB image produced is intended to be quite
similar (for greater malleability down the line).
The purpose of each file remains the same.
|
| |
|
|
|
| |
Without these modules, the GRUB Coreboot target image can't access
devices other than cbfsdisk. Adds support for HDD/USB drives.
|
| | |
|
| |
|
|
|
|
| |
As with the BIOS target, the modules listed in this file will later be
added to CBFS in order to avoid issues inherent to bundling modules
into the GRUB image.
|
| |
|
|
|
|
|
| |
As with the BIOS target's modules-minimal file, this file lists the
minimum necessary to complement a working, bootable image so that it
can read from other devices in addition to halting/rebooting the
machine.
|
| |
|
|
|
|
| |
Since GRUB images will be produced on a target-specific basis the
target will need its own copy of the modules to include in either the
GRUB image itself or CBFS.
|
| |
|
|
|
|
|
|
| |
The added files are mostly the same as their BIOS target counterparts
because the base configuration for each GRUB image produced is
intended to be quite similar (for greater malleability down the line).
The purpose of each file remains the same.
|
| |
|
|
|
|
| |
The produced GRUB image now has a more generalized name for
applicability to disparate platform builds (e.g. EFI vs. bootable
floppy image).
|
| |
|
|
|
| |
'keymap' isn't included as a target yet due to it needing further
work done to it.
|
| |
|
|
|
|
|
|
| |
The previous build function definition only allowed for a
one-size-fits-all build process for any given target. The function
was rewritten to allow for different build processes based on the
target passed to it (e.g. building GRUB keylayouts is very different
from building GRUB images).
|
| |
|
|
|
| |
Without this module the GRUB can't find devices--as in, 'ls' literally
lists nothing, not even the device GRUB booted from.
|
| |
|
|
|
|
|
|
| |
Since the majority of GRUB modules will be placed into CBFS instead of
the GRUB image itself, the modules-install and modules-preload files
no longer have any use as-is. However, they serve as a useful
reference to which modules should be retained for later
processing (thus the addition to the new install file).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This file should only contain the minimum of modules necessary to
create a working, bootable image able to source other modules and
files from CBFS and/or a separate device.
(module dependencies are installed automatically)
By including as few modules as possible into the GRUB image, selective
addition/removal of modules to/from CBFS is now possible. In
addition, modules can be reloaded without issue (modules included in
the GRUB image can't be reloaded).
|
| |
|
|
|
|
| |
A GRUB image will be produced on a target-specific basis so the
target will need its own copy of the modules to include in either the
GRUB image itself or CBFS.
|
| |
|
|
|
| |
It's fairly obvious that the files refer to _GRUB_ modules considering
the files are located in the GRUB project's configuration directory.
|
| |
|
|
|
|
|
|
|
|
|
| |
The purpose of each new file is as follows:
* arch -- CPU architecture to target when building images
* config -- embedded GRUB configuration
* format -- GRUB output format
* platform -- the platform GRUB should build images for
* prefix -- where GRUB should search for modules by default
* size -- the size of the floppy image to produce, in KiB
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
