u-boot.git/configs/chromebook_link_defconfig, branch master

env: Rename SYS_RELOC_GD_ENV_ADDR to ENV_RELOC_GD_ENV_ADDR

2025-06-20T18:15:08+00:00

Rename the variable and add ENV_ prefix, so that all configuration
options which are related to environment would have an CONFIG_ENV_
prefix. No functional change.

Reviewed-by: Tom Rini 
Signed-off-by: Marek Vasut

configs: Resync with savedefconfig

2024-11-12T21:00:36+00:00

Rsync all defconfig files using moveconfig.py

Signed-off-by: Tom Rini

configs: Resync with savedefconfig

2024-10-08T15:28:10+00:00

Rsync all defconfig files using moveconfig.py

Signed-off-by: Tom Rini

google: Disable TPMv2 on most Chromebooks

2024-07-04T15:25:21+00:00

This feature is not present on older Chromebooks, so disable the
setting.

Signed-off-by: Simon Glass 
Reviewed-by: Ilias Apalodimas

Merge branch 'next'

2024-07-01T21:00:56+00:00

x86: Set a board-size limit for chromebook_link

2024-06-28T19:54:52+00:00

Set a size limit for this board so that we get a build error if it grows
too much.

Note that the limit is approximately, since it does not include the FDT,
microcode and fdtmap, which can change in size. However this board is
fairly stable, so overflowing this limit will likely result in the image
not fitting in the ROM space available for U-Boot.

Signed-off-by: Simon Glass

configs: Resync with savedefconfig

2024-01-03T14:26:16+00:00

Rsync all defconfig files using moveconfig.py

Signed-off-by: Tom Rini

configs: Resync with savedefconfig

2023-10-02T17:58:20+00:00

Rsync all defconfig files using moveconfig.py

Signed-off-by: Tom Rini

event: Use an event to replace last_stage_init()

2023-08-31T17:16:55+00:00

Add a new event which handles this function. Convert existing use of
the function to use the new event instead.

Make sure that EVENT is enabled by affected boards, by selecting it from
the LAST_STAGE_INIT option. For x86, enable it by default since all boards
need it.

For controlcenterdc, inline the get_tpm() function and make sure the event
is not built in SPL.

Signed-off-by: Simon Glass

disable NFS support by default

2023-07-14T19:21:07+00:00

While NFS is widely used in data centres, and private
networks it's quite a nuanced usecase for device firmware.
A lot of devices already disable it.

Various network protocols should really be opt in, not opt
out, because they add extra size and are potential attack
vectors from a security PoV. In the NFS case it doesn't
really make sense for a lot of devices like tables, SBCs etc.
It's also something we don't really want for SystemReady-IR
due to security concerns.

Signed-off-by: Peter Robinson 
Reviewed-by: Tom Rini 
Reviewed-by: Ilias Apalodimas