arm: am57xx: Add vendor partition to Android GPT table for eMMC
Subsystems (3)
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.
--- include/configs/am57xx_evm.h | 1 + 1 file changed, 1 insertion(+)
include/configs/am57xx_evm.h +1 -0
@@ -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};" \
Signature · 1 line
1.9.1
PATCH 2/4 arm: dra7xx: Add vendor partition to Android GPT table for eMMC
From: Vishal Mahaveer <[email protected]>
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.
--- include/configs/dra7xx_evm.h | 1 + 1 file changed, 1 insertion(+)
include/configs/dra7xx_evm.h +1 -0
@@ -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};" \
Signature · 1 line
1.9.1
PATCH 2/4 arm: dra7xx: Add vendor partition to Android GPT table for eMMC
Quoted 22 lines · Praneeth Bajjuri
From: Vishal Mahaveer <[email protected]>
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.
Quoted 2 lines
Signed-off-by Vishal Mahaveer <[email protected]>Signed-off-by Praneeth Bajjuri <[email protected]>
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171013/e6768cb8/attachment.sig>
PATCH 2/4 arm: dra7xx: Add vendor partition to Android GPT table for eMMC
In reply to Praneeth BajjuriQuoted 22 lines · Praneeth Bajjuri
From: Vishal Mahaveer <[email protected]>
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.
Quoted 3 lines
Signed-off-by Vishal Mahaveer <[email protected]>Signed-off-by Praneeth Bajjuri <[email protected]>Reviewed-by Tom Rini <[email protected]>
Applied to u-boot/master, thanks!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171016/1a3b0bfb/attachment.sig>
PATCH 3/4 omap-common: fastboot: extend cpu type for DRA71x rev 2.1
In reply to Praneeth BajjuriFrom: Vishal Mahaveer <[email protected]>
DRA71x processors are reduced pin and software compatible derivative of DRA72 processors. Extend support for this revision in "getvar cpu" command.
--- arch/arm/mach-omap2/utils.c | 1 + 1 file changed, 1 insertion(+)
arch/arm/mach-omap2/utils.c +1 -0
@@ -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 :
Signature · 1 line
1.9.1
PATCH 3/4 omap-common: fastboot: extend cpu type for DRA71x rev 2.1
Quoted 9 lines · Praneeth Bajjuri
From: Vishal Mahaveer <[email protected]>
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 <[email protected]>[praneeth at ti.com: rebase to u-boot master]Signed-off-by Praneeth Bajjuri <[email protected]>
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171013/d19e4588/attachment.sig>
PATCH 3/4 omap-common: fastboot: extend cpu type for DRA71x rev 2.1
In reply to Praneeth BajjuriQuoted 10 lines · Praneeth Bajjuri
From: Vishal Mahaveer <[email protected]>
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 <[email protected]>[praneeth at ti.com: rebase to u-boot master]Signed-off-by Praneeth Bajjuri <[email protected]>Reviewed-by Tom Rini <[email protected]>
Applied to u-boot/master, thanks!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171016/246cfcb4/attachment.sig>
PATCH 4/4 arm: dra76: fastboot: extend cpu type for getvar command
In reply to Praneeth Bajjuri'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.
--- arch/arm/mach-omap2/utils.c | 3 +++ 1 file changed, 3 insertions(+)
arch/arm/mach-omap2/utils.c +3 -0
@@ -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 :
Signature · 1 line
1.9.1
PATCH 4/4 arm: dra76: fastboot: extend cpu type for getvar command
Quoted 11 lines · Praneeth Bajjuri
'commit
fa24eca1f20a("omap: Add routine for setting fastboot variables")' adds initial support and usage of "fastboot getvar" command for DRA75x and DRA72x devices.and
'commit0f9e6aee9dbc("arm: dra76: Add support for ES1.0 detection")' adds initial dra76 device definitionThis patch is to extend usage of "fastboot getvar" for DRA76 device.
Signed-off-by Praneeth Bajjuri <[email protected]>
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171013/0a92ff7b/attachment.sig>
PATCH 4/4 arm: dra76: fastboot: extend cpu type for getvar command
In reply to Praneeth BajjuriQuoted 4 lines · Praneeth Bajjuri
'commit
fa24eca1f20a("omap: Add routine for setting fastboot variables")' adds initial support and usage of "fastboot getvar" command for DRA75x and DRA72x devices.
Quoted 8 lines
and
'commit0f9e6aee9dbc("arm: dra76: Add support for ES1.0 detection")' adds initial dra76 device definitionThis patch is to extend usage of "fastboot getvar" for DRA76 device.
Signed-off-by Praneeth Bajjuri <[email protected]>Reviewed-by Tom Rini <[email protected]>
Applied to u-boot/master, thanks!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171016/5487c1c0/attachment.sig>
PATCH 1/4 arm: am57xx: Add vendor partition to Android GPT table for eMMC
In reply to Praneeth BajjuriQuoted 13 lines · Praneeth Bajjuri
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).
Quoted 8 lines
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 <[email protected]>
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171013/c256e14c/attachment.sig>
PATCH 1/4 arm: am57xx: Add vendor partition to Android GPT table for eMMC
In reply to Praneeth BajjuriQuoted 20 lines · Praneeth Bajjuri
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.
Quoted 2 lines
Signed-off-by Praneeth Bajjuri <[email protected]>Reviewed-by Tom Rini <[email protected]>
Applied to u-boot/master, thanks!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171016/51046eb9/attachment.sig>