aboutsummaryrefslogtreecommitdiff
path: root/projects/coreboot
Commit message (Collapse)AuthorAgeFilesLines
* Add missing QEMU payload dependencies filesAndrew Robbins2019-10-1916-0/+16
|
* Remove dependencies_check() from project scriptsAndrew Robbins2019-10-191-4/+0
| | | | | | | | Removing the check function allows dependencies() to be executed, printing the list of dependencies. It was not executed before due to the way check functions are handled; check functions are executed before functions with the same name (minus the "_check" suffix) in order to determine whether calling the function is necessary.
* Create 8MiB target for qemu_i440fx_piix4Andrew Robbins2019-03-0911-0/+21
| | | | | | | | | The 16MiB ROM is non-functional at the moment so an 8MiB target has been added in order to avoid losing QEMU support while the bug is identified and fixed. Files were copied from the 16MiB directory with the exception of the config file located at 8MiB/config which is new.
* Add GRUB/SeaBIOS targets to qemu_i440fx_piix4Andrew Robbins2019-03-096-0/+8
|
* Create corebootfb/textmode targets for qemu_i440fx_piix4Andrew Robbins2019-03-093-0/+8
| | | | | | | | The config for text mode doesn't actually have to be there (since text mode is the default in the base config) but, as in other cases, this configuration snippet is included for the sake of documenting what part of the base config is related to the target ("textmode" in this case).
* Create 16MiB flash size target for qemu_i440fx_piix4Andrew Robbins2019-03-092-0/+6
| | | | | 16MiB is the largest flash size for most of our supported boards so any emulated boards should stick with that upper limit.
* Create 8MiB target for qemu_q35_ich9Andrew Robbins2019-03-0911-0/+21
| | | | | | | | | The 16MiB ROM is non-functional at the moment so an 8MiB target has been added in order to avoid losing QEMU support while the bug is identified and fixed. Files were copied from the 16MiB directory with the exception of the config file located at 8MiB/config which is new.
* Add GRUB/SeaBIOS targets to qemu_q35_ich9Andrew Robbins2019-03-086-0/+8
|
* Create corebootfb/textmode targets for qemu_q35_ich9Andrew Robbins2019-03-083-0/+8
| | | | | | | | The config for text mode doesn't actually have to be there (since text mode is the default in the base config) but, as in other cases, this configuration snippet is included for the sake of documenting what part of the base config is related to the target ("textmode" in this case).
* Create 16MiB flash size target for qemu_q35_ich9Andrew Robbins2019-03-082-0/+6
| | | | | 16MiB is the largest flash size for most of our supported boards so any emulated boards should stick with that upper limit.
* Update coreboot config for qemu_q35_ich9Andrew Robbins2019-03-081-57/+70
| | | | | | | | | | Updated with the "oldconfig" make target. New configurations: * USE_OPTION_TABLE=y * STATIC_OPTION_TABLE=y * COMPRESS_SECONDARY_PAYLOAD=y
* Update coreboot config for qemu_i440fx_piix4Andrew Robbins2019-03-081-52/+62
| | | | | | | | Updated with the "oldconfig" make target. New configurations: * COMPRESS_SECONDARY_PAYLOAD=y
* Merge branch 'unit-prefix-3' of and_who/libreboot into masterSwift Geek2019-03-07115-12/+12
|\
| * Veyron Mickey: use proper binary prefix for flash sizeAndrew Robbins2019-03-056-1/+1
| |
| * Veyron Minnie: use proper binary prefix for flash sizeAndrew Robbins2019-03-0511-2/+2
| |
| * Veyron Speedy: use proper binary prefix for flash sizeAndrew Robbins2019-03-0511-2/+2
| |
| * X200: use proper binary prefix for flash sizeAndrew Robbins2019-03-0543-3/+3
| |
| * X60: use proper binary prefix for flash sizeAndrew Robbins2019-03-0529-2/+2
| |
| * Z61t: use proper binary prefix for flash sizeAndrew Robbins2019-03-0515-2/+2
| |
* | Merge branch 'unit-prefix-2' of and_who/libreboot into masterSwift Geek2019-03-07134-13/+13
|\ \
| * | Macbook2,1: use proper binary prefix for flash sizeAndrew Robbins2019-03-0529-2/+2
| | |
| * | Nyan Big: use proper binary prefix for flash sizeAndrew Robbins2019-03-0511-2/+2
| | |
| * | Nyan Blaze: use proper binary prefix for flash sizeAndrew Robbins2019-03-0511-2/+2
| | |
| * | T400: use proper binary prefix for flash sizeAndrew Robbins2019-03-0543-3/+3
| | |
| * | T60: use proper binary prefix for flash sizeAndrew Robbins2019-03-0529-2/+2
| | |
| * | Veyron Jerry: use proper binary prefix for flash sizeAndrew Robbins2019-03-0511-2/+2
| |/
* | D945GCLF: use proper binary prefix for flash sizeAndrew Robbins2019-03-0520-3/+3
| |
* | D510MO: use proper binary prefix for flash sizeAndrew Robbins2019-03-0515-2/+2
| |
* | GA-G41M-ES2L: use proper binary prefix for flash sizeAndrew Robbins2019-03-0529-2/+2
| |
* | KCMA-D8: use proper binary prefix for flash sizeAndrew Robbins2019-03-0515-2/+2
| |
* | KFSN4-DRE: use proper binary prefix for flash sizeAndrew Robbins2019-03-0529-2/+2
| |
* | KGPE-D16: use proper binary prefix for flash sizeAndrew Robbins2019-03-0515-2/+2
|/
* 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.
generated by cgit v1.2.3-70-g09d2 (git 2.47.0) at 2024-11-01 07:26:17 +0000