aboutsummaryrefslogtreecommitdiff
path: root/projects
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'libreboot-images' of and_who/libreboot into masterSwift Geek2019-02-221-0/+9
|\
| * Create projects-download file for libreboot-imagesAndrew Robbins2019-02-221-0/+9
| | | | | | | | | | | | Avoid redundant actions if certain projects which are part of another (e.g. crossgcc in the coreboot repository) are left out of the download process.
* | Merge branch 'missing-functions' of and_who/libreboot into masterSwift Geek2019-02-2215-0/+60
|\ \
| * | Add usage() action to projects lacking itAndrew Robbins2019-02-2115-0/+60
| | |
* | | Merge branch 'libreboot-images' of and_who/libreboot into masterSwift Geek2019-02-222-4/+19
|\ \ \ | | |/ | |/|
| * | Delineate an order to build projects for imagesAndrew Robbins2019-02-211-1/+10
| | | | | | | | | | | | | | | There is more than one correct ordering of projects in this file; "correct" includes handling of project dependencies.
| * | Provide missing projects to build imagesAndrew Robbins2019-02-211-3/+9
| |/ | | | | | | | | Projects listed in this file are those (and their dependencies) which are necessary for creating Libreboot images in all configurations.
* | Create projects-build file for libreboot-toolsAndrew Robbins2019-02-221-0/+7
| | | | | | | | | | The projects listed in this file are those which are built when running the build action.
* | Update project files for libreboot-toolsAndrew Robbins2019-02-222-4/+5
|/ | | | | All tools currently in the build system should be represented in these files now.
* Declare and support dependencies for mosysAndrew Robbins2019-02-102-0/+9
|
* Declare and support dependencies for grubAndrew Robbins2019-02-102-0/+9
|
* Declare and support dependencies for depthchargeAndrew Robbins2019-02-104-0/+11
|
* Declare and support dependencies for dejavu-fontsAndrew Robbins2019-02-102-0/+9
|
* Declare and support dependencies for cros-ecAndrew Robbins2019-02-106-0/+13
|
* Declare project dependencies for coreboot depthcharge targetsAndrew Robbins2019-01-2211-0/+11
|
* Declare project dependencies for coreboot seabios targetsAndrew Robbins2019-01-2243-0/+43
|
* Declare project dependencies for coreboot grub targetsAndrew Robbins2019-01-2242-0/+42
|
* Declare minimum project dependencies for all boardsAndrew Robbins2019-01-2216-0/+20
|
* Support declaring dependencies for coreboot targetsAndrew Robbins2019-01-222-0/+9
| | | | | | | | | | | Projects listed in projects/coreboot/configs/dependencies are the minimum required by all boards. Dependencies required by a target in addition to those specified in parent dependencies files may be declared in the target's directory, e.g: projects/coreboot/configs/x200/dependencies
* Restructure Z61t coreboot target directoriesAndrew Robbins2019-01-1412-3/+4
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure X60 coreboot target directoriesAndrew Robbins2019-01-1425-15/+10
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure X200 coreboot target directoriesAndrew Robbins2019-01-1436-26/+17
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure Veyron Speedy coreboot target directoriesAndrew Robbins2019-01-1410-3/+4
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure Veyron Minnie coreboot target directoriesAndrew Robbins2019-01-1410-3/+4
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure Veyron Mickey coreboot target directoriesAndrew Robbins2019-01-146-2/+2
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure Veyron Jerry coreboot target directoriesAndrew Robbins2019-01-1410-3/+4
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure T60 coreboot target directoriesAndrew Robbins2019-01-1425-15/+10
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure T400 coreboot target directoriesAndrew Robbins2019-01-1436-26/+17
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure Nyan Blaze coreboot target directoriesAndrew Robbins2019-01-1410-3/+4
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure Nyan Big coreboot target directoriesAndrew Robbins2019-01-1410-3/+4
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure Macbook2,1 coreboot target directoriesAndrew Robbins2019-01-1425-15/+10
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure KGPE-D16 coreboot target directoriesAndrew Robbins2019-01-1412-3/+4
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure KFSN4-DRE coreboot target directoriesAndrew Robbins2019-01-1425-15/+10
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure KCMA-D8 coreboot target directoriesAndrew Robbins2019-01-1412-3/+4
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure GA-G41M-ES2L coreboot target directoriesAndrew Robbins2019-01-1425-15/+10
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure D945GCLF coreboot target directoriesAndrew Robbins2019-01-1415-0/+3
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Restructure D510MO coreboot target directoriesAndrew Robbins2019-01-1412-3/+4
| | | | | | | | The intent is to create a simple rule of thumb where arguments are given beginning with those that relate to the device's physical attributes, such as flash chip size, continuing with arguments on how to use the hardware (e.g. display mode), and ending with anything else.
* Create SeaBIOS/GRUB targets for D945GCLF corebootAndrew Robbins2019-01-123-0/+4
| | | | | | | D945GCLF ROMs can now be built with either SeaBIOS or GRUB as a default payload for use with a 1MiB flash, e.g.: './libreboot build coreboot d945gclf textmode 1mb seabios'
* Create 1MiB coreboot config/target for D945GCLFAndrew Robbins2019-01-122-0/+6
| | | | | | | | | Previously it was thought that only boards with 512KiB flash chips were produced but JohnMH (in #libreboot) ran across one with an SST25LF080A 1MiB flash. D945GCLF Coreboot ROMs can be built with, e.g.: './libreboot build coreboot d945gclf textmode 1mb'
* Merge branch 'grub-misc' of and_who/libreboot into masterLeah Rowe2018-12-292-19/+15
|\
| * Update BIOS GRUB prefix hard coded in core.imgAndrew Robbins2018-12-291-1/+1
| |
| * Copy correct number of bytes for floppy BPBAndrew Robbins2018-12-291-1/+1
| | | | | | | | | | | | | | | | The Bios Parameter Block (BPB) is 51 bytes, not 52. As-is, the first byte of executable code from the floppy image boot record is copied along with the BPB to boot.img; this extra byte isn't harmful to leave in since execution begins at offset 0x63+2 rather than 0x3C+2, but is a little messy.
| * Trim some less useful comments in grub-helperAndrew Robbins2018-12-281-4/+0
| |
| * Remove extraneous radix specifier in grub_bo_dump()Andrew Robbins2018-12-281-1/+1
| |
| * Use tabs for indentation in grub_bo functionsAndrew Robbins2018-12-281-13/+13
| |
* | Amend dejavu-fonts patch message about fontforgeAndrew Robbins2018-12-281-4/+4
|/ | | | | | | | 2017-12-20 was not the initial date from which fontforge could build fonts deterministically--builds of the DejaVu LGC subset were reproducible for some time before then. Though, it wasn't until that date that fontforge could reproducibly build the full DejaVu family of fonts (including DejaVuSansMono, which we use).
* Add redundancy for seabios git clone in case the main git repository is offlineLeah Rowe2018-12-281-1/+2
| | | | This modification has been made to both build systems.
* Include FAT fs support in BIOS GRUB core.imgAndrew Robbins2018-12-251-0/+1
| | | | | The SeaGRUB floppy image has a FAT12 filesystem and GRUB needs to be able to read it in order to load modules stored there.
* Automate updating SeaGRUB floppy image blocklistsAndrew Robbins2018-12-251-1/+95
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Refactor SeaGRUB floppy creation codeAndrew Robbins2018-12-252-29/+45
| | | | | | | | | | | | | | | | | | | 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)
generated by cgit v1.2.3-70-g09d2 (git 2.47.0) at 2024-11-01 22:26:03 +0000