| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
|
| |
|
|
| |
Signed-off-by: Cristinel Panfir <cristinel.panfir@nxp.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Drop patch appplied upstream, remove additional install step which is
handled by imx-boot recipe.
Update u-boot dtb names in machine description files, upstream U-Boot
from NXP has DTB files renamed.
Upgrade u-boot-imx-tools and u-boot-imx-mfgtool to 2020.04 as well to
match u-boot-imx recipe.
Signed-off-by: Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>
|
| |
|
|
| |
Signed-off-by: Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>
|
|
|
Splits out the IMX u-boot tools build to it's own recipe. This is
required because these are native tools and thus need to be in a -native
recipe to be properly relocated (instead of being built as part of the
target u-boot-imx recipe). If the tools aren't built in a -native
recipe, then the mkimage tool will contain a hard coded path to the
uninative program loader from the sandbox where it was first built and
this will not get corrected when restored from sstate. The result is
that the mkimage_uboot executable can't run because it's looking for a
hard coded program loader that does not exist, resulting in strange
build errors like:
./mkimage_uboot: Command not found
even though the executable is obviously in the correct location.
Signed-off-by: Joshua Watt <Joshua.Watt@garmin.com>
|
