summaryrefslogtreecommitdiff
path: root/util/nvramtool/nvramtool.spec
diff options
context:
space:
mode:
authorMartin Roth <gaumless@gmail.com>2024-03-03 14:05:01 -0700
committerFelix Singer <service+coreboot-gerrit@felixsinger.de>2024-07-26 04:36:52 +0000
commit28c669e216c5c16caa09f4c28682d37681717f51 (patch)
tree340c90f9afd9d8cd0e819181e06309a05b75aff4 /util/nvramtool/nvramtool.spec
parent6d6ec575b72fe4507825210fb2258416c784755f (diff)
3rdparty: Remove chromeec submodule
The chromeec submodule is the largest submodule being pulled into the coreboot tree, at over 400MB. The main branch also contains the majority of these commits, so restricting it to a single branch still fetches over 350MB. Because there is only a single mainboard directory that enables the build of the chromeec codebase by default, most people are fetching this repo for no reason. Based on this, we're going to change the way that the chromeec submodule is used, fetching it the way we currently fetch external payloads. This gives us 2 large advantages: 1) Only builds that actually need the chromeec repo will pull it down. 2) Each board that wants to build the chromeec codebase can use a different commit, unlike submodules which all use the same "current" commit. Signed-off-by: Martin Roth <gaumless@gmail.com> Change-Id: I357c4c9b506dd3817a308232446144ae889bc220 Reviewed-on: https://review.coreboot.org/c/coreboot/+/81024 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Matt DeVillier <matt.devillier@gmail.com> Reviewed-by: Julius Werner <jwerner@chromium.org> Reviewed-by: Angel Pons <th3fanbus@gmail.com> Reviewed-by: Elyes Haouas <ehaouas@noos.fr> Reviewed-by: Felix Singer <service+coreboot-gerrit@felixsinger.de>
Diffstat (limited to 'util/nvramtool/nvramtool.spec')
0 files changed, 0 insertions, 0 deletions