Raul Rangel has uploaded a new patch set (#2). ( https://review.coreboot.org/c/coreboot/+/67385 )
Change subject: Documentation: Add wake source info to device tree documentation
......................................................................
Documentation: Add wake source info to device tree documentation
The device tree documentation was promoting using a GPIO wake event and
a GPE wake event. We should only ever have one. This wasn't actually
causing a problem because the wake bit was set on the `irq` property,
but the IO-APIC can't actually wake the system, so it was a no-op.
This change fixes up the markdown so it's formatted correctly, and also
adds a section explaining what the different wake configurations are.
BUG=b:243700486
TEST=mdformat
Signed-off-by: Raul E Rangel <rrangel(a)chromium.org>
Change-Id: Ifcdbd5371408784bf9b81c1ade90263de8c60e0f
---
M Documentation/getting_started/devicetree.md
1 file changed, 97 insertions(+), 25 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/85/67385/2
--
To view, visit https://review.coreboot.org/c/coreboot/+/67385
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: Ifcdbd5371408784bf9b81c1ade90263de8c60e0f
Gerrit-Change-Number: 67385
Gerrit-PatchSet: 2
Gerrit-Owner: Raul Rangel <rrangel(a)chromium.org>
Gerrit-MessageType: newpatchset
Raul Rangel has uploaded this change for review. ( https://review.coreboot.org/c/coreboot/+/67385 )
Change subject: Documentation: Add wake source info to device tree documentation
......................................................................
Documentation: Add wake source info to device tree documentation
The device tree documentation was promoting using a GPIO wake event and
a GPE wake event. We should only ever have one. This wasn't actually
causing a problem because the wake bit was set on the `irq` property,
but the IO-APIC can't actually wake the system, so it was a no-op.
This change fixes up the markdown so it's formatted correctly, and also
adds a section explaining what the different wake configurations are.
BUG=b:243700486
TEST=mdformat
Signed-off-by: Raul E Rangel <rrangel(a)chromium.org>
Change-Id: Ifcdbd5371408784bf9b81c1ade90263de8c60e0f
---
M Documentation/getting_started/devicetree.md
1 file changed, 99 insertions(+), 27 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/85/67385/1
diff --git a/Documentation/getting_started/devicetree.md b/Documentation/getting_started/devicetree.md
index 41f5901..09f161b 100644
--- a/Documentation/getting_started/devicetree.md
+++ b/Documentation/getting_started/devicetree.md
@@ -86,7 +86,7 @@
chip drivers/i2c/generic
register "hid" = ""ELAN0000""
register "desc" = ""ELAN Touchpad""
- register "irq" = "ACPI_IRQ_WAKE_LEVEL_LOW(GPP_A21_IRQ)"
+ register "irq" = "ACPI_IRQ_LEVEL_LOW(GPP_A21_IRQ)"
register "wake" = "GPE0_DW0_21"
device i2c 15 on end
end
@@ -116,7 +116,7 @@
I2cSerialBusV2 (0x0015, ControllerInitiated, 400000,
AddressingMode7Bit, "\\_SB.PCI0.I2C0",
0x00, ResourceConsumer, , Exclusive, )
- Interrupt (ResourceConsumer, Level, ActiveLow, ExclusiveAndWake, ,, )
+ Interrupt (ResourceConsumer, Level, ActiveLow, Exclusive, ,, )
{
0x0000002D,
}
@@ -131,7 +131,7 @@
}
```
-You can see it generates _HID, _UID, _DDN, _STA, _CRS, _S0W, and _PRW
+You can see it generates \_HID, \_UID, \_DDN, \_STA, \_CRS, \_S0W, and \_PRW
names/methods in the Device's scope.
## Utilizing a device driver
@@ -165,7 +165,7 @@
register "hid" = ""ELAN0000""
```
-This corresponds to **const char *hid** in the struct. In the ACPI ASL, it
+This corresponds to **const char \*hid** in the struct. In the ACPI ASL, it
translates to:
```
@@ -181,18 +181,18 @@
register "desc" = ""ELAN Touchpad""
```
-corresponds to **const char *desc** and in ASL:
+corresponds to **const char \*desc** and in ASL:
```
Name (_DDN, "ELAN Touchpad") // _DDN: DOS Device Name
```
-### irq
+#### irq
It also adds the interrupt,
```
- Interrupt (ResourceConsumer, Level, ActiveLow, ExclusiveAndWake, ,, )
+ Interrupt (ResourceConsumer, Level, ActiveLow, Exclusive, ,, )
{
0x0000002D,
}
@@ -201,24 +201,20 @@
which comes from:
```
- register "irq" = "ACPI_IRQ_WAKE_LEVEL_LOW(GPP_A21_IRQ)"
+ register "irq" = "ACPI_IRQ_LEVEL_LOW(GPP_A21_IRQ)"
```
-The GPIO pin IRQ settings control the "Level", "ActiveLow", and
-"ExclusiveAndWake" settings seen above (level means it is a level-triggered
-interrupt as opposed to edge-triggered; active low means the interrupt is
-triggered when the signal is low).
+The GPIO pin IRQ settings control the "Level", and "ActiveLow" settings seen
+above (level means it is a level-triggered interrupt as opposed to
+edge-triggered; active low means the interrupt is triggered when the signal is
+low).
-Note that the ACPI_IRQ_WAKE_LEVEL_LOW macro informs the platform that the GPIO
-will be routed through SCI (ACPI's System Control Interrupt) for use as a wake
-source. Also note that the IRQ names are SoC-specific, and you will need to
+
+Also note that the IRQ names are SoC-specific, and you will need to
find the names in your SoC's header file. The ACPI_* macros are defined in
``src/arch/x86/include/acpi/acpi_device.h``.
-Using a GPIO as an IRQ requires that it is configured in coreboot correctly.
-This is often done in a mainboard-specific file named ``gpio.c``.
-
-### wake
+#### wake
The last register is:
@@ -231,6 +227,8 @@
this example. The "21" indicates GPP_X21, where GPP_X is mapped onto DW0
elsewhere in the devicetree.
+### device
+
The last bit of the definition of that device includes:
```
@@ -244,6 +242,57 @@
"Scope" that the device names and methods will live under, in this case
"\_SB.PCI0.I2C0".
+## Wake sources
+
+The ACPI spec defines two methods to describe how a device can wake the system.
+Only one of these method should be used, otherwise duplicate wake events will be
+generated.
+
+### Using GPEs as a wake source
+
+The `wake` property specified above is used to tell the ACPI subsystem that the
+device can use a GPE to wake the system. The OS can control whether to enable
+or disable the wake source by unmasking/masking off the GPE.
+
+The GPIO -> GPE mapping must be configured in firmware. On AMD platforms this is
+generally done by a mainboard specific `gpio.c` file that defines the GPIO
+using `PAD_SCI`. The GPIO -> GPE mapping is returned by the
+`soc_get_gpio_event_table` method that is defined in the SoC specific `gpio.c`
+file.
+
+The linux kernel has great support for this method.
+
+Windows on the other hand will
+[BSOD](https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/debugger/bug-check-0xa5--acpi-bios-error.md)
+complaining about an invalid ACPI configuration.
+> 0x1000D - A device used both GPE and GPIO interrupts, which is not supported.
+
+## Using GPIO interrupts as a wake source
+
+The `ACPI_IRQ_WAKE_{EDGE,LEVEL}_{LOW,HIGH}` macros can be used when setting the
+`irq` or `gpio_irq` properties. This ends up setting `ExclusiveAndWake` or
+`SharedAndWake` on the `Interrupt` or `GpioInt` ACPI resource.
+
+This method has a few caveats:
+* On Intel and AMD platforms the IO-APIC can't wake the system. This means you
+ can't use the `ACPI_IRQ_WAKE_*` macros with the `irq` property. Instead you
+ need to use the `gpio_irq` property.
+* The OS needs to know how to enable the `wake` bit on the GPIO. For linux this
+ means the platform specific GPIO controller driver must implement the
+ `irq_set_wake` callback. For AMD systems this wasn't implemented until
+ linux v5.15. If the controller doesn't define this callback, it's
+ possible for the firmware to manually set the `wake` bit on the GPIO. This is
+ often done in a mainboard-specific file named `gpio.c`. This is not
+ recommended because then it's not possible for the OS to disable the wake
+ source.
+* As of linux v6.0, the ACPI subsystem doesn't take the GPIO `wake` bit into
+ account when deciding on which power state to put the device in before
+ suspending the system. This means that if you define a power resource for a
+ device via `has_power_resource`, `enable_gpio`, etc, then the linux kernel
+ will place the device into D3Cold.
+
+This is the method preferred by Windows since it doesn't result in a BSOD.
+
## Other auto-generated names
(see [ACPI specification
@@ -251,17 +300,19 @@
for more details on ACPI methods)
### _S0W (S0 Device Wake State)
-_S0W indicates the deepest S0 sleep state this device can wake itself from,
-which in this case is ACPI_DEVICE_SLEEP_D3_HOT, representing _D3hot_.
+\_S0W indicates the deepest S0 sleep state this device can wake itself from,
+which in this case is `ACPI_DEVICE_SLEEP_D3_HOT`, representing _D3hot_.
+D3Hot means the `PR3` power resources are still on and the device is still
+responsive on the bus. For i2c devices this is generally the same state as `D0`.
-### _PRW (Power Resources for Wake)
-_PRW indicates the power resources and events required for wake. There are no
+### \_PRW (Power Resources for Wake)
+\_PRW indicates the power resources and events required for wake. There are no
dependent power resources, but the GPE (GPE0_DW0_21) is mentioned here (0x15),
as well as the deepest sleep state supporting waking the system (3), which is
S3.
-### _STA (Status)
-The _STA method is generated automatically, and its values, 0xF, indicates the
+### \_STA (Status)
+The \_STA method is generated automatically, and its values, 0xF, indicates the
following:
Bit [0] – Set if the device is present.
@@ -269,8 +320,8 @@
Bit [2] – Set if the device should be shown in the UI.
Bit [3] – Set if the device is functioning properly (cleared if device failed its diagnostics).
-### _CRS (Current resource settings)
-The _CRS method is generated automatically, as the driver knows it is an I2C
+### \_CRS (Current resource settings)
+The \_CRS method is generated automatically, as the driver knows it is an I2C
controller, and so specifies how to configure the controller for proper
operation with the touchpad.
--
To view, visit https://review.coreboot.org/c/coreboot/+/67385
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: Ifcdbd5371408784bf9b81c1ade90263de8c60e0f
Gerrit-Change-Number: 67385
Gerrit-PatchSet: 1
Gerrit-Owner: Raul Rangel <rrangel(a)chromium.org>
Gerrit-MessageType: newchange
Attention is currently required from: Raul Rangel, Jon Murphy, Karthik Ramasubramanian, Felix Held.
Robert Zieba has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/67384 )
Change subject: util/amdfwtool: Include the header with __packed definition
......................................................................
Patch Set 1: Code-Review+1
--
To view, visit https://review.coreboot.org/c/coreboot/+/67384
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I448cbad533608dd5c2bd4f2d827fcc5db5dee5cb
Gerrit-Change-Number: 67384
Gerrit-PatchSet: 1
Gerrit-Owner: Karthik Ramasubramanian <kramasub(a)google.com>
Gerrit-Reviewer: Felix Held <felix-coreboot(a)felixheld.de>
Gerrit-Reviewer: Jon Murphy <jpmurphy(a)google.com>
Gerrit-Reviewer: Raul Rangel <rrangel(a)chromium.org>
Gerrit-Reviewer: Robert Zieba <robertzieba(a)google.com>
Gerrit-Attention: Raul Rangel <rrangel(a)chromium.org>
Gerrit-Attention: Jon Murphy <jpmurphy(a)google.com>
Gerrit-Attention: Karthik Ramasubramanian <kramasub(a)google.com>
Gerrit-Attention: Felix Held <felix-coreboot(a)felixheld.de>
Gerrit-Comment-Date: Tue, 06 Sep 2022 20:39:29 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: Jason Nien, Martin Roth, Karthik Ramasubramanian.
build bot (Jenkins) has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/67261 )
Change subject: mb/google/skyrim: Enable amdfw separation
......................................................................
Patch Set 5:
(6 comments)
Commit Message:
Robot Comment from checkpatch (run ID jenkins-coreboot-checkpatch-158177):
https://review.coreboot.org/c/coreboot/+/67261/comment/07f9f09e_80d42442
PS5, Line 17: Before this patch series:
Possible unwrapped commit description (prefer a maximum 72 chars per line)
Robot Comment from checkpatch (run ID jenkins-coreboot-checkpatch-158177):
https://review.coreboot.org/c/coreboot/+/67261/comment/26828a4d_cf98904d
PS5, Line 18: 506:finished verifying keyblock/preamble (RSA) 1,977,851,803 (339,910)
Possible unwrapped commit description (prefer a maximum 72 chars per line)
Robot Comment from checkpatch (run ID jenkins-coreboot-checkpatch-158177):
https://review.coreboot.org/c/coreboot/+/67261/comment/ecbf5fcf_c7b3af10
PS5, Line 19: 507:starting to verify body (load+SHA2+RSA) 1,977,851,914 (111)
Possible unwrapped commit description (prefer a maximum 72 chars per line)
Robot Comment from checkpatch (run ID jenkins-coreboot-checkpatch-158177):
https://review.coreboot.org/c/coreboot/+/67261/comment/50a5f3cf_8297bdeb
PS5, Line 21: After this patch series:
Possible unwrapped commit description (prefer a maximum 72 chars per line)
Robot Comment from checkpatch (run ID jenkins-coreboot-checkpatch-158177):
https://review.coreboot.org/c/coreboot/+/67261/comment/cdd4410f_43dd1497
PS5, Line 22: 506:finished verifying keyblock/preamble (RSA) 7,948,714,284 (312,722)
Possible unwrapped commit description (prefer a maximum 72 chars per line)
Robot Comment from checkpatch (run ID jenkins-coreboot-checkpatch-158177):
https://review.coreboot.org/c/coreboot/+/67261/comment/744a7a24_1380850e
PS5, Line 23: 507:starting to verify body (load+SHA2+RSA) 7,948,714,389 (105)
Possible unwrapped commit description (prefer a maximum 72 chars per line)
--
To view, visit https://review.coreboot.org/c/coreboot/+/67261
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I78ec6d28b4c5fc40bdade47489d58180a54dee4d
Gerrit-Change-Number: 67261
Gerrit-PatchSet: 5
Gerrit-Owner: Karthik Ramasubramanian <kramasub(a)google.com>
Gerrit-Reviewer: Jason Nien <jason.nien(a)amd.corp-partner.google.com>
Gerrit-Reviewer: Martin Roth <martin.roth(a)amd.corp-partner.google.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Jason Nien <jason.nien(a)amd.corp-partner.google.com>
Gerrit-Attention: Martin Roth <martin.roth(a)amd.corp-partner.google.com>
Gerrit-Attention: Karthik Ramasubramanian <kramasub(a)google.com>
Gerrit-Comment-Date: Tue, 06 Sep 2022 20:23:20 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: Jason Nien, Martin Roth, Karthik Ramasubramanian.
Hello build bot (Jenkins), Jason Nien, Martin Roth,
I'd like you to reexamine a change. Please visit
https://review.coreboot.org/c/coreboot/+/67261
to look at the new patch set (#5).
Change subject: mb/google/skyrim: Enable amdfw separation
......................................................................
mb/google/skyrim: Enable amdfw separation
Select the config to separate the AMDFW binary from the verified boot
section.
BUG=b:203597980
TEST=Build Skyrim BIOS image and boot to OS with PSP verstage passing
the hash table and PSP verifying the binaries against the hash table.
Observe boot time improvement of ~140 ms while operating SPI bus at 66
MHz with PSP verstage enabled.
Before this patch series:
506:finished verifying keyblock/preamble (RSA) 1,977,851,803 (339,910)
507:starting to verify body (load+SHA2+RSA) 1,977,851,914 (111)
508:finished loading body 1,978,053,432 (201,518)
After this patch series:
506:finished verifying keyblock/preamble (RSA) 7,948,714,284 (312,722)
507:starting to verify body (load+SHA2+RSA) 7,948,714,389 (105)
508:finished loading body 7,948,797,849 (83,460)
Change-Id: I78ec6d28b4c5fc40bdade47489d58180a54dee4d
Signed-off-by: Karthikeyan Ramasubramanian <kramasub(a)google.com>
---
M src/mainboard/google/skyrim/Kconfig
M src/mainboard/google/skyrim/chromeos.fmd
2 files changed, 30 insertions(+), 0 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/61/67261/5
--
To view, visit https://review.coreboot.org/c/coreboot/+/67261
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I78ec6d28b4c5fc40bdade47489d58180a54dee4d
Gerrit-Change-Number: 67261
Gerrit-PatchSet: 5
Gerrit-Owner: Karthik Ramasubramanian <kramasub(a)google.com>
Gerrit-Reviewer: Jason Nien <jason.nien(a)amd.corp-partner.google.com>
Gerrit-Reviewer: Martin Roth <martin.roth(a)amd.corp-partner.google.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Jason Nien <jason.nien(a)amd.corp-partner.google.com>
Gerrit-Attention: Martin Roth <martin.roth(a)amd.corp-partner.google.com>
Gerrit-Attention: Karthik Ramasubramanian <kramasub(a)google.com>
Gerrit-MessageType: newpatchset
Attention is currently required from: Jason Glenesk, Raul Rangel, Matt DeVillier, Fred Reitberger, Felix Held.
Martin Roth has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/67301 )
Change subject: soc/amd/common/block/apob: Add hashed APOB support
......................................................................
Patch Set 5: Code-Review+2
(1 comment)
Commit Message:
https://review.coreboot.org/c/coreboot/+/67301/comment/faaca76f_fe4ef7de
PS4, Line 15: chausie
> The ABL will tell us exactly how big the APOB is in the header field. […]
I don't think there's a problem with getting this patch in before testing on guybrush. Since this needs to be enabled in the config, we just shouldn't push a patch enabling it for cezanne until then.
--
To view, visit https://review.coreboot.org/c/coreboot/+/67301
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I241968b115aaf41af63445410660bdd5199ceaba
Gerrit-Change-Number: 67301
Gerrit-PatchSet: 5
Gerrit-Owner: Fred Reitberger <reitbergerfred(a)gmail.com>
Gerrit-Reviewer: Felix Held <felix-coreboot(a)felixheld.de>
Gerrit-Reviewer: Jason Glenesk <jason.glenesk(a)gmail.com>
Gerrit-Reviewer: Martin Roth <martin.roth(a)amd.corp-partner.google.com>
Gerrit-Reviewer: Matt DeVillier <matt.devillier(a)amd.corp-partner.google.com>
Gerrit-Reviewer: Raul Rangel <rrangel(a)chromium.org>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Jason Glenesk <jason.glenesk(a)gmail.com>
Gerrit-Attention: Raul Rangel <rrangel(a)chromium.org>
Gerrit-Attention: Matt DeVillier <matt.devillier(a)amd.corp-partner.google.com>
Gerrit-Attention: Fred Reitberger <reitbergerfred(a)gmail.com>
Gerrit-Attention: Felix Held <felix-coreboot(a)felixheld.de>
Gerrit-Comment-Date: Tue, 06 Sep 2022 20:03:49 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: Raul Rangel <rrangel(a)chromium.org>
Comment-In-Reply-To: Fred Reitberger <reitbergerfred(a)gmail.com>
Gerrit-MessageType: comment
Attention is currently required from: Arthur Heymans, Patrick Rudolph, Christian Walter.
Angel Pons has uploaded a new patch set (#8) to the change originally created by Arthur Heymans. ( https://review.coreboot.org/c/coreboot/+/62649 )
Change subject: mb/prodrive/hermes: Allow using the Intel iGPU as primary
......................................................................
mb/prodrive/hermes: Allow using the Intel iGPU as primary
Configure the Intel iGPU as primary video adapter if enabled according
to EEPROM settings. The default is to use the ASPEED BMC as primary
video adapter, which only has a VGA output and the remote KVM output.
TODO: Figure out why iGPU video stops working after booting Linux and
doing a warm (no power cycle) reboot.
TEST=Test that DP and HDMI outputs work in pre-OS and on Linux using
the Poseidon piggy-back board, which has two DisplayPort outputs
and one HDMI output from a LSPCON.
Change-Id: I24d9ebc2055dc246e7f257aa2f3853b22c8af370
Signed-off-by: Arthur Heymans <arthur(a)aheymans.xyz>
---
M src/mainboard/prodrive/hermes/eeprom.h
M src/mainboard/prodrive/hermes/mainboard.c
M src/mainboard/prodrive/hermes/romstage.c
3 files changed, 55 insertions(+), 0 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/49/62649/8
--
To view, visit https://review.coreboot.org/c/coreboot/+/62649
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I24d9ebc2055dc246e7f257aa2f3853b22c8af370
Gerrit-Change-Number: 62649
Gerrit-PatchSet: 8
Gerrit-Owner: Arthur Heymans <arthur.heymans(a)9elements.com>
Gerrit-Reviewer: Christian Walter <christian.walter(a)9elements.com>
Gerrit-Reviewer: Patrick Rudolph <patrick.rudolph(a)9elements.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-CC: Arthur Heymans <arthur(a)aheymans.xyz>
Gerrit-CC: Paul Menzel <paulepanter(a)mailbox.org>
Gerrit-Attention: Arthur Heymans <arthur.heymans(a)9elements.com>
Gerrit-Attention: Patrick Rudolph <patrick.rudolph(a)9elements.com>
Gerrit-Attention: Christian Walter <christian.walter(a)9elements.com>
Gerrit-MessageType: newpatchset
Attention is currently required from: Elyes Haouas.
Hello build bot (Jenkins),
I'd like you to reexamine a change. Please visit
https://review.coreboot.org/c/coreboot/+/67367
to look at the new patch set (#2).
Change subject: crossgcc: Upgrade cmake and llvm
......................................................................
crossgcc: Upgrade cmake and llvm
Upgrade cmake to version 3.24.1 and llvm to version 15.0.0
Signed-off-by: Elyes Haouas <ehaouas(a)noos.fr>
Change-Id: I81a8371190513ca34d3c5efb0e3770ac3d873b03
Signed-off-by: Elyes Haouas <ehaouas(a)noos.fr>
---
M util/crossgcc/buildgcc
D util/crossgcc/sum/clang-14.0.6.src.tar.xz.cksum
A util/crossgcc/sum/clang-15.0.0.src.tar.xz.cksum
D util/crossgcc/sum/clang-tools-extra-14.0.6.src.tar.xz.cksum
A util/crossgcc/sum/clang-tools-extra-15.0.0.src.tar.xz.cksum
D util/crossgcc/sum/cmake-3.23.2.tar.gz.cksum
A util/crossgcc/sum/cmake-3.24.1.tar.gz.cksum
D util/crossgcc/sum/compiler-rt-14.0.6.src.tar.xz.cksum
A util/crossgcc/sum/compiler-rt-15.0.0.src.tar.xz.cksum
D util/crossgcc/sum/llvm-14.0.6.src.tar.xz.cksum
A util/crossgcc/sum/llvm-15.0.0.src.tar.xz.cksum
11 files changed, 20 insertions(+), 7 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/67/67367/2
--
To view, visit https://review.coreboot.org/c/coreboot/+/67367
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I81a8371190513ca34d3c5efb0e3770ac3d873b03
Gerrit-Change-Number: 67367
Gerrit-PatchSet: 2
Gerrit-Owner: Elyes Haouas <ehaouas(a)noos.fr>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Elyes Haouas <ehaouas(a)noos.fr>
Gerrit-MessageType: newpatchset