| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The u-boot config is a property of the board and not the SOC. Don't set
a default in the g4 and g5 include files. This ensures that BSP users
explicitly select a uboot config capable of booting the board.
(From meta-aspeed rev: 6203fbdba652e2f7943b55b067b2e91247c795e1)
Change-Id: I7b07019eb7428d8c38268e8dbed0ff5d05f3a7a2
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Instead of setting MACHINE_EXTRA_RDEPENDS in each SOC specific include
file, just set it once in aspeed.inc.
Use MACHINE_EXTRA_RRECOMMENDS as the udev rule is definitely not
required and should be removable via BAD_RECOMMENDATIONS.
(From meta-aspeed rev: 672366760cccfe5bf2e734939ec21c90482e298f)
Change-Id: I42091a522b346fe07511e16439438a73d0c9be6c
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Move most settings from the ast2xxx.inc files to aspeed.inc. This seems
to be how other BSPs do it (e.g. meta-freescale) and it keeps everying
in one consolidated location for easy perusal, comparison, etc. bitbake
will take a different path through it's code while parsing but we wind
up with the exact same variable settings in the end.
Remove worthless comments from ast2xxx.inc file headers.
(From meta-aspeed rev: 456a28202671507ca91b35103a13d3a1dac695db)
Change-Id: Id8ed034350761770f5dae4d1a0adecc9bcfea3b5
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Use the correct tune for the g6 arm core: vfpv4d16
(From meta-aspeed rev: 8f80491f1d58fbe94ef1d32aba45789aee549cec)
Change-Id: I06b7b982c9064edd7369e947cc9e41e2e39a50ed
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Provide a default setting for SERIAL_CONSOLES for all Aspeed SOCs.
Set the SERIAL_CONSOLE for the g5 and g6 evb explicitly, in case the
default changes.
(From meta-aspeed rev: b539e873a7731bad9eee83e17838a78f281d7b4b)
Change-Id: I1ee9f44535cd009de25baccacada36cd58ad4f10
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
oe-core has these defaults:
KERNEL_IMAGETYPE: "zimage"
KERNEL_CLASSES: "kernel-uimage"
INITRAMFS_IMAGE: ""
INITRAMFS_FSTYPES: "cpio.gz"
Override those defaults with Aspeed specific defaults that are more
appropriate to the current state of typical usage (FIT) of Aspeed chips:
KERNEL_IMAGETYPE: "fitImage"
KERNEL_CLASSES: "kernel-fitimage"
INITRAMFS_IMAGE: "aspeed-image-initramfs"
INITRAMFS_FSTYPES: "cpio.xz"
By default use aspeed-image-initramfs in the FIT image.
aspeed-image-initramfs is just an alias to core-image-minimal. The
alias is required because vanilla core-image-minimal is not an initramfs
image recipe...in oe, in general, the usage of the image recipe
(initramfs or not) is baked into the recipe itself with a line like:
IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}"
The same behavior *could* be obtained with a bbappend but that then
prevents users from using the original image recipe as a real root
filesystem image in their setups.
Perhaps at a later time a replacement image with an Aspeed hardware
evaluation kit theme would be a more suitable default.
(From meta-aspeed rev: 7639df3650f6d91c9b533e0287142fdcfbc0b2ea)
Change-Id: I51def69bcfd786f4c8aad2ae68376da335aad039
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add base configuration metadata for the Aspeed AST2600 and its
evaluation board.
Initially point at the Aspeed SDK until kernel and u-boot support is
added upstream.
(From meta-aspeed rev: 2f128068bc3b7705071868176624ef19a9000750)
Change-Id: Id8636520815a2cf98f8a801f6a2241387e4a8231
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Leave KMACHINE at the OE-core default. It is only used by the
kernel-yocto bitbake class when dealing with kernel source trees like
the Yocto kernel fork that include KERNEL_FEATURES metadata right in the
source tree. None of the Aspeed trees do that.
Don't set FLASH_SIZE. It isn't an OE-core variable and it isn't used
anywhere.
(From meta-aspeed rev: 798e4360c387b12e6bd190c5e526edc1cd75521d)
Change-Id: I4a68fa98108014b8517d0417357060a8fc4e7aae
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
From the manual on LAYERSERIES_COMPAT:
Lists the versions of the OpenEmbedded-Core for which a layer is
compatible. Using the LAYERSERIES_COMPAT variable allows the layer
maintainer to indicate which combinations of the layer and OE-Core can
be expected to work. The variable gives the system a way to detect when
a layer has not been tested with new releases of OE-Core (e.g. the layer
is not maintained).
Noone is testing OE-core thud + meta-aspeed master, so take the safe
route and don't advertise support. For compatibility with OE-core thud,
use the thud branch of meta-aspeed.
(From meta-aspeed rev: 47d59dc9e3944127b91c89f6745da55eb12bdbfa)
Change-Id: I11dc3c5bd285e2bc9c6b7226b8dda757f3705db7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add a minimal sample local.conf and bblayers.conf to enable easy build
setup:
TEMPLATECONF=meta=aspeed/conf . oe-init-build-env
(From meta-aspeed rev: fdcd3979b7a1beaef7b832ddc74648226008317a)
Change-Id: I6d62b6e7b1ef7e874178ce52979f522e103ab332
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
There currently aren't any usable targets provided with meta-aspeed.
Typical OE BSP layers provide reference metadata for evaluation boards.
Provide one for the AST2500 evaluation board.
Typical BSPs also provide an image class that produces images usable on
the target hardware. meta-aspeed doesn't have one (yet), so although
baking an image (e.g. core-image-minimal) will now work, it will not
produce images usable with actual Aspeed hardware.
(From meta-aspeed rev: 720fcee6f9dc78ed46b4641de6f2fb0054a6da44)
Change-Id: I3419d448b05aa7c72b77224e44050ca63ec20f12
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Bitbake uses this regex to associate recipes and bbappends from BBFILES
(which contains recipes and bbappends from -all- layers listed in
bblayers.conf) to this layer. The association is then used to map the
BBFILE_PRIORITY value for this layer onto the recipes provided by this
layer.
BBFILE_PRIORITY is used to determine which recipe to use when the same
recipe appears in multiple layers.
Without BBFILE_PATTERN set, recipes in this layer will get a default
priority and not the priority specified in BBFILE_PRIORITY.
This layer doesn't set a priority anyway, so functionally this patch is
a noop but it is an improvement from a correctness standpoint, and it
makes a warning go away:
WARNING: No bb files matched BBFILE_PATTERN_foo-layer
(From meta-aspeed rev: 1d2385f66eebac4548d7512b75f26fc641548c02)
Change-Id: Ia4101252ce6dc9ec0ebc920103ef3b5417775c2e
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
OE-Core adds the value of SOC_FAMILY to MACHINEOVERRIDES, so explicitly
setting a MACHINEOVERRIDES is redundant. Drop the explicit
ast2400/ast2500 MACHINEOVERRIDES and use the OE-Core provided aspeed-g4
and aspeed-g5 instead.
After the redundant ast2400/ast2500 overrides are dropped, the ordering
of the values in MACHINEOVERRIDES is wrong:
MACHINEOVERRIDES="aspeed-g5:aspeed"
This means that:
FOO_aspeed = "bar"
will override:
FOO_aspeed-g5 = "baz"
which is the opposite of expectation. The ordering is a function of
config file include order and choice of the predot vs postdot operator.
Use the same include ordering and dot operators as meta-fsl-arm to get
the overrides to appear in MACHINEOVERRIDES in the correct order such
that the expected semantics are provided and:
FOO_aspeed-g5 = "bar"
will override:
FOO_aspeed = "baz"
Drop explicit setting for FILESPATH as OE-Core adds OVERRIDES to
FILESPATH and bitbake will find the appropriate defconfig without them.
Move defconfigs to aspeed-g4 and aspeed-g5 since the ast2400 and ast2500
are being removed.
(From meta-aspeed rev: 85d614a69c1e752fb4d5917499500c37c4f745ac)
Change-Id: I63c0f71f14bf9145e7e769902be87bb267a78a30
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
oe-core branched in preparation for the upcoming 2.7 Yocto release and
as of 13e45ff requires core layer compatibility to "warrior" instead of
"thud". We'll retain compatibility for both until we do our own branch
or stop testing thud.
(From meta-aspeed rev: b0a660fff71d73fd3ebce07fb2092e25cf72d4f4)
Change-Id: I55ff5fc408780ea721a3aa9b7b91144dea4235fa
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
meta-aspeed commit 054541adc3 was not applied correctly. sync up the
subtree with 054541adc3 applied correctly.
Change-Id: I3df6319c6e5f68e2d517db177928c1077dacdb85
Fixes: 1a4b7ee28bf7413af6513fb45ad0d0736048f866
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Reset the following subtrees on thud HEAD:
poky: 87e3a9739d
meta-openembedded: 6094ae18c8
meta-security: 31dc4e7532
meta-raspberrypi: a48743dc36
meta-xilinx: c42016e2e6
Also re-apply backports that didn't make it into thud:
poky:
17726d0 systemd-systemctl-native: handle Install wildcards
meta-openembedded:
4321a5d libtinyxml2: update to 7.0.1
042f0a3 libcereal: Add native and nativesdk classes
e23284f libcereal: Allow empty package
030e8d4 rsyslog: curl-less build with fmhttp PACKAGECONFIG
179a1b9 gtest: update to 1.8.1
Squashed OpenBMC subtree compatibility updates:
meta-aspeed:
Brad Bishop (1):
aspeed: add yocto 2.6 compatibility
meta-ibm:
Brad Bishop (1):
ibm: prepare for yocto 2.6
meta-ingrasys:
Brad Bishop (1):
ingrasys: set layer compatibility to yocto 2.6
meta-openpower:
Brad Bishop (1):
openpower: set layer compatibility to yocto 2.6
meta-phosphor:
Brad Bishop (3):
phosphor: set layer compatibility to thud
phosphor: libgpg-error: drop patches
phosphor: react to fitimage artifact rename
Ed Tanous (4):
Dropbear: upgrade options for latest upgrade
yocto2.6: update openssl options
busybox: remove upstream watchdog patch
systemd: Rebase CONFIG_CGROUP_BPF patch
Change-Id: I7b1fe71cca880d0372a82d94b5fd785323e3a9e7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The new subtree paradigm has moved the meta-bsp layers to the top level
Change-Id: Ic4f64c39465be699bed3649e125e027d17daf938
Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
