#
18e791c4 |
|
22-Apr-2024 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
db04ff42 |
|
10-Jan-2024 |
Tom Rini <trini@konsulko.com> |
mtd: Make CONFIG_MTD be the gate symbol for the menu The help for CONFIG_MTD explains that it needs to be enabled for various things like NAND, etc to be available. It however then doesn't enforce this dependency and so if you have none of these systems present you still need to disable a number of options. Fix this by making places that select/imply one type of flash, but did not do the same, also do this for "MTD". Make boards which hadn't been enabling MTD already but need it now, do so. In a few places, disable CONFIG_CMD_MTDPARTS as it wasn't previously enabled but was now being implied. Signed-off-by: Tom Rini <trini@konsulko.com> |
#
b35df87a |
|
04-Nov-2023 |
Sean Anderson <seanga2@gmail.com> |
mtd: Rename SPL_MTD_SUPPORT to SPL_MTD Rename SPL_MTD_SUPPORT to SPL_MTD in order to match MTD. This allows using CONFIG_IS_ENABLED to test for MTD support. Signed-off-by: Sean Anderson <seanga2@gmail.com> |
#
1a1d48e3 |
|
03-Aug-2023 |
Andrew Davis <afd@ti.com> |
configs: Make TI_SECURE_DEVICE default for K3 All K3 boards now are secure by default, instead of setting this in each defconfig, make it implied by the ARCH config. The only exception is IOT2050, which I do not believe will have any problems with being a TI_SECURE_DEVICE, but for now turn it off to keep its config the same. Signed-off-by: Andrew Davis <afd@ti.com> Tested-by: Tom Rini <trini@konsulko.com> |
#
82e26e0d |
|
26-Sep-2023 |
Simon Glass <sjg@chromium.org> |
spl: Use CONFIG_SPL... instead of CONFIG_..._SPL_... We like to put the SPL first so it is clear that it relates to SPL. Rename various malloc-related options which have crept in, to stick to this convention. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> Reviewed-by: Martyn Welch <martyn.welch@collabora.com> Reviewed-by: Svyatoslav Ryhel <clamor95@gmail.com> |
#
c960c0fd |
|
01-May-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
411faba7 |
|
17-Mar-2023 |
Bryan Brattlof <bb@ti.com> |
configs: am62ax: enable secure device configs by default TI's security enforcing SoCs will authenticate each binary it loads by comparing it's signature with keys etched into the SoC during the boot up process. The am62ax family of SoCs by default will have some level of security enforcement checking. To keep things as simple as possible, enable the CONFIG_TI_SECURE_DEVICE options by default so all levels of secure SoCs will work out of the box Enable the CONFIG_TI_SECURE_DEVICE by default Signed-off-by: Bryan Brattlof <bb@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Kamlesh Gurudasani <kamlesh@ti.com> |
#
fcb5117d |
|
17-Feb-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
940b7128 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: am62a: move stack and heap to HSM RAM Texas Instruments has begun enabling security setting on the SoCs they produce to instruct ROM and TIFS to begin protecting the Security Management Subsystem (SMS) from other binaries we load into the chip by default. One way ROM does this is by enabling firewalls to protect the OCSRAM region it's using during bootup. Only after TIFS has started (and had time to disable the OCSRAM firewall region) will we have write access to the region. This means we will need to move the stack & heap from OCSRAM to HSM RAM and reduce the size of BSS and the SPL to allow it to fit properly. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
d1256121 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: restrict am62ax wakup SPL size In its current form, the am62a's wakeup SPL is fairly small, however this will not remain as more boot modes are eventually added. To protect us from overflowing our ~256k of HSM SRAM, add limits and check during the wakeup SPL build. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
719bd650 |
|
03-Nov-2022 |
Bryan Brattlof <bb@ti.com> |
configs: introduce configs for the am62a Introduce the minimum configs, only SD-MMC and UART boot related settings, to serve as a good starting point for the am62a as we add more functionality. Signed-off-by: Bryan Brattlof <bb@ti.com> [trini: Disable CONFIG_NET as it's not used, in both platforms] Signed-off-by: Tom Rini <trini@konsulko.com> |
#
db04ff42 |
|
10-Jan-2024 |
Tom Rini <trini@konsulko.com> |
mtd: Make CONFIG_MTD be the gate symbol for the menu The help for CONFIG_MTD explains that it needs to be enabled for various things like NAND, etc to be available. It however then doesn't enforce this dependency and so if you have none of these systems present you still need to disable a number of options. Fix this by making places that select/imply one type of flash, but did not do the same, also do this for "MTD". Make boards which hadn't been enabling MTD already but need it now, do so. In a few places, disable CONFIG_CMD_MTDPARTS as it wasn't previously enabled but was now being implied. Signed-off-by: Tom Rini <trini@konsulko.com> |
#
b35df87a |
|
04-Nov-2023 |
Sean Anderson <seanga2@gmail.com> |
mtd: Rename SPL_MTD_SUPPORT to SPL_MTD Rename SPL_MTD_SUPPORT to SPL_MTD in order to match MTD. This allows using CONFIG_IS_ENABLED to test for MTD support. Signed-off-by: Sean Anderson <seanga2@gmail.com> |
#
1a1d48e3 |
|
03-Aug-2023 |
Andrew Davis <afd@ti.com> |
configs: Make TI_SECURE_DEVICE default for K3 All K3 boards now are secure by default, instead of setting this in each defconfig, make it implied by the ARCH config. The only exception is IOT2050, which I do not believe will have any problems with being a TI_SECURE_DEVICE, but for now turn it off to keep its config the same. Signed-off-by: Andrew Davis <afd@ti.com> Tested-by: Tom Rini <trini@konsulko.com> |
#
82e26e0d |
|
26-Sep-2023 |
Simon Glass <sjg@chromium.org> |
spl: Use CONFIG_SPL... instead of CONFIG_..._SPL_... We like to put the SPL first so it is clear that it relates to SPL. Rename various malloc-related options which have crept in, to stick to this convention. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> Reviewed-by: Martyn Welch <martyn.welch@collabora.com> Reviewed-by: Svyatoslav Ryhel <clamor95@gmail.com> |
#
c960c0fd |
|
01-May-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
411faba7 |
|
17-Mar-2023 |
Bryan Brattlof <bb@ti.com> |
configs: am62ax: enable secure device configs by default TI's security enforcing SoCs will authenticate each binary it loads by comparing it's signature with keys etched into the SoC during the boot up process. The am62ax family of SoCs by default will have some level of security enforcement checking. To keep things as simple as possible, enable the CONFIG_TI_SECURE_DEVICE options by default so all levels of secure SoCs will work out of the box Enable the CONFIG_TI_SECURE_DEVICE by default Signed-off-by: Bryan Brattlof <bb@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Kamlesh Gurudasani <kamlesh@ti.com> |
#
fcb5117d |
|
17-Feb-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
940b7128 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: am62a: move stack and heap to HSM RAM Texas Instruments has begun enabling security setting on the SoCs they produce to instruct ROM and TIFS to begin protecting the Security Management Subsystem (SMS) from other binaries we load into the chip by default. One way ROM does this is by enabling firewalls to protect the OCSRAM region it's using during bootup. Only after TIFS has started (and had time to disable the OCSRAM firewall region) will we have write access to the region. This means we will need to move the stack & heap from OCSRAM to HSM RAM and reduce the size of BSS and the SPL to allow it to fit properly. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
d1256121 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: restrict am62ax wakup SPL size In its current form, the am62a's wakeup SPL is fairly small, however this will not remain as more boot modes are eventually added. To protect us from overflowing our ~256k of HSM SRAM, add limits and check during the wakeup SPL build. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
719bd650 |
|
03-Nov-2022 |
Bryan Brattlof <bb@ti.com> |
configs: introduce configs for the am62a Introduce the minimum configs, only SD-MMC and UART boot related settings, to serve as a good starting point for the am62a as we add more functionality. Signed-off-by: Bryan Brattlof <bb@ti.com> [trini: Disable CONFIG_NET as it's not used, in both platforms] Signed-off-by: Tom Rini <trini@konsulko.com> |
#
b35df87a |
|
04-Nov-2023 |
Sean Anderson <seanga2@gmail.com> |
mtd: Rename SPL_MTD_SUPPORT to SPL_MTD Rename SPL_MTD_SUPPORT to SPL_MTD in order to match MTD. This allows using CONFIG_IS_ENABLED to test for MTD support. Signed-off-by: Sean Anderson <seanga2@gmail.com> |
#
1a1d48e3 |
|
03-Aug-2023 |
Andrew Davis <afd@ti.com> |
configs: Make TI_SECURE_DEVICE default for K3 All K3 boards now are secure by default, instead of setting this in each defconfig, make it implied by the ARCH config. The only exception is IOT2050, which I do not believe will have any problems with being a TI_SECURE_DEVICE, but for now turn it off to keep its config the same. Signed-off-by: Andrew Davis <afd@ti.com> Tested-by: Tom Rini <trini@konsulko.com> |
#
82e26e0d |
|
26-Sep-2023 |
Simon Glass <sjg@chromium.org> |
spl: Use CONFIG_SPL... instead of CONFIG_..._SPL_... We like to put the SPL first so it is clear that it relates to SPL. Rename various malloc-related options which have crept in, to stick to this convention. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> Reviewed-by: Martyn Welch <martyn.welch@collabora.com> Reviewed-by: Svyatoslav Ryhel <clamor95@gmail.com> |
#
c960c0fd |
|
01-May-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
411faba7 |
|
17-Mar-2023 |
Bryan Brattlof <bb@ti.com> |
configs: am62ax: enable secure device configs by default TI's security enforcing SoCs will authenticate each binary it loads by comparing it's signature with keys etched into the SoC during the boot up process. The am62ax family of SoCs by default will have some level of security enforcement checking. To keep things as simple as possible, enable the CONFIG_TI_SECURE_DEVICE options by default so all levels of secure SoCs will work out of the box Enable the CONFIG_TI_SECURE_DEVICE by default Signed-off-by: Bryan Brattlof <bb@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Kamlesh Gurudasani <kamlesh@ti.com> |
#
fcb5117d |
|
17-Feb-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
940b7128 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: am62a: move stack and heap to HSM RAM Texas Instruments has begun enabling security setting on the SoCs they produce to instruct ROM and TIFS to begin protecting the Security Management Subsystem (SMS) from other binaries we load into the chip by default. One way ROM does this is by enabling firewalls to protect the OCSRAM region it's using during bootup. Only after TIFS has started (and had time to disable the OCSRAM firewall region) will we have write access to the region. This means we will need to move the stack & heap from OCSRAM to HSM RAM and reduce the size of BSS and the SPL to allow it to fit properly. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
d1256121 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: restrict am62ax wakup SPL size In its current form, the am62a's wakeup SPL is fairly small, however this will not remain as more boot modes are eventually added. To protect us from overflowing our ~256k of HSM SRAM, add limits and check during the wakeup SPL build. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
719bd650 |
|
03-Nov-2022 |
Bryan Brattlof <bb@ti.com> |
configs: introduce configs for the am62a Introduce the minimum configs, only SD-MMC and UART boot related settings, to serve as a good starting point for the am62a as we add more functionality. Signed-off-by: Bryan Brattlof <bb@ti.com> [trini: Disable CONFIG_NET as it's not used, in both platforms] Signed-off-by: Tom Rini <trini@konsulko.com> |
#
1a1d48e3 |
|
03-Aug-2023 |
Andrew Davis <afd@ti.com> |
configs: Make TI_SECURE_DEVICE default for K3 All K3 boards now are secure by default, instead of setting this in each defconfig, make it implied by the ARCH config. The only exception is IOT2050, which I do not believe will have any problems with being a TI_SECURE_DEVICE, but for now turn it off to keep its config the same. Signed-off-by: Andrew Davis <afd@ti.com> Tested-by: Tom Rini <trini@konsulko.com> |
#
82e26e0d |
|
26-Sep-2023 |
Simon Glass <sjg@chromium.org> |
spl: Use CONFIG_SPL... instead of CONFIG_..._SPL_... We like to put the SPL first so it is clear that it relates to SPL. Rename various malloc-related options which have crept in, to stick to this convention. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> Reviewed-by: Martyn Welch <martyn.welch@collabora.com> Reviewed-by: Svyatoslav Ryhel <clamor95@gmail.com> |
#
c960c0fd |
|
01-May-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
411faba7 |
|
17-Mar-2023 |
Bryan Brattlof <bb@ti.com> |
configs: am62ax: enable secure device configs by default TI's security enforcing SoCs will authenticate each binary it loads by comparing it's signature with keys etched into the SoC during the boot up process. The am62ax family of SoCs by default will have some level of security enforcement checking. To keep things as simple as possible, enable the CONFIG_TI_SECURE_DEVICE options by default so all levels of secure SoCs will work out of the box Enable the CONFIG_TI_SECURE_DEVICE by default Signed-off-by: Bryan Brattlof <bb@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Kamlesh Gurudasani <kamlesh@ti.com> |
#
fcb5117d |
|
17-Feb-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
940b7128 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: am62a: move stack and heap to HSM RAM Texas Instruments has begun enabling security setting on the SoCs they produce to instruct ROM and TIFS to begin protecting the Security Management Subsystem (SMS) from other binaries we load into the chip by default. One way ROM does this is by enabling firewalls to protect the OCSRAM region it's using during bootup. Only after TIFS has started (and had time to disable the OCSRAM firewall region) will we have write access to the region. This means we will need to move the stack & heap from OCSRAM to HSM RAM and reduce the size of BSS and the SPL to allow it to fit properly. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
d1256121 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: restrict am62ax wakup SPL size In its current form, the am62a's wakeup SPL is fairly small, however this will not remain as more boot modes are eventually added. To protect us from overflowing our ~256k of HSM SRAM, add limits and check during the wakeup SPL build. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
719bd650 |
|
03-Nov-2022 |
Bryan Brattlof <bb@ti.com> |
configs: introduce configs for the am62a Introduce the minimum configs, only SD-MMC and UART boot related settings, to serve as a good starting point for the am62a as we add more functionality. Signed-off-by: Bryan Brattlof <bb@ti.com> [trini: Disable CONFIG_NET as it's not used, in both platforms] Signed-off-by: Tom Rini <trini@konsulko.com> |
#
82e26e0d |
|
26-Sep-2023 |
Simon Glass <sjg@chromium.org> |
spl: Use CONFIG_SPL... instead of CONFIG_..._SPL_... We like to put the SPL first so it is clear that it relates to SPL. Rename various malloc-related options which have crept in, to stick to this convention. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> Reviewed-by: Martyn Welch <martyn.welch@collabora.com> Reviewed-by: Svyatoslav Ryhel <clamor95@gmail.com> |
#
c960c0fd |
|
01-May-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
411faba7 |
|
17-Mar-2023 |
Bryan Brattlof <bb@ti.com> |
configs: am62ax: enable secure device configs by default TI's security enforcing SoCs will authenticate each binary it loads by comparing it's signature with keys etched into the SoC during the boot up process. The am62ax family of SoCs by default will have some level of security enforcement checking. To keep things as simple as possible, enable the CONFIG_TI_SECURE_DEVICE options by default so all levels of secure SoCs will work out of the box Enable the CONFIG_TI_SECURE_DEVICE by default Signed-off-by: Bryan Brattlof <bb@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Kamlesh Gurudasani <kamlesh@ti.com> |
#
fcb5117d |
|
17-Feb-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
940b7128 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: am62a: move stack and heap to HSM RAM Texas Instruments has begun enabling security setting on the SoCs they produce to instruct ROM and TIFS to begin protecting the Security Management Subsystem (SMS) from other binaries we load into the chip by default. One way ROM does this is by enabling firewalls to protect the OCSRAM region it's using during bootup. Only after TIFS has started (and had time to disable the OCSRAM firewall region) will we have write access to the region. This means we will need to move the stack & heap from OCSRAM to HSM RAM and reduce the size of BSS and the SPL to allow it to fit properly. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
d1256121 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: restrict am62ax wakup SPL size In its current form, the am62a's wakeup SPL is fairly small, however this will not remain as more boot modes are eventually added. To protect us from overflowing our ~256k of HSM SRAM, add limits and check during the wakeup SPL build. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
719bd650 |
|
03-Nov-2022 |
Bryan Brattlof <bb@ti.com> |
configs: introduce configs for the am62a Introduce the minimum configs, only SD-MMC and UART boot related settings, to serve as a good starting point for the am62a as we add more functionality. Signed-off-by: Bryan Brattlof <bb@ti.com> [trini: Disable CONFIG_NET as it's not used, in both platforms] Signed-off-by: Tom Rini <trini@konsulko.com> |
#
c960c0fd |
|
01-May-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
411faba7 |
|
17-Mar-2023 |
Bryan Brattlof <bb@ti.com> |
configs: am62ax: enable secure device configs by default TI's security enforcing SoCs will authenticate each binary it loads by comparing it's signature with keys etched into the SoC during the boot up process. The am62ax family of SoCs by default will have some level of security enforcement checking. To keep things as simple as possible, enable the CONFIG_TI_SECURE_DEVICE options by default so all levels of secure SoCs will work out of the box Enable the CONFIG_TI_SECURE_DEVICE by default Signed-off-by: Bryan Brattlof <bb@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Kamlesh Gurudasani <kamlesh@ti.com> |
#
fcb5117d |
|
17-Feb-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
940b7128 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: am62a: move stack and heap to HSM RAM Texas Instruments has begun enabling security setting on the SoCs they produce to instruct ROM and TIFS to begin protecting the Security Management Subsystem (SMS) from other binaries we load into the chip by default. One way ROM does this is by enabling firewalls to protect the OCSRAM region it's using during bootup. Only after TIFS has started (and had time to disable the OCSRAM firewall region) will we have write access to the region. This means we will need to move the stack & heap from OCSRAM to HSM RAM and reduce the size of BSS and the SPL to allow it to fit properly. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
d1256121 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: restrict am62ax wakup SPL size In its current form, the am62a's wakeup SPL is fairly small, however this will not remain as more boot modes are eventually added. To protect us from overflowing our ~256k of HSM SRAM, add limits and check during the wakeup SPL build. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
719bd650 |
|
03-Nov-2022 |
Bryan Brattlof <bb@ti.com> |
configs: introduce configs for the am62a Introduce the minimum configs, only SD-MMC and UART boot related settings, to serve as a good starting point for the am62a as we add more functionality. Signed-off-by: Bryan Brattlof <bb@ti.com> [trini: Disable CONFIG_NET as it's not used, in both platforms] Signed-off-by: Tom Rini <trini@konsulko.com> |
#
411faba7 |
|
17-Mar-2023 |
Bryan Brattlof <bb@ti.com> |
configs: am62ax: enable secure device configs by default TI's security enforcing SoCs will authenticate each binary it loads by comparing it's signature with keys etched into the SoC during the boot up process. The am62ax family of SoCs by default will have some level of security enforcement checking. To keep things as simple as possible, enable the CONFIG_TI_SECURE_DEVICE options by default so all levels of secure SoCs will work out of the box Enable the CONFIG_TI_SECURE_DEVICE by default Signed-off-by: Bryan Brattlof <bb@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Kamlesh Gurudasani <kamlesh@ti.com> |
#
fcb5117d |
|
17-Feb-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
940b7128 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: am62a: move stack and heap to HSM RAM Texas Instruments has begun enabling security setting on the SoCs they produce to instruct ROM and TIFS to begin protecting the Security Management Subsystem (SMS) from other binaries we load into the chip by default. One way ROM does this is by enabling firewalls to protect the OCSRAM region it's using during bootup. Only after TIFS has started (and had time to disable the OCSRAM firewall region) will we have write access to the region. This means we will need to move the stack & heap from OCSRAM to HSM RAM and reduce the size of BSS and the SPL to allow it to fit properly. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
d1256121 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: restrict am62ax wakup SPL size In its current form, the am62a's wakeup SPL is fairly small, however this will not remain as more boot modes are eventually added. To protect us from overflowing our ~256k of HSM SRAM, add limits and check during the wakeup SPL build. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
719bd650 |
|
03-Nov-2022 |
Bryan Brattlof <bb@ti.com> |
configs: introduce configs for the am62a Introduce the minimum configs, only SD-MMC and UART boot related settings, to serve as a good starting point for the am62a as we add more functionality. Signed-off-by: Bryan Brattlof <bb@ti.com> [trini: Disable CONFIG_NET as it's not used, in both platforms] Signed-off-by: Tom Rini <trini@konsulko.com> |
#
fcb5117d |
|
17-Feb-2023 |
Tom Rini <trini@konsulko.com> |
configs: Resync with savedefconfig Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com> |
#
940b7128 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: am62a: move stack and heap to HSM RAM Texas Instruments has begun enabling security setting on the SoCs they produce to instruct ROM and TIFS to begin protecting the Security Management Subsystem (SMS) from other binaries we load into the chip by default. One way ROM does this is by enabling firewalls to protect the OCSRAM region it's using during bootup. Only after TIFS has started (and had time to disable the OCSRAM firewall region) will we have write access to the region. This means we will need to move the stack & heap from OCSRAM to HSM RAM and reduce the size of BSS and the SPL to allow it to fit properly. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
d1256121 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: restrict am62ax wakup SPL size In its current form, the am62a's wakeup SPL is fairly small, however this will not remain as more boot modes are eventually added. To protect us from overflowing our ~256k of HSM SRAM, add limits and check during the wakeup SPL build. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
719bd650 |
|
03-Nov-2022 |
Bryan Brattlof <bb@ti.com> |
configs: introduce configs for the am62a Introduce the minimum configs, only SD-MMC and UART boot related settings, to serve as a good starting point for the am62a as we add more functionality. Signed-off-by: Bryan Brattlof <bb@ti.com> [trini: Disable CONFIG_NET as it's not used, in both platforms] Signed-off-by: Tom Rini <trini@konsulko.com> |
#
940b7128 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: am62a: move stack and heap to HSM RAM Texas Instruments has begun enabling security setting on the SoCs they produce to instruct ROM and TIFS to begin protecting the Security Management Subsystem (SMS) from other binaries we load into the chip by default. One way ROM does this is by enabling firewalls to protect the OCSRAM region it's using during bootup. Only after TIFS has started (and had time to disable the OCSRAM firewall region) will we have write access to the region. This means we will need to move the stack & heap from OCSRAM to HSM RAM and reduce the size of BSS and the SPL to allow it to fit properly. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
d1256121 |
|
23-Dec-2022 |
Bryan Brattlof <bb@ti.com> |
configs: restrict am62ax wakup SPL size In its current form, the am62a's wakeup SPL is fairly small, however this will not remain as more boot modes are eventually added. To protect us from overflowing our ~256k of HSM SRAM, add limits and check during the wakeup SPL build. Signed-off-by: Bryan Brattlof <bb@ti.com> |
#
719bd650 |
|
03-Nov-2022 |
Bryan Brattlof <bb@ti.com> |
configs: introduce configs for the am62a Introduce the minimum configs, only SD-MMC and UART boot related settings, to serve as a good starting point for the am62a as we add more functionality. Signed-off-by: Bryan Brattlof <bb@ti.com> [trini: Disable CONFIG_NET as it's not used, in both platforms] Signed-off-by: Tom Rini <trini@konsulko.com> |