[PATCH] configs: am62x: enable secure device configs by default
Enable the CONFIG_TI_SECURE_DEVICE by default Non-HS devices will continue to boot due to runtime device type detection. 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 am62x 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 Signed-off-by: Praneeth Bajjuri Signed-off-by: Kamlesh Gurudasani Signed-off-by: Bryan Brattlof --- configs/am62x_evm_a53_defconfig | 1 + configs/am62x_evm_r5_defconfig | 1 + 2 files changed, 2 insertions(+) diff --git a/configs/am62x_evm_a53_defconfig b/configs/am62x_evm_a53_defconfig index cc9c8eab3e..fc76d88727 100644 --- a/configs/am62x_evm_a53_defconfig +++ b/configs/am62x_evm_a53_defconfig @@ -1,5 +1,6 @@ CONFIG_ARM=y CONFIG_ARCH_K3=y +CONFIG_TI_SECURE_DEVICE=y CONFIG_SYS_MALLOC_F_LEN=0x8000 CONFIG_SPL_LIBCOMMON_SUPPORT=y CONFIG_SPL_LIBGENERIC_SUPPORT=y diff --git a/configs/am62x_evm_r5_defconfig b/configs/am62x_evm_r5_defconfig index 44a9130d99..cab8c820f9 100644 --- a/configs/am62x_evm_r5_defconfig +++ b/configs/am62x_evm_r5_defconfig @@ -1,5 +1,6 @@ CONFIG_ARM=y CONFIG_ARCH_K3=y +CONFIG_TI_SECURE_DEVICE=y CONFIG_SYS_MALLOC_LEN=0x0800 CONFIG_SYS_MALLOC_F_LEN=0x9000 CONFIG_SPL_LIBCOMMON_SUPPORT=y -- 2.17.1
Re: [PATCH v3 00/10] AM642-EVM: Add USB support
On 6/4/21 11:53 AM, Praneeth Bajjuri wrote: Aswath, Suman, Dave, Gowtham, Vignesh On 6/4/21 11:49 AM, Aswath Govindraju wrote: Hi Praneeth, On 04/06/21 10:18 pm, Praneeth Bajjuri wrote: On 6/4/21 11:30 AM, Aswath Govindraju wrote: The following series of patches add support for the following - Kconfig symbol for giving the load address for ATF - USB Mass storage boot mode in AM642-EVM - DFU boot mode in AM642-EVM - Host and peripheral modes for AM642-EVM in U-Boot - Set the USB PHY core voltage to 0.85V changes since v2, - Increased the max size of ATF in patch 9 Please confirm if this is tested on ATF 2.5 too. Sorry, for not mentioning it. Yes, this series was tested using ATF 2.5. Ok , pulling to ti-u-boot. Aswath: 1. Please send the updated series to upstream u-boot as well. 2. post the kernel dts change to mainline as well. Vignesh, Assuming you are pulling the KIG patch too. Suman/Dave/Gowtham, Assuming you are pulling the kernel patch too. Please ignore this mail. was reviewing product baseline for same feature. Thanks, Aswath - Added reviewed-by from Suman Anna in patch 1 - Reworded the subject of patch 8 changes since v1, - Corrected the default load address of ATF to 0x7000 Aswath Govindraju (10): tools: k3_fit_atf: Add support for providing ATF load address using a Kconfig symbol arm: mach-k3: am642_init: Add support for USB boot mode arm: mach-k3: am642_init: Do USB fixups to facilitate host and device boot modes board: ti: am64x: Set the core voltage of USB PHY to 0.85V arm: dts: k3-am64-main: Add USB DT nodes arm: dts: k3-am642-*-evm: Add USB support arm: dts: k3-am642-evm-u-boot: Add U-Boot tags and fix the dr_mode to peripheral for USB subsystem configs: am64x_evm_*_defconfig: Rearrange the components in SRAM to satisfy the limitations for USB DFU boot mode arm: dts: k3-am64-main: Update the location of ATF in SRAM and increase its max size configs: am64: Enable configs to support USB host and device modes arch/arm/dts/k3-am64-main.dtsi | 32 - arch/arm/dts/k3-am642-evm-u-boot.dtsi | 13 ++ arch/arm/dts/k3-am642-evm.dts | 18 arch/arm/dts/k3-am642-r5-evm.dts | 18 arch/arm/mach-k3/Kconfig | 7 +++ arch/arm/mach-k3/am642_init.c | 46 ++- arch/arm/mach-k3/config.mk | 1 + arch/arm/mach-k3/include/mach/am64_hardware.h | 11 +++-- arch/arm/mach-k3/include/mach/am64_spl.h | 6 ++- board/ti/am64x/evm.c | 14 ++ configs/am64x_evm_a53_defconfig | 40 configs/am64x_evm_r5_defconfig | 38 +-- include/configs/am64x_evm.h | 15 +- tools/k3_fit_atf.sh | 9 ++-- 14 files changed, 251 insertions(+), 17 deletions(-)
Re: [PATCH v3 00/10] AM642-EVM: Add USB support
Aswath, Suman, Dave, Gowtham, Vignesh On 6/4/21 11:49 AM, Aswath Govindraju wrote: Hi Praneeth, On 04/06/21 10:18 pm, Praneeth Bajjuri wrote: On 6/4/21 11:30 AM, Aswath Govindraju wrote: The following series of patches add support for the following - Kconfig symbol for giving the load address for ATF - USB Mass storage boot mode in AM642-EVM - DFU boot mode in AM642-EVM - Host and peripheral modes for AM642-EVM in U-Boot - Set the USB PHY core voltage to 0.85V changes since v2, - Increased the max size of ATF in patch 9 Please confirm if this is tested on ATF 2.5 too. Sorry, for not mentioning it. Yes, this series was tested using ATF 2.5. Ok , pulling to ti-u-boot. Aswath: 1. Please send the updated series to upstream u-boot as well. 2. post the kernel dts change to mainline as well. Vignesh, Assuming you are pulling the KIG patch too. Suman/Dave/Gowtham, Assuming you are pulling the kernel patch too. Thanks, Aswath - Added reviewed-by from Suman Anna in patch 1 - Reworded the subject of patch 8 changes since v1, - Corrected the default load address of ATF to 0x7000 Aswath Govindraju (10): tools: k3_fit_atf: Add support for providing ATF load address using a Kconfig symbol arm: mach-k3: am642_init: Add support for USB boot mode arm: mach-k3: am642_init: Do USB fixups to facilitate host and device boot modes board: ti: am64x: Set the core voltage of USB PHY to 0.85V arm: dts: k3-am64-main: Add USB DT nodes arm: dts: k3-am642-*-evm: Add USB support arm: dts: k3-am642-evm-u-boot: Add U-Boot tags and fix the dr_mode to peripheral for USB subsystem configs: am64x_evm_*_defconfig: Rearrange the components in SRAM to satisfy the limitations for USB DFU boot mode arm: dts: k3-am64-main: Update the location of ATF in SRAM and increase its max size configs: am64: Enable configs to support USB host and device modes arch/arm/dts/k3-am64-main.dtsi | 32 - arch/arm/dts/k3-am642-evm-u-boot.dtsi | 13 ++ arch/arm/dts/k3-am642-evm.dts | 18 arch/arm/dts/k3-am642-r5-evm.dts | 18 arch/arm/mach-k3/Kconfig | 7 +++ arch/arm/mach-k3/am642_init.c | 46 ++- arch/arm/mach-k3/config.mk | 1 + arch/arm/mach-k3/include/mach/am64_hardware.h | 11 +++-- arch/arm/mach-k3/include/mach/am64_spl.h | 6 ++- board/ti/am64x/evm.c | 14 ++ configs/am64x_evm_a53_defconfig | 40 configs/am64x_evm_r5_defconfig | 38 +-- include/configs/am64x_evm.h | 15 +- tools/k3_fit_atf.sh | 9 ++-- 14 files changed, 251 insertions(+), 17 deletions(-)
Re: [PATCH v3 00/10] AM642-EVM: Add USB support
On 6/4/21 11:30 AM, Aswath Govindraju wrote: The following series of patches add support for the following - Kconfig symbol for giving the load address for ATF - USB Mass storage boot mode in AM642-EVM - DFU boot mode in AM642-EVM - Host and peripheral modes for AM642-EVM in U-Boot - Set the USB PHY core voltage to 0.85V changes since v2, - Increased the max size of ATF in patch 9 Please confirm if this is tested on ATF 2.5 too. - Added reviewed-by from Suman Anna in patch 1 - Reworded the subject of patch 8 changes since v1, - Corrected the default load address of ATF to 0x7000 Aswath Govindraju (10): tools: k3_fit_atf: Add support for providing ATF load address using a Kconfig symbol arm: mach-k3: am642_init: Add support for USB boot mode arm: mach-k3: am642_init: Do USB fixups to facilitate host and device boot modes board: ti: am64x: Set the core voltage of USB PHY to 0.85V arm: dts: k3-am64-main: Add USB DT nodes arm: dts: k3-am642-*-evm: Add USB support arm: dts: k3-am642-evm-u-boot: Add U-Boot tags and fix the dr_mode to peripheral for USB subsystem configs: am64x_evm_*_defconfig: Rearrange the components in SRAM to satisfy the limitations for USB DFU boot mode arm: dts: k3-am64-main: Update the location of ATF in SRAM and increase its max size configs: am64: Enable configs to support USB host and device modes arch/arm/dts/k3-am64-main.dtsi| 32 - arch/arm/dts/k3-am642-evm-u-boot.dtsi | 13 ++ arch/arm/dts/k3-am642-evm.dts | 18 arch/arm/dts/k3-am642-r5-evm.dts | 18 arch/arm/mach-k3/Kconfig | 7 +++ arch/arm/mach-k3/am642_init.c | 46 ++- arch/arm/mach-k3/config.mk| 1 + arch/arm/mach-k3/include/mach/am64_hardware.h | 11 +++-- arch/arm/mach-k3/include/mach/am64_spl.h | 6 ++- board/ti/am64x/evm.c | 14 ++ configs/am64x_evm_a53_defconfig | 40 configs/am64x_evm_r5_defconfig| 38 +-- include/configs/am64x_evm.h | 15 +- tools/k3_fit_atf.sh | 9 ++-- 14 files changed, 251 insertions(+), 17 deletions(-)
[U-Boot] [PATCH] arm: ti: boot: Fix am57xx evm fdtfile name
am57xx evm uses am57xx-evm-reva3.dtb. update findfdt to pick the correct default dtb Signed-off-by: Praneeth Bajjuri --- include/environment/ti/boot.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/environment/ti/boot.h b/include/environment/ti/boot.h index 86ff6d3ea7c6..c9ad3046acaa 100644 --- a/include/environment/ti/boot.h +++ b/include/environment/ti/boot.h @@ -125,7 +125,7 @@ "if test $board_name = am57xx_evm; then " \ "setenv fdtfile am57xx-beagle-x15.dtb; fi;" \ "if test $board_name = am57xx_evm_reva3; then " \ - "setenv fdtfile am57xx-beagle-x15.dtb; fi;" \ + "setenv fdtfile am57xx-evm-reva3.dtb; fi;" \ "if test $board_name = am571x_idk; then " \ "setenv fdtfile am571x-idk.dtb; fi;" \ "if test $fdtfile = undefined; then " \ -- 2.7.4 ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
[U-Boot] [PATCH] configs: am57xx: change default board name to beagle_x15
beagleboard x15 is the first supported platform variant of am57xx
in AOSP (android open source project) now.
changing board name to stay in consistent with aosp target name.
Signed-off-by: Praneeth Bajjuri
---
configs/am57xx_evm_defconfig| 2 +-
configs/am57xx_hs_evm_defconfig | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/configs/am57xx_evm_defconfig b/configs/am57xx_evm_defconfig
index 1572dc80db03..07ab01e921bf 100644
--- a/configs/am57xx_evm_defconfig
+++ b/configs/am57xx_evm_defconfig
@@ -14,7 +14,7 @@ CONFIG_NR_DRAM_BANKS=2
CONFIG_SPL_LOAD_FIT=y
CONFIG_OF_BOARD_SETUP=y
CONFIG_USE_BOOTARGS=y
-CONFIG_BOOTARGS="androidboot.serialno=${serial#} console=ttyS2,115200
androidboot.console=ttyS2 androidboot.hardware=am57xevmboard"
+CONFIG_BOOTARGS="androidboot.serialno=${serial#} console=ttyS2,115200
androidboot.console=ttyS2 androidboot.hardware=beagle_x15board"
# CONFIG_USE_BOOTCOMMAND is not set
CONFIG_SYS_CONSOLE_INFO_QUIET=y
# CONFIG_MISC_INIT_R is not set
diff --git a/configs/am57xx_hs_evm_defconfig b/configs/am57xx_hs_evm_defconfig
index 895719286dc5..0522c10b01c4 100644
--- a/configs/am57xx_hs_evm_defconfig
+++ b/configs/am57xx_hs_evm_defconfig
@@ -20,7 +20,7 @@ CONFIG_SPL_LOAD_FIT=y
CONFIG_SPL_FIT_IMAGE_POST_PROCESS=y
CONFIG_OF_BOARD_SETUP=y
CONFIG_USE_BOOTARGS=y
-CONFIG_BOOTARGS="androidboot.serialno=${serial#} console=ttyS2,115200
androidboot.console=ttyS2 androidboot.hardware=am57xevmboard"
+CONFIG_BOOTARGS="androidboot.serialno=${serial#} console=ttyS2,115200
androidboot.console=ttyS2 androidboot.hardware=beagle_x15board"
# CONFIG_USE_BOOTCOMMAND is not set
CONFIG_SYS_CONSOLE_INFO_QUIET=y
# CONFIG_MISC_INIT_R is not set
--
2.7.4
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
[U-Boot] [PATCH 0/2] Boot android with FIT image
Enable the FDT library overlay support for all TI SOC family and while at it Enable android over emmc by default thru FIT image Praneeth Bajjuri (2): configs: TI: Enable FIT Library overlay support env: ti: android: boot with FIT Image include/environment/ti/boot.h | 3 ++- lib/Kconfig | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) -- 1.9.1 ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
[U-Boot] [PATCH 1/2] configs: TI: Enable FIT Library overlay support
Enable the FDT library overlay support for all TI SOC family. Without this option, when Loading fdt from FIT image, the following warning is seen. "config with overlays but CONFIG_OF_LIBFDT_OVERLAY not set". Signed-off-by: Praneeth Bajjuri <prane...@ti.com> Suggested-by: Andrew F.Davis <a...@ti.com> --- lib/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/lib/Kconfig b/lib/Kconfig index 436b90f..6d5306a 100644 --- a/lib/Kconfig +++ b/lib/Kconfig @@ -252,6 +252,7 @@ config OF_LIBFDT config OF_LIBFDT_OVERLAY bool "Enable the FDT library overlay support" + default y if ARCH_OMAP2PLUS || ARCH_KEYSTONE help This enables the FDT library (libfdt) overlay support. -- 1.9.1 ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
[U-Boot] [PATCH 2/2] env: ti: android: boot with FIT Image
Boot android over emmc by default thru FIT image
Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
Suggested-by: Andrew F.Davis <a...@ti.com>
---
include/environment/ti/boot.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/environment/ti/boot.h b/include/environment/ti/boot.h
index 24b7783..a1767b4 100644
--- a/include/environment/ti/boot.h
+++ b/include/environment/ti/boot.h
@@ -37,6 +37,7 @@
"run mmcboot;\0" \
"emmc_android_boot=" \
"echo Trying to boot Android from eMMC ...; " \
+ "run update_to_fit; " \
"setenv eval_bootargs setenv bootargs $bootargs; " \
"run eval_bootargs; " \
"setenv mmcdev 1; " \
@@ -49,7 +50,7 @@
"part size mmc ${mmcdev} boot boot_size; " \
"mmc read ${fdtaddr} ${fdt_start} ${fdt_size}; " \
"mmc read ${loadaddr} ${boot_start} ${boot_size}; " \
- "bootm $loadaddr $loadaddr $fdtaddr;\0"
+ "bootm ${loadaddr}#${fdtfile};\0 "
#ifdef CONFIG_OMAP54XX
--
1.9.1
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
[U-Boot] [PATCH 1/3] arm: dra76: fastboot: extend cpu type for getvar command
'commit dda0bd674481 ("arm: dra762: Add support for device package
identification")'
introduces ABZ and ACD package identification.
This patch is to extend usage of "fastboot getvar cpu" for
DRA76x ABZ and ACD devices.
Helps in fixing the boot warning.
Warning: fastboot.cpu: unknown CPU rev: 123863298
on
CPU : DRA762-GP ES1.0 ABZ package
Model: TI AM5748 IDK
Board: AM574x IDK REV 1.0A
Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
arch/arm/mach-omap2/utils.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/mach-omap2/utils.c b/arch/arm/mach-omap2/utils.c
index 1d39625..391055e 100644
--- a/arch/arm/mach-omap2/utils.c
+++ b/arch/arm/mach-omap2/utils.c
@@ -30,6 +30,8 @@ static void omap_set_fastboot_cpu(void)
switch (cpu_rev) {
case DRA762_ES1_0:
+ case DRA762_ABZ_ES1_0:
+ case DRA762_ACD_ES1_0:
cpu = "DRA762";
break;
case DRA752_ES1_0:
--
1.9.1
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
[U-Boot] [PATCH] dra7x: fastboot: Increase recovery partition size
As per current android recommendation
https://source.android.com/devices/architecture/kernel/modular-kernels
1. Android recovery mode should contain both SOC and ODM
kernel modules in the recovery partition.
2. If a kernel module is required both in recovery and normal boot
mode, the module has to be located in recovery and vendor
partition seperately.
3. Kernel modules used in recovery mode should be independent
of vendor and odm partition
4. Recovery image should contain atleast
storage, display, keypad, battery and pmic modules.
Due to these requirements, recovery image size has increased
to >10MB.
This patch is to increase recovery partition size for TI devices
so that we dont see such flashing error
log:
sending 'recovery' (12560 KB)...
OKAY [ 0.436s]
writing 'recovery'...
FAILED (remote: too large for partition)
finished. total time: 0.458s
Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
include/configs/am57xx_evm.h | 2 +-
include/configs/dra7xx_evm.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/configs/am57xx_evm.h b/include/configs/am57xx_evm.h
index ebb0474..dc05bea 100644
--- a/include/configs/am57xx_evm.h
+++ b/include/configs/am57xx_evm.h
@@ -56,7 +56,7 @@
"name=reserved,size=256K,uuid=${uuid_gpt_reserved};" \
"name=efs,size=16M,uuid=${uuid_gpt_efs};" \
"name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
- "name=recovery,size=10M,uuid=${uuid_gpt_recovery};" \
+ "name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
"name=boot,size=10M,uuid=${uuid_gpt_boot};" \
"name=system,size=768M,uuid=${uuid_gpt_system};" \
"name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
diff --git a/include/configs/dra7xx_evm.h b/include/configs/dra7xx_evm.h
index 34a4555..f84c1f0 100644
--- a/include/configs/dra7xx_evm.h
+++ b/include/configs/dra7xx_evm.h
@@ -63,7 +63,7 @@
"name=reserved,size=256K,uuid=${uuid_gpt_reserved};" \
"name=efs,size=16M,uuid=${uuid_gpt_efs};" \
"name=crypto,size=16K,uuid=${uuid_gpt_crypto};" \
- "name=recovery,size=10M,uuid=${uuid_gpt_recovery};" \
+ "name=recovery,size=40M,uuid=${uuid_gpt_recovery};" \
"name=boot,size=10M,uuid=${uuid_gpt_boot};" \
"name=system,size=768M,uuid=${uuid_gpt_system};" \
"name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
--
1.9.1
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
[U-Boot] [PATCH 2/4] arm: dra7xx: Add vendor partition to Android GPT table for eMMC
From: Vishal Mahaveer <vish...@ti.com>
Add vendor partition to Android GPT table for eMMC.
A Vendor image contains SoC-specific code and configuration.
Prior to Android 8.0, the vendor partition was optional ;
files belonging to these images were placed in boot.img or system.img
with symlinks (such as /vendor >/system/vendor ) when absent.
Android 8.0 makes the vendor partition mandatory
The goal is to modularize Android partitions with standard interface between
the Android Platform (on system.img ) and vendor-provided code(on vendor.img).
This standard interface enables the Android Platform to be updated
without affecting the SoC partitions. This makes it possible to upgrade a
device system.img from Android 8.0 to Android P while other images (such as
vendor.img) remain at Android 8.0. This modularity enables timely
Android platform upgrades (such as monthly security updates )
without requiring SoC/ODM partners to update SoC- and device-specific code.
Signed-off-by: Vishal Mahaveer <vish...@ti.com>
Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
include/configs/dra7xx_evm.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/configs/dra7xx_evm.h b/include/configs/dra7xx_evm.h
index 717861f..e5e 100644
--- a/include/configs/dra7xx_evm.h
+++ b/include/configs/dra7xx_evm.h
@@ -66,6 +66,7 @@
"name=recovery,size=10M,uuid=${uuid_gpt_recovery};" \
"name=boot,size=10M,uuid=${uuid_gpt_boot};" \
"name=system,size=768M,uuid=${uuid_gpt_system};" \
+ "name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
"name=cache,size=256M,uuid=${uuid_gpt_cache};" \
"name=ipu1,size=1M,uuid=${uuid_gpt_ipu1};" \
"name=ipu2,size=1M,uuid=${uuid_gpt_ipu2};" \
--
1.9.1
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
[U-Boot] [PATCH 3/4] omap-common: fastboot: extend cpu type for DRA71x rev 2.1
From: Vishal Mahaveer <vish...@ti.com> DRA71x processors are reduced pin and software compatible derivative of DRA72 processors. Extend support for this revision in "getvar cpu" command. Signed-off-by: Vishal Mahaveer <vish...@ti.com> [prane...@ti.com: rebase to u-boot master] Signed-off-by: Praneeth Bajjuri <prane...@ti.com> --- arch/arm/mach-omap2/utils.c | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/mach-omap2/utils.c b/arch/arm/mach-omap2/utils.c index d4f171b..2bd8290 100644 --- a/arch/arm/mach-omap2/utils.c +++ b/arch/arm/mach-omap2/utils.c @@ -33,6 +33,7 @@ static void omap_set_fastboot_cpu(void) break; case DRA722_ES1_0: case DRA722_ES2_0: + case DRA722_ES2_1: cpu = "DRA722"; break; default: -- 1.9.1 ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
[U-Boot] [PATCH 4/4] arm: dra76: fastboot: extend cpu type for getvar command
'commit fa24eca1f20a ("omap: Add routine for setting fastboot variables")'
adds initial support and usage of "fastboot getvar" command
for DRA75x and DRA72x devices.
and
'commit 0f9e6aee9dbc ("arm: dra76: Add support for ES1.0 detection")'
adds initial dra76 device definition
This patch is to extend usage of "fastboot getvar" for DRA76 device.
Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
arch/arm/mach-omap2/utils.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-omap2/utils.c b/arch/arm/mach-omap2/utils.c
index 2bd8290..2e87780 100644
--- a/arch/arm/mach-omap2/utils.c
+++ b/arch/arm/mach-omap2/utils.c
@@ -26,6 +26,9 @@ static void omap_set_fastboot_cpu(void)
u32 cpu_rev = omap_revision();
switch (cpu_rev) {
+ case DRA762_ES1_0:
+ cpu = "DRA762";
+ break;
case DRA752_ES1_0:
case DRA752_ES1_1:
case DRA752_ES2_0:
--
1.9.1
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
[U-Boot] [PATCH 1/4] arm: am57xx: Add vendor partition to Android GPT table for eMMC
Add vendor partition to Android GPT table for eMMC.
A Vendor image contains SoC-specific code and configuration.
Prior to Android 8.0, the vendor partition was optional ;
files belonging to these images were placed in boot.img or system.img
with symlinks (such as /vendor >/system/vendor ) when absent.
Android 8.0 makes the vendor partition mandatory
The goal is to modularize Android partitions with standard interface between
the Android Platform (on system.img ) and vendor-provided code(on vendor.img).
This standard interface enables the Android Platform to be updated
without affecting the SoC partitions. This makes it possible to upgrade a
device system.img from Android 8.0 to Android P while other images (such as
vendor.img) remain at Android 8.0. This modularity enables timely
Android platform upgrades (such as monthly security updates )
without requiring SoC/ODM partners to update SoC- and device-specific code.
Signed-off-by: Praneeth Bajjuri <prane...@ti.com>
---
include/configs/am57xx_evm.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/configs/am57xx_evm.h b/include/configs/am57xx_evm.h
index 5427974..ebb0474 100644
--- a/include/configs/am57xx_evm.h
+++ b/include/configs/am57xx_evm.h
@@ -59,6 +59,7 @@
"name=recovery,size=10M,uuid=${uuid_gpt_recovery};" \
"name=boot,size=10M,uuid=${uuid_gpt_boot};" \
"name=system,size=768M,uuid=${uuid_gpt_system};" \
+ "name=vendor,size=256M,uuid=${uuid_gpt_vendor};" \
"name=cache,size=256M,uuid=${uuid_gpt_cache};" \
"name=ipu1,size=1M,uuid=${uuid_gpt_ipu1};" \
"name=ipu2,size=1M,uuid=${uuid_gpt_ipu2};" \
--
1.9.1
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
