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 <vishalm@ti.com> Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Reviewed-by: Tom Rini <trini@konsulko.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: Praneeth Bajjuri <praneeth@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com>
This macro isn't used by anything, and in fact hasn't ever been used according to the Git logs. Signed-off-by: Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi>
Add support for the DHCOM i.MX6 PDK board. This board has: - FEC ethernet - EHCI USB host - 3x SDMMC Signed-off-by: Marek Vasut <marex@denx.de> Cc: Stefano Babic <sbabic@denx.de>
The i.MX7 SOC doesn't include the SATA interface. Signed-off-by: Uri Mashiach <uri.mashiach@compulab.co.il> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
UART pinmux has been changed on the last board revision. Change board pinmux accordingly. Console is on UART7 now, add pinmux, base address and update console string in environment. Signed-off-by: Anatolij Gustschin <agust@denx.de> Reviewed-by: Stefano Babic <sbabic@denx.de>
mx6slevk can run different kernel versions, such as NXP 4.1 or mainline. Currently the rootfs location is passed via mmcblk number and the problem with this approach is that the mmcblk number for the SD card changes depending on the kernel version. In order to avoid such issue, use the UUID method to specify the rootfs location. Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
Latest wandboard hardware revision is revd1, which brings the following new features: - PFUZE100 PMIC - AR8035 Ethernet PHY - Upgrade Wifi/BT chip to BCM4339/BCM43430. The detection mechanism is to probe the PMIC and when it is found, then the revision of the board is revd1. As the detection is done via PMIC, we need to print the board version at a later stage via CONFIG_DISPLAY_BOARDINFO_LATE and also need to disable CONFIG_DISPLAY_BOARDINFO, which is done much earlier. Make the necessary adjustments for the AR8035 PHY to work on revd1. Based on Richard Hu's work from Technexion's U-Boot tree. Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
Add initial support for Compulab cl-som-imx7 SoM. The initial support includes: - MMC - eMMC - SPI flash - I2C - FEC - USB - Serial console Signed-off-by: Ilya Ledvich <ilya@compulab.co.il>