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 change is an adaptation of commit 81e8a52e8e40e47 from poky/master.
Linux kernel build dependencies include bison since v4.16.
There were two different commits in poky adding those dependencies:
- poky/master: 81e8a52e8e40e47
- poky/sumo: 20e4d309e12bf10
However just adding bison-native to DEPENDS in linux or linux-yocto
class (as in poky/sumo) appears to be insufficient. The reason has
been clarified in 81e8a52e8e40e47 commit message:
"For linux-yocto, we also need to specify the compiler/tools dependencies
for the configme task since it executes before configure and hence the
main kernel build DEPENDS will not always be in the sysroot before it
executes. Without those dependencies the kernel will be incorrectly
configured (i.e. bison is missing) or the configuration will fail
the mitigation tests."
Layer meta-sunxi is compatible with multiple Yocto releases. Some of
those releases have been developed and tested with earlier kernels.
So they may not include new bison kernel build dependencies. That
is why it makes sense to specify new kernel build dependencies
explicitely in meta-sunxi kernel recipes rather than rely upon
upper layers.
Signed-off-by: Sergey Matyukevich <geomatsi@gmail.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>
Currently, only one of the exposed USB ports works because we haven't
loaded the sunxi musb driver, which enables the OTG port to act in host
mode.
After enabling this driver in the config, both ports work correctly.
Signed-off-by: Martin Kelly <mkelly@xevo.com>
Bump Linux kernel version to 4.15.
Notes:
- orange-pi-zero-plus2: drop patch fixing sdcard detect
-- this fix is already in 4.15
- H2+/H3 SoCs: in 4.15 ethernet works right out of the box
Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
This fixes an important brcmfmac use-after-free error:
brcmfmac: change driver unbind order of the sdio function devices
commit 5c3de777bdaf48bd0cfb43097c0d0fb85056cab7 upstream.
commit 01b43f2e3cad60c626daa9b174667a202cee6987 in linux-4.14.y
Without this change, I notice this error regularly when loading the wifi
firmware on the nanopi neo air.
Signed-off-by: Martin Kelly <mkelly@xevo.com>
The kernel-devicetree class now sets RDEPENDS_${KERNEL_PACKAGE_NAME}-base so we
needs to do the same, otherwise bitbake emits a warning. Reference change is
6c8c899 commit in oe-core.
Signed-off-by: Diego Rondini <diego.rondini@kynetics.com>
Currently, using kernel config fragments is not working. If you try
adding one as documented in the Yocto Mega Manual [1], it will be
ignored.
There are two reasons for this:
- The config fragment logic is in kernel-yocto.bbclass, so we need to inherit
that (this is similar to what linux-raspberrypi does in meta-raspberrypi).
- We remove ${B}/.config, which undoes any config created by
kernel-yocto.
Fix this by inheriting kernel-yocto and not removing ${B}/.config. With
this patch, fragments are working. Note that we also need to add a few
variables (like KERNEL_KBUILD) to make kernel-yocto happy.
[1]
http://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html#creating-the-append-file
Signed-off-by: Martin Kelly <mkelly@xevo.com>
