Update the layer compatibility information to indicate this layer is
compatible with "dunfell".
Signed-off-by: Diego Rondini <diego.rondini@kynetics.com>
Enable open source GPU support for Mali Utgard GPUs (lima driver) and
Mali Midgard and Bifrost GPUs (panfrost driver).
The support is enabled by:
- enabling DRM kernel CONFIGs
- enabling lima, panfrost and kmsro in Mesa
- disabling the specific mali driver overrides in sunxi-mali.inc
To enable open source mainline graphics support just add the following
line in your local.conf:
MACHINEOVERRIDES .= ":use-mailine-graphics"
Please note that some machines may need a bigger CMA value to be able to
start Weston. To do that, add e.g. "cma=128M" to the kernel parameters.
Signed-off-by: Diego Rondini <diego.rondini@kynetics.com>
According to:
https://www.kernel.org/category/releases.html
version 5.4 is a longterm release, so:
- add longterm 5.4 series at 5.4.18
- update longterm 4.19 series to 4.19.103
- update stable to 5.5.3
- remove rc, as it quickly gets out of date. rc users will likely build
kernel from master outside of OE anyway
- set 5.4 as the preferred version for linux-mainline
Signed-off-by: Diego Rondini <diego.rondini@kynetics.com>
Add support for AMPAK 6212A module:
1) install kernel module
2) install firmware
3) create the required symlink with the AP6212 NVRAM file
Enable the support in the boards with the module, according to:
https://linux-sunxi.org/Table_of_Allwinner_based_boards
The link creation with compatible name works on kernels >= 5.0.
Signed-off-by: Diego Rondini <diego.rondini@kynetics.com>
Remove pointless U-Boot PREFERRED_VERSION, as meta-sunxi no longer
provides its own u-boot recipe.
Signed-off-by: Diego Rondini <diego.rondini@kynetics.com>
In the latest OE, this file has been renamed. Since this board is
ARMv8-A, we should use the armv8-a config instead of the armv8 config.
Signed-off-by: Martin Kelly <mkelly@xevo.com>
This has been assigned a value containing a typo since 2015, my
assumption is that this is not used and hence we can simply drop
it. The typo is that the address contains a 'O' character instead
of '0', the last one is a zero.
Either way the kernel.bbclass will set a default value, that is:
UBOOT_LOADADDRESS ?= "${UBOOT_ENTRYPOINT}"
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
v2017.03 no longer exists and produces warnings if set as preferred:
NOTE: Resolving any missing task queue dependencies
NOTE: preferred version v2017.03% of u-boot not available (for item virtual/bootloader)
NOTE: versions of u-boot available: 1:2018.01 2:v2018.03+gitAUTOINC+f95ab1fb6e
NOTE: preferred version v2017.03% of u-boot not available (for item u-boot-dev)
NOTE: versions of u-boot available: 1:2018.01 2:v2018.03+gitAUTOINC+f95ab1fb6e
NOTE: preferred version v2017.03% of u-boot not available (for item u-boot)
NOTE: versions of u-boot available: 1:2018.01 2:v2018.03+gitAUTOINC+f95ab1fb6e
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
In current Yocto master, it's now a warning not to include
LAYERSERIES_COMPAT in layer.conf. See below for more information:
https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-LAYERSERIES_COMPAT
Add this information for all current development and stable releases.
Tested-by: Sergey Matyukevich <geomatsi@gmail.com>
Tested-by: Diego Rondini <diego.rondini@kynetics.com>
Signed-off-by: Martin Kelly <mkelly@xevo.com>
We have devicetree and u-boot configs for the nanopi-neo-air, so add
them. As a basic test, this boots correctly on my nanopi-neo-air.
Signed-off-by: Martin Kelly <mkelly@xevo.com>
Orange Pi Zero Plus2 board is based on AllWinner H5 SoC.
For more details on its hardware see linux-sunxi wiki:
http://linux-sunxi.org/Xunlong_Orange_Pi_Zero_Plus_2
This patch enables basic support for orange-pi-zero-plus2 board:
- mainline kernel 4.14.2
- mainline u-boot 2017.11
- dts kernel patch that fixes boot from SD card
- dts kernel patch enabling AP6212 WiFi/BT chip
Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
Add support of sun50i SoC family to u-boot recipe:
- move SPL_BINARY to sunxi.inc and sunxi64.inc
-- different SoC families have different SPL_BINARY names
- create separate boot.cmd files for arm and aarch64
-- different kernel image types require different boot commands
- add atf-sunxi dependency
-- u-boot for aarch64 needs ATF BL31 binary
- add do_compile_sun50i[depends]
-- make sure that BL31 binary is already deployed before u-boot build
Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
Follow the same approach as in 32-bit sunxi SoC families:
- create sunxi64.inc: umbrella description for aarch64 sunxi
-- specify proper u-boot/spl image types
-- specify proper kernel image type
-- specify u-boot/kernel preferred providers
- create basic description of sun50i SoC family
-- sun50i SoC family is based on armv8
Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
- remove older stable release recipes
- bump stable linux recipe to 4.14.2
- bump git linux recipe to 4.15-rc1
- rename linux to linux-mainline
Renaming kernel recipe from 'linux' to 'linux-mainline' is needed to
get ready for adding aarch64 support. The reason is in the value of
OVERRIDES environment variable. BitBake uses OVERRIDES to control what
variables are overridden after BitBake parses recipes and configuration
files. So packages names are not allowed to take values listed in
OVERRIDES. One of the OVERRIDES values is TARGET_OS:
TARGET_OS = linux${LIBCEXTENSION}${ABIEXTENSION}
For arm architecture TARGET_OS = "linux-gnueabi". However for aarch64
architecture TARGET_OS = "linux". As a result, in the case of aarch64
kernel package can not be named 'linux'. This patch renames kernel
package name to 'linux-mainline' in order to be able to maintain the
same kernel recipes for both arm and aarch64 boards.
Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
