Arthur Heymans has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/36589 )
Change subject: cpu/x86/smm: Add helper functions to deal with different save states
......................................................................
Patch Set 3:
> Patch Set 3:
>
> We have something similar in src/soc/intel/common/block/include/intelblocks/smihandler.h and src/soc/intel/common/block/smm/smihandler.c where the ops are about getting and setting a register.
>
> 1. Why is this about pointers to registers and not just getting and setting the explicit register?
> 2. I prefer the ops-based approach because the chipset can say "these are my ops" and the other save state versions are garbage collected instead of carrying support for save state versions in the binary.
> 3. Are we planning on converging/sharing the implementation?
Attempt to provide an API in CB:36661. With that code there is no need anymore to have per chipset ops, since the ops can be guessed from the smm revision.
--
To view, visit https://review.coreboot.org/c/coreboot/+/36589
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I85325a25dc38d7cfc7eb0dfde621e5ebfeef0e15
Gerrit-Change-Number: 36589
Gerrit-PatchSet: 3
Gerrit-Owner: Arthur Heymans <arthur(a)aheymans.xyz>
Gerrit-Reviewer: Aaron Durbin <adurbin(a)chromium.org>
Gerrit-Reviewer: Arthur Heymans <arthur(a)aheymans.xyz>
Gerrit-Reviewer: Martin Roth <martinroth(a)google.com>
Gerrit-Reviewer: Patrick Georgi <pgeorgi(a)google.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: Maxim Polyakov <max.senia.poliak(a)gmail.com>
Gerrit-CC: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Comment-Date: Thu, 07 Nov 2019 15:01:58 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Arthur Heymans has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/34089 )
Change subject: src/soc/intel/common/itss: Add support to get IRQ configuration for PCI devices
......................................................................
Patch Set 20:
> Patch Set 20:
>
> > Patch Set 20:
> >
> > > Patch Set 20:
> > >
> > > > Patch Set 20:
> > > >
> > > > > Patch Set 20:
> > > > >
> > > > > > Patch Set 20:
> > > > > > Ok, But this code already creates a irq info data , I am using the same to generate the ACPI code too, I do not need to re-populate the irq matrix.
> > > > >
> > > > > This argument sounds to me as if you don't want to use the common facilities we already have because you already wrote your own reimplementation of them. I hope I misunderstand you because that's not very convincing.
> > > > >
> > > > > What is missing in acpi_pirq_gen that is present in your code (and can't be added there to avoid having all the common parts twice in our code base)?
> > > >
> > > > The intent of this code was to populate irq info based on the device tree selection and pass it to FSP for IRQ configuration based on the irq assignment rules, this implementation is added new(does not exist in acpi_pirq_gen(neither should be scoped in ACPI module)), I think
> > > > Arthur made a point to re-use APCI generation part from acpi_pirq_gen, to which my response was I did not want to re-populate the irq matrix again, since this code already creates that info.
> > >
> > > You don't have to repopulate anything, the matrix is a local structure of that code. You just have to provide a callback function called 'intel_common_map_pirq' which returns a route for a given pin on a given PCI device. Given your current code that should be easy or even trivial to implement. Give the FSP what it needs using this code(and please document it first!) and use the common southbridge code create ACPI _PIR tables.
> > >
> > > Your code potentially has multiple entries for the same PCI device and pin in the _PIR table. That needs to be avoided. The best way to avoid that is by populating a matrix[MAX_PCI_DEV][4] '4' being pin[A-D] otherwise you have to keep track of what device and what pin already have an entry. You end up needing a 'matrix' anyway as the data FSP needs does not fully match what ACPI _PIR expects.
> > >
> > > Please consider that reusing common code usually means avoiding pitfalls someone else fell into in the past.
> >
> > Hi Arthur, I wanted to understand more on you below comment:
> >
> > [Arthur]Your code potentially has multiple entries for the same PCI device and pin in the _PIR table. That needs to be avoided. The best way to avoid that is by populating a matrix[MAX_PCI_DEV][4] '4' being pin[A-D] otherwise you have to keep track of what device and what pin already have an entry. You end up needing a 'matrix' anyway as the data FSP needs does not fully match what ACPI _PIR expects.
> >
> > [Aamir] I do not see multiple entries with same PCI device and int pin mapping , below is the ACPI package that is currently generated with this implementation:
> >
> > Name (PIRX, Package (0x11)
> > {
> > Package (0x04)
> > {
> > 0x0012FFFF,
> > 0x00,
> > Zero,
> > 0x10
> > },
> >
> > Package (0x04)
> > {
> > 0x0014FFFF,
> > 0x00,
> > Zero,
> > 0x10
> > },
> >
> > Package (0x04)
> > {
> > 0x0014FFFF,
> > 0x01,
> > Zero,
> > 0x11
> > },
> >
> > Package (0x04)
> > {
> > 0x0014FFFF,
> > 0x02,
> > Zero,
> > 0x12
> > },
> >
> > Package (0x04)
> > {
> > 0x0015FFFF,
> > 0x00,
> > Zero,
> > 0x10
> > },
> >
> > Package (0x04)
> > {
> > 0x0015FFFF,
> > 0x01,
> > Zero,
> > 0x11
> > },
> >
> > Package (0x04)
> > {
> > 0x0015FFFF,
> > 0x02,
> > Zero,
> > 0x12
> > },
> >
> > Package (0x04)
> > {
> > 0x0016FFFF,
> > 0x00,
> > Zero,
> > 0x10
> > },
> >
> > Package (0x04)
> > {
> > 0x0017FFFF,
> > 0x00,
> > Zero,
> > 0x10
> > },
> >
> > Package (0x04)
> > {
> > 0x0019FFFF,
> > 0x03,
> > Zero,
> > 0x13
> > },
> >
> > Package (0x04)
> > {
> > 0x001DFFFF,
> > 0x00,
> > Zero,
> > 0x10
> > },
> >
> > Package (0x04)
> > {
> > 0x001DFFFF,
> > 0x01,
> > Zero,
> > 0x11
> > },
> >
> > Package (0x04)
> > {
> > 0x001EFFFF,
> > 0x00,
> > Zero,
> > 0x14
> > },
> >
> > Package (0x04)
> > {
> > 0x001EFFFF,
> > 0x01,
> > Zero,
> > 0x15
> > },
> >
> > Package (0x04)
> > {
> > 0x001EFFFF,
> > 0x02,
> > Zero,
> > 0x16
> > },
> >
> > Package (0x04)
> > {
> > 0x001FFFFF,
> > 0x00,
> > Zero,
> > 0x10
> > },
> >
> > Package (0x04)
> > {
> > 0x001FFFFF,
> > 0x01,
> > Zero,
> > 0x11
> > }
> > })
> >
> > And this is the IRQ table passed to FSP for configuration.(LPSS would not share same IRQs)
> > https://review.coreboot.org/c/coreboot/+/34089/13/src/soc/intel/common/bloc…
> >
> > Both aligns and do not mismatch, that is the advantage of using the same irq data for creating the APCI package as well.
>
> Hi Arthur, did you get a chance to review the acpi package, if no concerns, can you please review your -2 vote?
> Anyways this CL is needed to populate irq table for FSP to consume. ACPI CL is here: https://review.coreboot.org/c/coreboot/+/34658/6
No, you are just 'lucky' that there are no double entries.
Please try https://review.coreboot.org/c/coreboot/+/36437 and use that to generate acpi _PRT entries. It should be trivial to extend to use other settings you provide fsp.
--
To view, visit https://review.coreboot.org/c/coreboot/+/34089
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: Ib7066432ff5f0d7017ac5a44922ca69f07da9556
Gerrit-Change-Number: 34089
Gerrit-PatchSet: 20
Gerrit-Owner: Aamir Bohra <aamir.bohra(a)intel.com>
Gerrit-Reviewer: Aamir Bohra <aamir.bohra(a)intel.com>
Gerrit-Reviewer: Arthur Heymans <arthur(a)aheymans.xyz>
Gerrit-Reviewer: Furquan Shaikh <furquan(a)google.com>
Gerrit-Reviewer: Karthik Ramasubramanian <kramasub(a)google.com>
Gerrit-Reviewer: Lean Sheng Tan <lean.sheng.tan(a)intel.com>
Gerrit-Reviewer: Martin Roth <martinroth(a)google.com>
Gerrit-Reviewer: Patrick Georgi <pgeorgi(a)google.com>
Gerrit-Reviewer: Patrick Rudolph <siro(a)das-labor.org>
Gerrit-Reviewer: Paul Fagerburg <pfagerburg(a)chromium.org>
Gerrit-Reviewer: Rizwan Qureshi <rizwan.qureshi(a)intel.com>
Gerrit-Reviewer: Shelley Chen <shchen(a)google.com>
Gerrit-Reviewer: Subrata Banik <subrata.banik(a)intel.com>
Gerrit-Reviewer: Tim Wawrzynczak <twawrzynczak(a)chromium.org>
Gerrit-Reviewer: Tim Wawrzynczak <twawrzynczak(a)google.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-CC: Patrick Rudolph <patrick.rudolph(a)9elements.com>
Gerrit-CC: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Comment-Date: Thu, 07 Nov 2019 14:19:11 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Mario Scheithauer has uploaded this change for review. ( https://review.coreboot.org/c/coreboot/+/36645 )
Change subject: soc/intel/{apl,dnv,quark}: Use strip_quotes for FSP options
......................................................................
soc/intel/{apl,dnv,quark}: Use strip_quotes for FSP options
The commit (1058dd84f06fa2fcbdd99eb99da07dccdf5b9722) breaks the Siemens
APL mainboards as FSP-M never returns once it is called.
This patch fixes an incomplete implementation of this change.
TEST=tested on siemens/mc_apl5
Change-Id: I48e5fa36e1ad799d09714f53a3041f73b8ec3550
Signed-off-by: Mario Scheithauer <mario.scheithauer(a)siemens.com>
---
M src/soc/intel/apollolake/Makefile.inc
M src/soc/intel/denverton_ns/Makefile.inc
M src/soc/intel/quark/Makefile.inc
3 files changed, 5 insertions(+), 5 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/45/36645/1
diff --git a/src/soc/intel/apollolake/Makefile.inc b/src/soc/intel/apollolake/Makefile.inc
index 42cbab0..ef81e32 100644
--- a/src/soc/intel/apollolake/Makefile.inc
+++ b/src/soc/intel/apollolake/Makefile.inc
@@ -108,7 +108,7 @@
CPPFLAGS_common += -I$(src)/soc/intel/apollolake/include
# Since FSP-M runs in CAR we need to relocate it to a specific address
-$(FSP_M_CBFS)-options := -b $(CONFIG_FSP_M_ADDR)
+$(call strip_quotes,$(CONFIG_FSP_M_CBFS))-options := -b $(CONFIG_FSP_M_ADDR)
# Handle GLK paging requirements
ifeq ($(CONFIG_PAGING_IN_CACHE_AS_RAM),y)
diff --git a/src/soc/intel/denverton_ns/Makefile.inc b/src/soc/intel/denverton_ns/Makefile.inc
index 51ae136..4050f61 100644
--- a/src/soc/intel/denverton_ns/Makefile.inc
+++ b/src/soc/intel/denverton_ns/Makefile.inc
@@ -90,8 +90,8 @@
##Set FSP binary blobs memory location
-$(FSP_T_CBFS)-options := -b $(CONFIG_FSP_T_ADDR) --xip
-$(FSP_M_CBFS)-options := -b $(CONFIG_FSP_M_ADDR) --xip
-$(FSP_S_CBFS)-options := -b $(CONFIG_FSP_S_ADDR) --xip
+$(call strip_quotes,$(CONFIG_FSP_T_CBFS))-options := -b $(CONFIG_FSP_T_ADDR) --xip
+$(call strip_quotes,$(CONFIG_FSP_M_CBFS))-options := -b $(CONFIG_FSP_M_ADDR) --xip
+$(call strip_quotes,$(CONFIG_FSP_S_CBFS))-options := -b $(CONFIG_FSP_S_ADDR) --xip
endif ## CONFIG_SOC_INTEL_DENVERTON_NS
diff --git a/src/soc/intel/quark/Makefile.inc b/src/soc/intel/quark/Makefile.inc
index f2413c8..bd120ab 100644
--- a/src/soc/intel/quark/Makefile.inc
+++ b/src/soc/intel/quark/Makefile.inc
@@ -71,7 +71,7 @@
CPPFLAGS_common += -I3rdparty/blobs/soc/intel/quark
# Since FSP-M runs in CAR we need to relocate it to a specific address
-$(FSP_M_CBFS)-options := -b $(CONFIG_FSP_ESRAM_LOC)
+$(call strip_quotes,$(CONFIG_FSP_M_CBFS))-options := -b $(CONFIG_FSP_ESRAM_LOC)
# Add the FSP binary to the CBFS image
cbfs-files-$(CONFIG_ADD_FSP_RAW_BIN) += fsp.bin
--
To view, visit https://review.coreboot.org/c/coreboot/+/36645
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I48e5fa36e1ad799d09714f53a3041f73b8ec3550
Gerrit-Change-Number: 36645
Gerrit-PatchSet: 1
Gerrit-Owner: Mario Scheithauer <mario.scheithauer(a)siemens.com>
Gerrit-MessageType: newchange
Joel Kitching has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/36341 )
Change subject: security/vboot: Build vboot library with same .a that depthcharge uses
......................................................................
Patch Set 18:
> > This is all good but it still leaves the problem that we need to deal with the TLCL duplicate references (see my comment early on). Are you guys clear on who's going to deal with that (Tim or Joel)?
Ah, it's only after seeing this CL that I realize the purpose is for handling the duplicate references. Might want to mention that in the vboot_reference CL.
--
To view, visit https://review.coreboot.org/c/coreboot/+/36341
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I905b781c3596965ec7ef45a2a7eafe15fdd4d9cc
Gerrit-Change-Number: 36341
Gerrit-PatchSet: 18
Gerrit-Owner: Tim Wawrzynczak <twawrzynczak(a)chromium.org>
Gerrit-Reviewer: Aaron Durbin <adurbin(a)chromium.org>
Gerrit-Reviewer: Furquan Shaikh <furquan(a)google.com>
Gerrit-Reviewer: Joel Kitching <kitching(a)google.com>
Gerrit-Reviewer: Julius Werner <jwerner(a)chromium.org>
Gerrit-Reviewer: Karthik Ramasubramanian <kramasub(a)google.com>
Gerrit-Reviewer: Martin Roth <martinroth(a)google.com>
Gerrit-Reviewer: Patrick Georgi <pgeorgi(a)google.com>
Gerrit-Reviewer: Tim Wawrzynczak <twawrzynczak(a)chromium.org>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Comment-Date: Thu, 07 Nov 2019 14:04:01 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Frans Hendriks has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/36635 )
Change subject: eltan/security: Replace __PRE_RAM__ with ENV_ROMSTAGE_OR_BEFORE
......................................................................
Patch Set 2: Code-Review+2
Working fine on Facebook FBG1701
--
To view, visit https://review.coreboot.org/c/coreboot/+/36635
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: Id56a63a67b7eb70dce6687bb9c2734a711f611b3
Gerrit-Change-Number: 36635
Gerrit-PatchSet: 2
Gerrit-Owner: Kyösti Mälkki <kyosti.malkki(a)gmail.com>
Gerrit-Reviewer: Frans Hendriks <fhendriks(a)eltan.com>
Gerrit-Reviewer: Kyösti Mälkki <kyosti.malkki(a)gmail.com>
Gerrit-Reviewer: Wim Vervoorn <wvervoorn(a)eltan.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Reviewer: wvervoorn <wvervoorn(a)eltan.com>
Gerrit-CC: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Comment-Date: Thu, 07 Nov 2019 13:41:12 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Frans Hendriks has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/36635 )
Change subject: eltan/security: Replace __PRE_RAM__ with ENV_ROMSTAGE_OR_BEFORE
......................................................................
Patch Set 2:
Will verify this patchset (and the other related patches) on Facebook FBG1701 and let you know the result.
--
To view, visit https://review.coreboot.org/c/coreboot/+/36635
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: Id56a63a67b7eb70dce6687bb9c2734a711f611b3
Gerrit-Change-Number: 36635
Gerrit-PatchSet: 2
Gerrit-Owner: Kyösti Mälkki <kyosti.malkki(a)gmail.com>
Gerrit-Reviewer: Frans Hendriks <fhendriks(a)eltan.com>
Gerrit-Reviewer: Kyösti Mälkki <kyosti.malkki(a)gmail.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Reviewer: wvervoorn <wvervoorn(a)eltan.com>
Gerrit-CC: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Comment-Date: Thu, 07 Nov 2019 11:24:26 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Aamir Bohra has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/34089 )
Change subject: src/soc/intel/common/itss: Add support to get IRQ configuration for PCI devices
......................................................................
Patch Set 20:
> Patch Set 20:
>
> > Patch Set 20:
> >
> > > Patch Set 20:
> > >
> > > > Patch Set 20:
> > > >
> > > > > Patch Set 20:
> > > > > Ok, But this code already creates a irq info data , I am using the same to generate the ACPI code too, I do not need to re-populate the irq matrix.
> > > >
> > > > This argument sounds to me as if you don't want to use the common facilities we already have because you already wrote your own reimplementation of them. I hope I misunderstand you because that's not very convincing.
> > > >
> > > > What is missing in acpi_pirq_gen that is present in your code (and can't be added there to avoid having all the common parts twice in our code base)?
> > >
> > > The intent of this code was to populate irq info based on the device tree selection and pass it to FSP for IRQ configuration based on the irq assignment rules, this implementation is added new(does not exist in acpi_pirq_gen(neither should be scoped in ACPI module)), I think
> > > Arthur made a point to re-use APCI generation part from acpi_pirq_gen, to which my response was I did not want to re-populate the irq matrix again, since this code already creates that info.
> >
> > You don't have to repopulate anything, the matrix is a local structure of that code. You just have to provide a callback function called 'intel_common_map_pirq' which returns a route for a given pin on a given PCI device. Given your current code that should be easy or even trivial to implement. Give the FSP what it needs using this code(and please document it first!) and use the common southbridge code create ACPI _PIR tables.
> >
> > Your code potentially has multiple entries for the same PCI device and pin in the _PIR table. That needs to be avoided. The best way to avoid that is by populating a matrix[MAX_PCI_DEV][4] '4' being pin[A-D] otherwise you have to keep track of what device and what pin already have an entry. You end up needing a 'matrix' anyway as the data FSP needs does not fully match what ACPI _PIR expects.
> >
> > Please consider that reusing common code usually means avoiding pitfalls someone else fell into in the past.
>
> Hi Arthur, I wanted to understand more on you below comment:
>
> [Arthur]Your code potentially has multiple entries for the same PCI device and pin in the _PIR table. That needs to be avoided. The best way to avoid that is by populating a matrix[MAX_PCI_DEV][4] '4' being pin[A-D] otherwise you have to keep track of what device and what pin already have an entry. You end up needing a 'matrix' anyway as the data FSP needs does not fully match what ACPI _PIR expects.
>
> [Aamir] I do not see multiple entries with same PCI device and int pin mapping , below is the ACPI package that is currently generated with this implementation:
>
> Name (PIRX, Package (0x11)
> {
> Package (0x04)
> {
> 0x0012FFFF,
> 0x00,
> Zero,
> 0x10
> },
>
> Package (0x04)
> {
> 0x0014FFFF,
> 0x00,
> Zero,
> 0x10
> },
>
> Package (0x04)
> {
> 0x0014FFFF,
> 0x01,
> Zero,
> 0x11
> },
>
> Package (0x04)
> {
> 0x0014FFFF,
> 0x02,
> Zero,
> 0x12
> },
>
> Package (0x04)
> {
> 0x0015FFFF,
> 0x00,
> Zero,
> 0x10
> },
>
> Package (0x04)
> {
> 0x0015FFFF,
> 0x01,
> Zero,
> 0x11
> },
>
> Package (0x04)
> {
> 0x0015FFFF,
> 0x02,
> Zero,
> 0x12
> },
>
> Package (0x04)
> {
> 0x0016FFFF,
> 0x00,
> Zero,
> 0x10
> },
>
> Package (0x04)
> {
> 0x0017FFFF,
> 0x00,
> Zero,
> 0x10
> },
>
> Package (0x04)
> {
> 0x0019FFFF,
> 0x03,
> Zero,
> 0x13
> },
>
> Package (0x04)
> {
> 0x001DFFFF,
> 0x00,
> Zero,
> 0x10
> },
>
> Package (0x04)
> {
> 0x001DFFFF,
> 0x01,
> Zero,
> 0x11
> },
>
> Package (0x04)
> {
> 0x001EFFFF,
> 0x00,
> Zero,
> 0x14
> },
>
> Package (0x04)
> {
> 0x001EFFFF,
> 0x01,
> Zero,
> 0x15
> },
>
> Package (0x04)
> {
> 0x001EFFFF,
> 0x02,
> Zero,
> 0x16
> },
>
> Package (0x04)
> {
> 0x001FFFFF,
> 0x00,
> Zero,
> 0x10
> },
>
> Package (0x04)
> {
> 0x001FFFFF,
> 0x01,
> Zero,
> 0x11
> }
> })
>
> And this is the IRQ table passed to FSP for configuration.(LPSS would not share same IRQs)
> https://review.coreboot.org/c/coreboot/+/34089/13/src/soc/intel/common/bloc…
>
> Both aligns and do not mismatch, that is the advantage of using the same irq data for creating the APCI package as well.
Hi Arthur, did you get a chance to review the acpi package, if no concerns, can you please review your -2 vote?
Anyways this CL is needed to populate irq table for FSP to consume. ACPI CL is here: https://review.coreboot.org/c/coreboot/+/34658/6
--
To view, visit https://review.coreboot.org/c/coreboot/+/34089
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: Ib7066432ff5f0d7017ac5a44922ca69f07da9556
Gerrit-Change-Number: 34089
Gerrit-PatchSet: 20
Gerrit-Owner: Aamir Bohra <aamir.bohra(a)intel.com>
Gerrit-Reviewer: Aamir Bohra <aamir.bohra(a)intel.com>
Gerrit-Reviewer: Arthur Heymans <arthur(a)aheymans.xyz>
Gerrit-Reviewer: Furquan Shaikh <furquan(a)google.com>
Gerrit-Reviewer: Karthik Ramasubramanian <kramasub(a)google.com>
Gerrit-Reviewer: Lean Sheng Tan <lean.sheng.tan(a)intel.com>
Gerrit-Reviewer: Martin Roth <martinroth(a)google.com>
Gerrit-Reviewer: Patrick Georgi <pgeorgi(a)google.com>
Gerrit-Reviewer: Patrick Rudolph <siro(a)das-labor.org>
Gerrit-Reviewer: Paul Fagerburg <pfagerburg(a)chromium.org>
Gerrit-Reviewer: Rizwan Qureshi <rizwan.qureshi(a)intel.com>
Gerrit-Reviewer: Shelley Chen <shchen(a)google.com>
Gerrit-Reviewer: Subrata Banik <subrata.banik(a)intel.com>
Gerrit-Reviewer: Tim Wawrzynczak <twawrzynczak(a)chromium.org>
Gerrit-Reviewer: Tim Wawrzynczak <twawrzynczak(a)google.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-CC: Patrick Rudolph <patrick.rudolph(a)9elements.com>
Gerrit-CC: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Comment-Date: Thu, 07 Nov 2019 11:08:06 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment