Attention is currently required from: Joel Linn, Nico Huber.
Matt DeVillier has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/81426?usp=email )
Change subject: superio/ite: Add special fan vectors and further options
......................................................................
Patch Set 5:
(1 comment)
Commit Message:
https://review.coreboot.org/c/coreboot/+/81426/comment/0b50c89c_e591d790 :
PS5, Line 12:
: The 3VSBSW# signal can now also be disabled again which is necessary to
: power components down properly in SMM when entering S5.
:
: A function to disable the PME# output was added as well.
I think these two can be be individual commits, separate from the fan vector control
--
To view, visit https://review.coreboot.org/c/coreboot/+/81426?usp=email
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: main
Gerrit-Change-Id: I93df2b5652fc3fde775b6161fa5bebc4a34d5e94
Gerrit-Change-Number: 81426
Gerrit-PatchSet: 5
Gerrit-Owner: Joel Linn <jl_coreboot(a)conductive.de>
Gerrit-Reviewer: Matt DeVillier <matt.devillier(a)gmail.com>
Gerrit-Reviewer: Nico Huber <nico.h(a)gmx.de>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Nico Huber <nico.h(a)gmx.de>
Gerrit-Attention: Joel Linn <jl_coreboot(a)conductive.de>
Gerrit-Comment-Date: Tue, 26 Mar 2024 01:09:43 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: Joel Linn, Nico Huber.
Matt DeVillier has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/81426?usp=email )
Change subject: superio/ite: Add special fan vectors and further options
......................................................................
Patch Set 5:
(2 comments)
File src/superio/ite/common/Kconfig:
https://review.coreboot.org/c/coreboot/+/81426/comment/c2da8221_c46de9d2 :
PS5, Line 61: config SUPERIO_ITE_ENV_CTRL_FAN_VECTOR_RANGED
does this need `depends on SUPERIO_ITE_ENV_CTRL_FAN_VECTOR` ?
File src/superio/ite/common/env_ctrl.c:
https://review.coreboot.org/c/coreboot/+/81426/comment/0682beeb_083f7907 :
PS1, Line 369: #endif
> I implemented Matt's suggestion. […]
Acknowledged
--
To view, visit https://review.coreboot.org/c/coreboot/+/81426?usp=email
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: main
Gerrit-Change-Id: I93df2b5652fc3fde775b6161fa5bebc4a34d5e94
Gerrit-Change-Number: 81426
Gerrit-PatchSet: 5
Gerrit-Owner: Joel Linn <jl_coreboot(a)conductive.de>
Gerrit-Reviewer: Matt DeVillier <matt.devillier(a)gmail.com>
Gerrit-Reviewer: Nico Huber <nico.h(a)gmx.de>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Nico Huber <nico.h(a)gmx.de>
Gerrit-Attention: Joel Linn <jl_coreboot(a)conductive.de>
Gerrit-Comment-Date: Tue, 26 Mar 2024 01:08:38 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Nico Huber <nico.h(a)gmx.de>
Comment-In-Reply-To: Matt DeVillier <matt.devillier(a)gmail.com>
Comment-In-Reply-To: Joel Linn <jl_coreboot(a)conductive.de>
Gerrit-MessageType: comment
Attention is currently required from: Joel Linn, Nico Huber.
Matt DeVillier has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/81516?usp=email )
Change subject: superio/ite: Fix warnings, add full-speed config option
......................................................................
Patch Set 1:
(1 comment)
Commit Message:
https://review.coreboot.org/c/coreboot/+/81516/comment/02194733_bfe72941 :
PS1, Line 7: Fix warnings, add full-speed config option
these look like they can be easily split into 2 separate commits
--
To view, visit https://review.coreboot.org/c/coreboot/+/81516?usp=email
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: main
Gerrit-Change-Id: Ibabe1b1ef55f2acb2074eceb535ec684bffc8155
Gerrit-Change-Number: 81516
Gerrit-PatchSet: 1
Gerrit-Owner: Joel Linn <jl_coreboot(a)conductive.de>
Gerrit-Reviewer: Matt DeVillier <matt.devillier(a)gmail.com>
Gerrit-Reviewer: Nico Huber <nico.h(a)gmx.de>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Nico Huber <nico.h(a)gmx.de>
Gerrit-Attention: Joel Linn <jl_coreboot(a)conductive.de>
Gerrit-Comment-Date: Tue, 26 Mar 2024 01:01:43 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: Nick Vaccaro, Vladimir Serbinenko, Yu-Ping Wu.
Julius Werner has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/81508?usp=email )
Change subject: Support for creating hybrid vboot images
......................................................................
Patch Set 5:
(1 comment)
Patchset:
PS5:
I'm honestly not really sure what you're trying to do here anyway. Can you describe your high-level goal in more detail?
It looks like you're adding a separate CMOS field that can control whether coreboot boots in recovery mode (from the RO partition) or as normal from the RW partition. So I'm assuming that you install the normal ChromeOS coreboot and payload in the RW slot and your own alternative OS firmware and payload in the RO slot? Or the other way round?
But then I don't really understand why you're doing all this work to try to create compatibility between the old RO/RW images from Volteer and the current coreboot ToT. That really only makes sense if you can't change the RO anymore (because it's write-protected)... but you're making a few changes to the RO here anyway, so clearly you'll still have to remove your write-protection and update your RO. So then why don't you just build both your alternative OS firmware and the ChromeOS firmware from ToT and then you don't have to worry about being compatible with some ancient image? Volteer should still build and boot fine in ToT for both coreboot and depthcharge (at least we're trying to keep it that way for all but the super old Chromebooks, and if something broke by accident it's usually an easy fix), so you can still build firmware that can "boot ChromeOS" but with the ToT coreboot code and RO/RW interface.
And for that matter, I also don't think that the vboot RO/RW interface is the right point to select which OS you're booting. That's not really what it's designed for. It's designed to be the cut-off point between updateable and non-updateable firmware, but the differences between the two RW images (and the recovery RO image) are only supposed to be differences in which version of the code they're running, not what boot policy that code follows.
If you want to change boot policy (and maybe make it controllable by a CMOS flag), that would probably belong in the payload according to the usual coreboot philosophy. In fact, we already have such a mechanism in our depthcharge payload that you could simply use for your purposes if you want to. It does pretty much what you want: it can boot either stock ChromeOS or a custom payload that you install, and which one it picks in the next boot can be controlled by a CMOS setting (except that this setting is in the vboot nvdata part of CMOS and you control it with our `crossystem` utility, by running `crossystem dev_default_boot=altfw` or `crossystem dev_default_boot=disk`). It will also display a UI on boot where you can select the boot target manually, but if you set the right GBB flag it will only show for 3 seconds before going with the default. See https://www.chromium.org/chromium-os/developer-library/guides/device/develo… for details on how to use that if you're interested.
--
To view, visit https://review.coreboot.org/c/coreboot/+/81508?usp=email
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: main
Gerrit-Change-Id: I9b26c332f5bf6befd62b5930b19d1b20e76261e7
Gerrit-Change-Number: 81508
Gerrit-PatchSet: 5
Gerrit-Owner: Vladimir Serbinenko <phcoder(a)gmail.com>
Gerrit-Reviewer: Julius Werner <jwerner(a)chromium.org>
Gerrit-Reviewer: Nick Vaccaro <nvaccaro(a)chromium.org>
Gerrit-Reviewer: Yu-Ping Wu <yupingso(a)google.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Nick Vaccaro <nvaccaro(a)chromium.org>
Gerrit-Attention: Yu-Ping Wu <yupingso(a)google.com>
Gerrit-Attention: Vladimir Serbinenko <phcoder(a)gmail.com>
Gerrit-Comment-Date: Tue, 26 Mar 2024 00:53:47 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: Nick Vaccaro, Vladimir Serbinenko, Yu-Ping Wu.
Julius Werner has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/81505?usp=email )
Change subject: Support loading legacy stage
......................................................................
Patch Set 2:
(1 comment)
Patchset:
PS2:
Sorry, but I don't think it's worth adding this extra complexity to coreboot, because your underlying goal isn't really achievable in practice. The RO/RW interface is fundamentally not stable, and broken by dozens of changes every year — in ways that are often non-obvious and entirely platform-specific. For example any change to the CAR memory layout that shifts the position of some persistent buffers (like CB:79288), or any change to the format of any of these persistent buffers (vboot, TPM logs, CBFS and FMAP cache, etc.) will break it.
You may have experimentally determined all the incompatibilities that currently exist to the Volteer RO for the moment, but more are going to be added in the future again, and what you did for Volteer will not automatically work for other boards that released at a different point in the past either. If we were really going to try to add compatibility options for all (or at least many) old ChromeOS boards we'd just be playing whack-a-mole forever and adding mountains of extra backwards-compatibility cruft to all parts of coreboot, and it still wouldn't work reliably anyway (and constantly break with hard crashes or worse whenever we miss an issue).
The only way vboot's RO/RW mechanism is intended to work is that you cut a branch when you release the RO, and then you only ever release RW updates from that branch, and you only carefully cherry-pick individual patches where you've confirmed that they don't interfere with the RO/RW boundary to that branch. That's how we use it in ChromeOS, and our branches are public so if anyone wants to build new custom coreboot RW images that work with our existing released RO images, they are welcome to do that by basing them off that branch. If there's sufficient interest we could even try to maintain matching branches for each device upstream, or try to cut regular coreboot "LTS" branches that we then try to target with our Chromebook releases or something like that. But trying to make ToT compatible with every old release at once is futile, I think.
--
To view, visit https://review.coreboot.org/c/coreboot/+/81505?usp=email
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: main
Gerrit-Change-Id: I4ae29a6227235c86f9f846986c18b361c3b3c78d
Gerrit-Change-Number: 81505
Gerrit-PatchSet: 2
Gerrit-Owner: Vladimir Serbinenko <phcoder(a)gmail.com>
Gerrit-Reviewer: Julius Werner <jwerner(a)chromium.org>
Gerrit-Reviewer: Nick Vaccaro <nvaccaro(a)chromium.org>
Gerrit-Reviewer: Yu-Ping Wu <yupingso(a)google.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Nick Vaccaro <nvaccaro(a)chromium.org>
Gerrit-Attention: Yu-Ping Wu <yupingso(a)google.com>
Gerrit-Attention: Vladimir Serbinenko <phcoder(a)gmail.com>
Gerrit-Comment-Date: Tue, 26 Mar 2024 00:28:48 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: Dinesh Gehlot, Eric Lai, Kapil Porwal, Nick Vaccaro.
SH Kim has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/81436?usp=email )
The change is no longer submittable: All-Comments-Resolved is unsatisfied now.
Change subject: mb/google/{brya,hades}: use soc index for variant_update_power_limits()
......................................................................
Patch Set 5:
(2 comments)
Patchset:
PS5:
One
File src/mainboard/google/brya/variants/baseboard/brya/ramstage.c:
https://review.coreboot.org/c/coreboot/+/81436/comment/e9f3293b_237769f5 :
PS5, Line 68: soc_config->tdp_pl4 = DIV_ROUND_UP(limits[i].pl4_power,
How about writing 'soc_config->tdp_pl1_override' and 'soc_config->tdp_pl2_override' with the values in limits[i] here as well?
After booting to ChromeOS, dptf_power_limits setting values will be replaced with DTT setting in OS.
--
To view, visit https://review.coreboot.org/c/coreboot/+/81436?usp=email
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: main
Gerrit-Change-Id: I9f1ba25c2d673fda48babf773208c2f2d2386c53
Gerrit-Change-Number: 81436
Gerrit-PatchSet: 5
Gerrit-Owner: SH Kim <sh_.kim(a)samsung.corp-partner.google.com>
Gerrit-Reviewer: Dinesh Gehlot <digehlot(a)google.com>
Gerrit-Reviewer: Eric Lai <ericllai(a)google.com>
Gerrit-Reviewer: Kapil Porwal <kapilporwal(a)google.com>
Gerrit-Reviewer: Nick Vaccaro <nvaccaro(a)chromium.org>
Gerrit-Reviewer: Subrata Banik <subratabanik(a)google.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Eric Lai <ericllai(a)google.com>
Gerrit-Attention: Kapil Porwal <kapilporwal(a)google.com>
Gerrit-Attention: Dinesh Gehlot <digehlot(a)google.com>
Gerrit-Attention: Nick Vaccaro <nvaccaro(a)chromium.org>
Gerrit-Comment-Date: Tue, 26 Mar 2024 00:11:48 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: Vladimir Serbinenko.
Julius Werner has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/81504?usp=email )
Change subject: cbfstool: Add printing of legacy stage type
......................................................................
Patch Set 1: Code-Review+2
--
To view, visit https://review.coreboot.org/c/coreboot/+/81504?usp=email
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: main
Gerrit-Change-Id: I588028d4327f59538f7c9920b671458fc631cb4c
Gerrit-Change-Number: 81504
Gerrit-PatchSet: 1
Gerrit-Owner: Vladimir Serbinenko <phcoder(a)gmail.com>
Gerrit-Reviewer: Julius Werner <jwerner(a)chromium.org>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Vladimir Serbinenko <phcoder(a)gmail.com>
Gerrit-Comment-Date: Mon, 25 Mar 2024 23:54:52 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: Matt DeVillier, Nico Huber.
Joel Linn has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/81426?usp=email )
Change subject: superio/ite: Add special fan vectors and further options
......................................................................
Patch Set 5:
(1 comment)
File src/superio/ite/common/env_ctrl.c:
https://review.coreboot.org/c/coreboot/+/81426/comment/2dd57016_10e3a6ba :
PS1, Line 369: #endif
> I still think keeping ITE_EC_FAN_VECTOR_CNT fixed at 2 and letting the preprocessor exclude the loop […]
I implemented Matt's suggestion. Setting the array length to 0 would save only 12 bytes in the config struct. Granted we would still carry the dead code but that should also be in the order of tens of bytes.
--
To view, visit https://review.coreboot.org/c/coreboot/+/81426?usp=email
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: main
Gerrit-Change-Id: I93df2b5652fc3fde775b6161fa5bebc4a34d5e94
Gerrit-Change-Number: 81426
Gerrit-PatchSet: 5
Gerrit-Owner: Joel Linn <jl_coreboot(a)conductive.de>
Gerrit-Reviewer: Matt DeVillier <matt.devillier(a)gmail.com>
Gerrit-Reviewer: Nico Huber <nico.h(a)gmx.de>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Nico Huber <nico.h(a)gmx.de>
Gerrit-Attention: Matt DeVillier <matt.devillier(a)gmail.com>
Gerrit-Comment-Date: Mon, 25 Mar 2024 23:35:48 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Nico Huber <nico.h(a)gmx.de>
Comment-In-Reply-To: Matt DeVillier <matt.devillier(a)gmail.com>
Comment-In-Reply-To: Joel Linn <jl_coreboot(a)conductive.de>
Gerrit-MessageType: comment
Attention is currently required from: Matt DeVillier, Michał Żygowski, MrChromebox, Nico Huber, Piotr Król.
Joel Linn has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/81310?usp=email )
Change subject: superio/ite: Unify it8772f with common code
......................................................................
Patch Set 6:
(1 comment)
Patchset:
PS5:
> this is still a bit too much for a single patch, IMO the changes to the common code and non-8772F SI […]
Done
--
To view, visit https://review.coreboot.org/c/coreboot/+/81310?usp=email
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: main
Gerrit-Change-Id: Ic4d9d5460628e444dc20f620179b39c90dbc28c6
Gerrit-Change-Number: 81310
Gerrit-PatchSet: 6
Gerrit-Owner: Joel Linn <jl_coreboot(a)conductive.de>
Gerrit-Reviewer: Matt DeVillier <matt.devillier(a)gmail.com>
Gerrit-Reviewer: Michał Żygowski <michal.zygowski(a)3mdeb.com>
Gerrit-Reviewer: MrChromebox <mrchromebox(a)gmail.com>
Gerrit-Reviewer: Nico Huber <nico.h(a)gmx.de>
Gerrit-Reviewer: Piotr Król <piotr.krol(a)3mdeb.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Attention: Nico Huber <nico.h(a)gmx.de>
Gerrit-Attention: Michał Żygowski <michal.zygowski(a)3mdeb.com>
Gerrit-Attention: Matt DeVillier <matt.devillier(a)gmail.com>
Gerrit-Attention: MrChromebox <mrchromebox(a)gmail.com>
Gerrit-Attention: Piotr Król <piotr.krol(a)3mdeb.com>
Gerrit-Comment-Date: Mon, 25 Mar 2024 23:24:38 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Matt DeVillier <matt.devillier(a)gmail.com>
Gerrit-MessageType: comment