- based upon NXP imx_5.4.47_2.2.0 branch
- includes changes to allow UART4 access from Cortex-A
- fix lpddr4 cache flush for i.MX8MP
Note that the previous version was wrongly named 2.3 although it was
based upon ATF 2.0.
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
u-boot-qoriq in meta-freescale has upgraded to 2020.04. The patches for
lx2160acex7 can't be applied on 2020.04.
Restore the 2019.10 recipe to avoid build break.
Signed-off-by: Ting Liu <ting.liu@nxp.com>
Set a weak assignment for IMX_DEFAULT_BSP before include the
imx-base.inc to allow override IMX_DEFAULT_BSP in local.conf file.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
Fix /etc/asound.conf and enable sound out of the box with the
default machine configurations for cubox-i and hummingboard.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
LPDDR4 init updates
Android security features enabled
Fixed env import
Enabled HAB for i.MX 8M family
Fixed Nano board support
Fixed build with GCC10
Fixed i.MX 8M Mini ARM PLL choice
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
- Sync defconfig with imx_v7_var_defconfig
- Remove old patches
- Change recipe to use kernel-yocto.bbclass
- KERNEL_IMAGETYPE need to set in machine conf file, drop it
- Move COMPATIBLE_MACHINE to bottom
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
- Update to the latest stable release
- Drop unused patch
- Adjust recipe to build with newer Yocto Project
versions (Gatesgarth and Dunfell)
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
When removing the machine we ended not removing all files. This removes
all the related ones.
Fixes: e50d808 "ccimx6ul*: Drop unbuildable boards"
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Based on NXP imx_5.4.24_2.1.0 release.
Includes latest stable releases, hence 5.4.x naming.
Includes support for all Boundary Devices platforms + accessories.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
Recipe of u-boot-karo has not been maintained for years; more recent
support does not cover the use of updated linux kernel and is not
compatible with dunfell.
Removed u-boot-karo, linux-karo and the machine configurations.
Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
Change-Id: I02645c9f88e648c143b82c4baa89491a1baff934
The board is not building and received no maintenance, so it is being
removed along with linux-timesys that provides support for it.
kernel-module-mcc and libmcc2 were removed as they provided support
for pcm052 only.
Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
Change-Id: I997059c1824484df8c11c9b31b2dae6e989430e7
Solid-Run's official BSP provides linux-patches against linux-qoriq kernel
instead of using linux-fslc branches or an own one with stable updates.
To support comparable conditions with provided BSP, support patches can be
used with NXPs kernel as well as with FSL Community QorIQ kernel.
Signed-off-by: Jens Rehsack <sno@netbsd.org>
With all required components as dependency added:
* rcw
* atf
* mc-utils
* u-boot
* linux
* wic template
... go ahead to enable building for Honeycomb or Clearfog LX2 if you are a
lucky one who could get one :)
Signed-off-by: Jens Rehsack <sno@netbsd.org>
Introduce a script which is able to be used for any QorIQ boot situation
(with some adoption) to favour distro_boot over fallback sd_boot or alike
hacked by NXP.
Signed-off-by: Jens Rehsack <sno@netbsd.org>
Add support for Solid-Runs LX2160A based COM Express Type 7 Module and
machines built upon that module (see
https://www.solid-run.com/nxp-lx2160a-family/).
Signed-off-by: Jens Rehsack <sno@netbsd.org>
Add support for management-console and linux configuration of components
accessible by Solid-Runs LX2160A based COM Express Type 7 Module.
Signed-off-by: Jens Rehsack <sno@netbsd.org>
Add support for platform build upon Solid-Run's new COM Express Type 7
for NXPs LX2160A (https://www.solid-run.com/nxp-lx2160a-family/cex7-lx2160/)
to ARM Trusted Firmware implementation.
Signed-off-by: Jens Rehsack <sno@netbsd.org>
The board are in unbuildable state for long time and they were
removed from U-Boot mainline in 2018 and nobody noticed so it
is clearly not in use.
This commit removes both boards and respective recipes from
the layer.
Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
Change-Id: Ica122e72a0c357bba5924916c30a73d0874fae80
Old recipe had construction error due to virtual / kernel and updated linux 4.9 -> 5.4
Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
Change-Id: I8d37a7766749421b41124ee5147fc3df65358edc
The version of u-boot-variscite does not support target 'u-boot-initial-env'
yet so build fails with:
| make[1]: *** No rule to make target 'u-boot-initial-env'. Stop.
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
It seems building recent u-boot does not require native bc any more. So
while moving on it seems oe-core removed it from u-boot.inc so we need to add
it.
Fixes:
| /bin/sh: bc: command not found
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
The pwm-buzzer, can, emmc and nandflash MACHINE_FEATURES are invalid and
as such should not be on the BSP. Remove them.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Change-Id: I577a9d0887a9520618188b39c0114b319a3d7217
This commit includes the following changes:
- 3d58441adf3 kontron_mx6ul: Use the SPI NOR as primary boot device to load U-Boot proper
- f1db3d8504b kontron_mx6ul: Use 64K offset for U-Boot proper image, in SPI NOR
- e1d78d738c6 kontron_mx6ul: Fix support for SPI NOR boot
- c5e0df84780 kontron_mx6ul: Enable SPI NAND support
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
Fixed the name of WKS_FILES, which was not found and
had an error during the build.
Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
Change-Id: If51edd53b0f992858ad8289aed558f12d914aba0
Even with modifications, errors in the build of the image
persist. Since the board has not received updates in a long
time, it is being removed.
Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br>
Change-Id: I8554a49ca9e34282d11c9613b35de4cb7f0aa181
The imx specific weston version which is otherwise set is not in
COMPATIBLE_MACHINE for Vybrids.
Prevents:
| NOTE: preferred version 8.0.0.imx of weston not available (for item weston)
| NOTE: versions of weston available: 8.0.0
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
linux-imx.inc is using kernel-yocto class and it's necessary to set
LINUX_VERSION as shown in meta-freescale commit
c7e23876b199e2cfbc2aef6bf192ef50e665b1c5
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
