dany/meta-sunxi
1
0
Fork 0
mirror of https://github.com/linux-sunxi/meta-sunxi.git synced 2024-11-08 06:18:22 +01:00
Code Issues Packages Projects Releases Wiki Activity
df468d72d7
meta-sunxi/conf/machine/include/sunxi.inc

35 lines
968 B
PHP
Raw Normal View History

Use SOC_FAMILY to avoid the long list of COMPATIBLE_MACHINE It uses 3 different SOC_FAMILY sun4i,sun5i,sun7i this list come from here http://sunxi.org/Allwinner_SoC_Family Adding a new machine should be now more easy, as we have now to only create a new machine.conf file, set the right SOC_FAMILY and include the right arch inclue.
2015-06-16 00:20:39 +02:00
SOC_FAMILY ??= ""
include conf/machine/include/soc-family.inc
# Sub-architecture support
MACHINE_SOCARCH_SUFFIX ?= ""
MACHINE_SOCARCH_SUFFIX_sun4i = "-sun4i"
Factorise sunxi machines definition
2013-11-15 18:56:26 +01:00
PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg"
XSERVER = "xserver-xorg \
xf86-video-fbturbo \
xf86-input-evdev \
xf86-input-mouse \
xf86-input-keyboard"
linux: update kernel recipes - 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>
2017-12-03 19:57:31 +01:00
PREFERRED_PROVIDER_virtual/kernel ?= "linux-mainline"
Remove unused PREFFERED_VERSIONS and let the virtual/kernel preffered provider be overriden.
2015-07-18 16:44:20 +02:00
PREFERRED_PROVIDER_u-boot ?= "u-boot"
PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"
Factorise sunxi machines definition
2013-11-15 18:56:26 +01:00
Use SOC_FAMILY to avoid the long list of COMPATIBLE_MACHINE It uses 3 different SOC_FAMILY sun4i,sun5i,sun7i this list come from here http://sunxi.org/Allwinner_SoC_Family Adding a new machine should be now more easy, as we have now to only create a new machine.conf file, set the right SOC_FAMILY and include the right arch inclue.
2015-06-16 00:20:39 +02:00
KERNEL_IMAGETYPE ?= "uImage"
Factorise sunxi machines definition
2013-11-15 18:56:26 +01:00
IMAGE_CLASSES += "sdcard_image-sunxi"
removed unneeded definition in sunxi.inc
2014-01-12 06:47:57 +01:00
IMAGE_FSTYPES += "ext3 tar.gz sunxi-sdimg"
Install all modules built in images
2014-02-11 19:32:53 +01:00
MACHINE_EXTRA_RRECOMMENDS = "kernel-modules"
Append the shortened git revision to the u-boot version This add the first 7 characters of the git sha-1 to the compiled in u-boot version. With this change the serial console displays the following version information: U-Boot 2014.04-gee425f9 (Oct 01 2014 - 22:20:35) Allwinner Technology Without the version looks like this: U-Boot 2014.04 (Oct 01 2014 - 21:55:57) Allwinner Technology Signed-off-by: Christian Ege <k4230r6@gmail.com>
2014-10-01 22:42:20 +02:00
Use SOC_FAMILY to avoid the long list of COMPATIBLE_MACHINE It uses 3 different SOC_FAMILY sun4i,sun5i,sun7i this list come from here http://sunxi.org/Allwinner_SoC_Family Adding a new machine should be now more easy, as we have now to only create a new machine.conf file, set the right SOC_FAMILY and include the right arch inclue.
2015-06-16 00:20:39 +02:00
UBOOT_LOCALVERSION = "-g${@d.getVar('SRCPV', True).partition('+')[2][0:7]}"
UBOOT_ENTRYPOINT ?= "0x40008000"
UBOOT_LOADADDRESS ?= "0x400080OB00"
u-boot: enable support for sun50i 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>
2017-12-03 20:24:12 +01:00
SPL_BINARY ?= "u-boot-sunxi-with-spl.bin"
Use SOC_FAMILY to avoid the long list of COMPATIBLE_MACHINE It uses 3 different SOC_FAMILY sun4i,sun5i,sun7i this list come from here http://sunxi.org/Allwinner_SoC_Family Adding a new machine should be now more easy, as we have now to only create a new machine.conf file, set the right SOC_FAMILY and include the right arch inclue.
2015-06-16 00:20:39 +02:00
SERIAL_CONSOLE ?= "115200 ttyS0"
MACHINE_FEATURES ?= "alsa apm keyboard rtc serial screen usbgadget usbhost vfat"
Reference in New Issue Copy Permalink