Age | Commit message (Collapse) | Author | Files | Lines |
|
Witherspoon is running tight on space, and as our primary hardware CI
machine, we need to keep it going.
The GUI has already been pulled out so the KVM package doesn't make much
sense anyway.
Tested:
- Reduced image size by ~200KB
- Will rely on CI to regression test
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I3e55702da764e4e1ca1673e158c7acf4f74c9bda
|
|
`BBLAYERS_NON_REMOVABLE` is obsolete and no longer required.
As it said by Yocto documentation it can be used by `Hob`
https://www.yoctoproject.org/docs/1.5.2/ref-manual/ref-manual.html#var-BBLAYERS_NON_REMOVABLE
that already removed since Yocto-2.1
https://www.yoctoproject.org/tools-resources/projects/hob
Change-Id: Ibc2d8268a9d837a81e9cf6b0131dba8d0a030a3f
Signed-off-by: Alexander Filippov <a.filippov@yadro.com>
|
|
Modify the machine meta-layer configs to remove the use of the
OBMC_MACHINE_FEATURES indirection and favor the Yocto MACHINE_FEATURES
variable instead.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ifafb79e4e4c010e9476b9547cd4982f5b645060e
|
|
openpower-pnor-code-mgmt: srcrev bump 9c2ef681e3..6fc7fcd6b1
Adriana Kobylak (2):
Add a new pldm feature option
Add support for the host PLDM transport that takes place of hiomap
(mboxd). Add this new feature to p10bmc.
Tested: Verified that tacoma (that doesn't support pldm) and p10bmc
(supports pldm) reached runtime.
Change-Id: I31e8beba5ff8a413b7b7fa7476f5f2403d3781dd
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
bitbake offers a choice of DEB, RPM or IPK packaging. To a degree the
choice is functionally arbitrary for image generation but control over
the package format becomes important if we want to:
1. Include runtime package management functionality in the firmware image
2. Mess about with the packages on the build system
With respect to 1 the IPK format and opkg (an ipk package manager) are
designed for embedded systems[1] - by contrast to RPMs have heavier
dependencies and a greater impact on the size and complexity of the
firmware image.
Regarding 2, the embedded nature and the need for opkg to work without
much fuss leads to a lower configuration barrier by comparison to RPMs.
With ipk it becomes possible to reuse the packages built during image
preparation for core analysis without needing to generate an SDK:
```
$ export LD_LIBRARY_PATH=./tmp/work/x86_64-linux/opkg-native/*/recipe-sysroot-native/usr/lib
$ MY_DEBUG_ROOT=tmp/rootfs-debug
$ ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \
-f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/*/opkg.conf \
-o $MY_DEBUG_ROOT \
update
$ fakeroot ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \
-f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/opkg.conf \
-o $MY_DEBUG_ROOT \
install dbus-sensors dbus-sensors-dbg
$ gdb-multiarch
(gdb) set solib-absolute-prefix .../tmp/rootfs-debug
(gdb) add-auto-load-safe-path .../tmp/rootfs-debug
(gdb) file tmp/rootfs-debug/usr/bin/nvmesensor
(gdb) core-file obmcdump_17_9597/core.nvmesensor.0.aae91b519d0e4e0e8bbe746e3f6cd25f.2779.9594000000
Core was generated by `/usr/bin/nvmesensor'.
Program terminated with signal SIGABRT, Aborted.
pthread_kill.c:45
45 pthread_kill.c: No such file or directory.
(gdb) bt
pthread_kill.c:45
../sysdeps/posix/raise.c:26
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
"xyz.openbmc_project.NVMeSensor", this=0x488f04) at
/usr/include/sdbusplus/bus.hpp:234
../../../../../../workspace/sources/dbus-sensors/src/NVMeSensorMain.cpp:159
(gdb)
```
This approach documented in the Poky Reference Manual:
https://www.yoctoproject.org/docs/1.0/poky-ref-manual/poky-ref-manual.html#platdev-gdb-remotedebug-launch-gdb-inferiorbins
Switch all machines to IPK to align the debugging experience with
upstream's documentation and to facilitate efficient use of packaged
software at runtime.
[1] https://openwrt.org/docs/guide-user/additional-software/opkg
Change-Id: I8ef526add2d7a6790de1b3eb3fb85cd39b864f23
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
With the reshuffle that occurred in 38cfcc393d9e ("meta-aspeed:
u-boot-aspeed-sdk: Use provided signing key by default") we no-longer
need to specify these options in p10bmc.conf
Mistakenly, `SOCSEC_SIGN_ENABLE = "1"` was duplicated later in the file
by 699146128388 ("meta-ibm: p10bmc: Assert that we want the SPL signed
by socsec"). Removing the instance as done in this patch still leaves us
with the positive assertion that we want SPL signing enabled.
Change-Id: Iaa9cbe5b0ba4aaf69bb0fba1eb8f6bc62d085a33
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
We've typically kept these LAYERSERIES_COMPAT to 2 releases: the current
and the upcoming. Remove 'gatesgarth' is it is now 2 releases back.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5e812a94fed1738898af75c0fdee81996a5bbf20
|
|
Configure the SOCSEC_SIGN_* variables to sign the SPL and exploit the
AST2600 hardware root-of-trust.
Note that this doesn't require that secure-boot is enabled on the
system, the SoC will bootstrap just fine with the signature in place
while secure-boot is disabled. Signing the SPL allows us to switch the
systems over to secure-boot at our leisure.
Change-Id: I07b5c4afb7bacc040cbdce6c82a0fb3a57d0f7f8
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Update with the latest version from upstream.
Change-Id: I1a7da37b0457dab873afaf6445aca360d54b47ca
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
As for Rainier and Everest, use KCS2 as the debug-trigger interface.
Change-Id: I2614ffc3d97164658f2ad4fbb916cbf44be152e1
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
OpenBMC requires additional capabilities for the
OpenPOWER systems such as
- A common mechanism to access and control the host
hardware from the BMC.
- A storage mechanism to store the data that can be
used for initialize, control and access the CEC
hardware.
- An infrastructure to initialize the hardware using
the hardware procedures provided by the hardware team.
- Common mechanism to handle the hardware failures for
the host hardware.
These above features are essential for the BMC to provide
better RAS capability and to support lab debug for the
enterprise class systems.
The phal(POWER Hardware Abstraction Layer) aims to provide
a common layout such that the OpenPOWER application can
use this infrastructure to boot, enable RAS features like dump,
diagnostics, and lab debug tooling purpose.
The phal is a combination of open source packages that are
tailored/customised to use in OpenBMC. For instance POWER
hardware access and control is managed through pdbg and
host hardware data modelling is done via devicetree.
phal is group of libraries running in BMC. These libraries
are used by OpenPOWER specific application for host hardware
interactions, Hostboot and SBE initialization, diagnostics
and debugging.
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I187d9582598743871279a1e407451f4cf4f72668
|
|
Change-Id: Ic1cde1cd67fa6f8f68df80a1f327ace64a39d72b
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
This is apparently not actually working anymore and is removed in the
next poky update.
Change-Id: Ia1c6a258d124a4a30a14fc42e8e0bba95e64faeb
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
The rainier machine has been replaced with the generic p10bmc.
Change-Id: Ia7b6e8b6ad569d6f607d4a38318704fb402f2a1f
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Use the 'insecure/imprint' development key to sign the p10bmc SPL. The
key can be overriden for a production key if necessary.
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: I6e4abecb5859fb59c6185a097cf88bdcb958e207
|
|
Use the insecure key provided by commit '748d586bc1 meta-aspeed: Add
development key for Kernel sign' to sign both the Kernel as well as
U-Boot fitImages. This is used for U-Boot FIT Signature Verification
using a known key, fit for development purposes. For production
purposes, a secure private key must be used.
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: If0c39f4aa17e6eaa5f6952a90283457f252a64d3
|
|
This creates a new DISTRO_FEATURE "ibm-service-account-policy" which
- Adds an admin account which cannot SSH to the BMC's command shell.
- Adds a service account which can SSH and has passwordless sudo access.
This feature is applied to witherspoon-tacoma and p10bmc (rainier).
Tested:
The image behaves as before when the distro feature is not configured.
When the distro feature is configured:
The root user has the same access as before.
The admin user:
- Is not allowed to access the BMC's command shell.
- Console login gets: This account is currently not available.
- SSH login gets: Permission denied, please try again.
- Redfish and REST API access works with role=Administrator.
The service user:
- Console login to the BMC's command shell works. The home
directory is /. Passwordless sudo works.
- SSH login works and using sudo from a SSH session works.
- Redfish and REST API access works with role=Administrator.
Change-Id: Icac5ba7f4fa663047709ab55007bbcfec8158f5e
Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net>
|
|
The OBMC_ORG_YAML_SUBDIRS variable is intended to be set system-wide
and not via bbappends. There was an existing 'ibm-distrovars.inc'
that was unused. Rename it as appropriate, add it to the machines,
and remove the bbappend files.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Id5acd359f41c17ec9e68d1f0717e2f5c1bf96dcf
|
|
The meta-ibm layer supported two different DISTROs depending on the
machine being built. This caused complexity since the user needed to
remember to specify the DISTRO name, in addition to the CI build scripts
needed to check for the machine name being built to override the default
DISTRO.
For simplification, remove the openbmc-witherspoon DISTRO, which is the
openpower DISTRO plus additional features, and move these features to
the machine configuration files. Make the openpower DISTRO the default.
Tested: Built witherspoon and p10bmc using "source setup <machine> build"
followed by "bitbake obmc-phosphor-image" without specifying the
DISTRO. Verified witherspoon built a ubi image and p10bmc built
a emmc image.
Change-Id: If33441ab4ad2dc0fbedde09f0db91d691d2da4f7
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Replace rainier with p10bmc as build target. Keep the rainier.conf as a
symlink to p10bmc.conf to allow the transition. Remove the rainier.conf
and the machine override from p10bmc.conf in a later commit to complete
the replacement.
Tested: Built rainier and p10bmc and checked for some files/service
units to exist on both.
Change-Id: Ic8c8c6ffbc3507fbd9c692da259e37ae695359a6
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier system is being replaced with the generic p10bmc name.
Since the rainier.conf file will be renamed p10bmc.conf, add the device
tree files for all p10 systems that will be supported with the p10bmc
name (rainier, everest).
Change-Id: I10983b913d8a2ae98ed4d327131b864f2df96a0c
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Latest upstream yocto has moved on to the 3.3 hardknott release
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ieae36798d66d21c2c642931f06407d3bb2acf163
|
|
The IBMC POWER10 systems will have a common BMC image, therefore there
will be a transition to move from the 'rainier' system name to the
generic 'p10bmc' name.
This will be done in two stages. The first one is to create a p10bmc
MACHINEOVERRIDES and replace the rainier conditionals with p10bmc.
Once that's done, the rainier.conf will be replaced with p10bmc.conf.
Change-Id: Ic499d36dd7f74a8b7f4a44723f76d1e344e15a32
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
This layer provides libseccomp.
Signed-off-by: Anton D. Kachalov <gmouse@google.com>
Change-Id: I84513d56f2ed75fab49043196b98ef8b858e394f
|
|
This is the configuration that CI builds.
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: Ib9b2ccc554f7ca2c602cec57a300416105791412
|
|
This distro feature is not used anywhere. Remove it to reduce
the clutter.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I1dd4e5ae52197a377b552a8a0e7d1e6d7e7ebe7f
|
|
Both rainier and witherspoon-tacoma systems support the mpreboot
feature.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ieeb4724a5cf5678ba0f6ab950b5403db5aebcd88
|
|
The memory preserving reboot is a feature utilized on IBM systems which
allows a system to be rebooted with its memory preserved. This is
utilized in situations where the host firmware has crashed and put the
processor in an unusable state. The processors are put back in a good
state by rebooting the system. Memory is preserved though so host
firmware can capture the relevant data from memory needed to debug the
cause of the failure.
This feature is implemented across a few different repositories within
OpenBMC so lets create a distro feature to enable it across all of the
software stacks.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ia16626ba6e46aa8de642abef677735ed957f9f9e
|
|
There are some machines (Witherspoon-Tacoma and Rainier) that
have a TPM device, which will be used eventually. We need
access to the recipes in this layer.
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: I3b10ee4d39a69e651a790ae3238e39c45e21ce72
|
|
(From meta-ibm rev: c203fa3d1ca3de7d61b3c06a22dbf4385202cc78)
Change-Id: Iab1adeab9ff493e05e26f31f72c9cb708f28e73e
Signed-off-by: Rashmica Gupta <rashmica.g@gmail.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The AST2600 systems booted from NOR during bringup, but now that we have
eMMC support in u-boot they can run from eMMC.
(From meta-ibm rev: 46419c51c3bd3d43873ecbab7fbbb6f1d6c54de4)
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: Idd2389ab62e1b7cc32639f5547f1f1098631654f
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The next release of Yocto is soon and most of the upstream
layers have switched support strings for it. Support layer
compat for gatesgarth (current) and dunsfell (previous).
(From meta-ibm rev: 00e954d3100bb932d154273376620b40d6b8cad3)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iffd47517e7b9e85597fe97478375a48d0c2db927
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
As we add support for a new series, remove support for the oldest.
Little to no testing is done with older ones.
(From meta-ibm rev: 6255d23fd68023fdc838d0a2262b43883b86be58)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Id63754bdc8ec82628cad23427bfdadafca380c15
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
At a high level, the purpose of this feature was to utilize the BMC
hardware watchdogs to switch the BMC boot flash when certain errors were
hit which were preventing the BMC from booting.
At a high level, this worked but some critical issues were found with
this:
- No failure data is gathered to understand why the boot flash was
switched
- No event or error is logged to notify the user of the system that the
boot flash has switched
- At times, switching sides didn't help because the BMC network
information was not properly copied to the other boot flash which
caused even more confusion for the user
Give the above, this patch proposes a reset on this logic until we can
come back and address the above issues and get this working end to end.
(From meta-ibm rev: d5069cffe865ea104915d8e0fdbe8d7d145644fc)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8c8d2b30c80940f4674e6c6848bd22f759e943a5
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
phosphor-dbus-interfaces recipe requires that we add to the
OBMC_ORG_YAML_DIRS, the directory paths where the interface
YAMLs reside. On IBM systems, we need com/ibm to be addded
to that list.
Tested: Built Witherspoon and Rainier images cleanly.
(From meta-ibm rev: 6f4a08414c5dcea760f75a402cc90a48b833a0aa)
Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com>
Change-Id: Ife7de39ff10a6ead641ccfe82c31481f5135a0f5
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
witherspoon-tacoma systems do not utilize this feature
(From meta-ibm rev: b32849212c59c6383543ba769b8b4f6e2fbbc48b)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I59c5b19b6ad140447f5cdf4184db5acf251c2842
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
rainier systems do not utilize this feature
(From meta-ibm rev: dcfa1a4d7ad4065d983e3bf77cc88d5167492e9d)
Change-Id: I0a9b430c8245016237c0f168781ecf0b68438f96
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Build the u-boot and the SPL binary. The image_types_phosphor.bbclass
keys off these configs to concatenate them together into a single
file which is used during code update to update the device where
the SPL+U-Boot reside.
(From meta-ibm rev: 2e8a6ac2986dfbfc62139355cf663ec5161cb1b9)
Change-Id: Ia17635ef68c059bfa6fd937ac806c3f21fad8c84
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Prior to this patch the Rainier system doesn't include any host
processor configuration. Rainier is a server with a host processor, so
include the correct host processor configuration.
(From meta-ibm rev: 5b44384b92419673b1ce7cca40c5dc613cc6d60a)
Change-Id: I3da77be772c3cd0f89539c8e56c5d0719ad84c44
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
For tacoma, adjusting the size of the eMMC image by making the
hostfw partition smaller.
(From meta-ibm rev: f12da2705f487a933cbf291c129d3832b91d1816)
Change-Id: Ic13d141d41ab513f2af7bff790efc7529739b11d
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This system will no longer be supported or maintained. Drop to minimize
cruft.
(From meta-ibm rev: 7c17e6a1f826cdfbbb39ffa3f237025e56fab52f)
Change-Id: Id954a1c91c754a1eb4eb67348c5fb01a115326ed
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-ibm rev: dcb69381073974467c462609a4c0ebaba19f6b7f)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8dfa84af12606fbb8d6b6874d6642b89d55dc6cd
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-ibm rev: 34c7a88436d2e425429b7a61065e25ce4a9b0664)
Change-Id: I9d4259e36c7c7225e5f29041e204f7d75dc15720
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This was a P9 DD1 workaround. These systems are no longer supported and
are not found in the wild, so the workaround has been retired.
All of the p9 systems in the tree exclude the package so this change
should be a noop.
(From meta-ibm rev: 38c5c9539fb3f01fc2b96d483701938bffdf48a0)
Change-Id: I1c7786526dee4d9bb0d5db916890c1cbe3d51577
Signed-off-by: Joel Stanley <joel@jms.id.au>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The metadata common to all IBM systems is confusingly split between
meta-ibm and meta-witherspoon. Move everything to meta-ibm.
The meta-ibm README is re-written to more accurately reflect the scope
of the layer.
Allow the configuration samples (bblayers.conf.sample,
local.conf.sample) to be sourced from either meta-ibm or
meta-witherspoon until such a time that any workflows and tooling have
had the opportunity to move to meta-ibm.
(From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442)
Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-ibm rev: 9508c70494a7d0ae3bd8f2a2fe662407ae642ad5)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ib03ada135194b8dffdd3982a98ff08bbbc131995
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
OE-core master will be dropping warrior soon; zeus is the next release.
(From meta-ibm rev: 9c8d1b961e1185ab2e7eabf6f6b42754fcb57db0)
Change-Id: I791f06ddb596584d1a566657a38ad6eb13692521
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
IBMBASE is only used for pointing at licenses...point at the
licenses in oe-core in meta/files/common-licenses instead. to match the
defacto convention used in other oe layers like meta-openembedded.
(From meta-ibm rev: cbbb0e5b4e44d831fce5daafd13272d401440f40)
Change-Id: Ib214f92b2c384e3eb2a1f53ecf4b21034438d001
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-ibm rev: 32cabcf8a5f70946d80f51ac41917987f6118031)
Change-Id: Iad810a7a9606a2aee1982337508d1be24cff79f8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|