Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
Latest upstream yocto has moved on to the 3.3 hardknott release
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ieae36798d66d21c2c642931f06407d3bb2acf163
|
|
This layer provides libseccomp.
Signed-off-by: Anton D. Kachalov <gmouse@google.com>
Change-Id: I84513d56f2ed75fab49043196b98ef8b858e394f
|
|
Most openpower machines use DISTRO="openbmc-openpower" but
Romulus has a "openbmc-romulus" distro config file. This
config file has nothing except an inclusion of the openpower
one, so remove this useless indirection.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I371ce4137369e4964eed1529f8a8190e31721ecc
|
|
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 dunfell (previous).
(From meta-ibm rev: 284e2ad06544f567582b2732a22e052190b5b95a)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ic1cb74ebd387715b08feccd8b94bfd0be7d35205
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>
|
|
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>
|
|
(From meta-ibm rev: b2f780f527e156adff88c3c8e05fe87762266db6)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I523e93b55dd1333640ef7e84aa596b5efb06c4ca
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Base hardware enablement support for meta-romulus is provided by
meta-romulus and meta-openpower. meta-ibm adds advanced serviceability
functions for IBM branded products backed by the IBM service structure.
Romulus is a reference platform for ODMs and/or OEMS building POWER9
based systems. End users cannot purchase support contracts for Romulus
systems. As such remove meta-ibm from the build configuration in the
spirit of keeping the reference implementation mini and simplified.
At a functional level this removes the ibm-logging application from
images.
Note that meta-ibm can always be re-integrated by simply adding it to
bblayers.conf
(From meta-ibm rev: c8cb279e0a8e9d941d8a73f04496a81e0efd5501)
Change-Id: Ie657468f2566042c5faad9ae5a7923a2f9222564
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.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>
|
|
A prior patch added a new recipe romulus-yaml-config to provide all the
YAML configuration for Romulus systems. This patch switches the layer
to that recipe by setting EXTRA_OECONF and DEPENDS as appropriate in the
required bbappends.
With this switch, a number of recipes and their provided YAML are now
dead metadata, so remove those.
(From meta-ibm rev: 66ca8269544784908b0abf78715620adf04d69cc)
Change-Id: I02305ec4c431122ae6ab440c5dcb3def509b7ff9
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The ipmi configs were using .bbappends to override the default ones.
There was a change in OpenBMC about overriding variable assignments,
that causes the .bbappends not working anymore due to they are native.
This commit fixes the issue, by adding romulus specific configs to
replace the default ones.
Tested: Verify the ipmi sensor, fru are correct on Romulus.
(From meta-ibm rev: e020d0d8973cb4fa36d382bc9af5c056e8d8e913)
Change-Id: If804ced6d53c8c4433351b982ebcf079cd014f56
Signed-off-by: Lei YU <mine260309@gmail.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
meta-phosphor dropped support for native class config recipes and uses
target class config recipes by default. Drop the reference to
PHOSPHOR_FAN_CONFIG_USE_NATIVE_SYSROOT as it is no longer used in
meta-phosphor.
(From meta-ibm rev: 0bc0301510b3371510a86fa684b72ea4d4100cf1)
Change-Id: I6b59b1429ead70c1e4ac85a1c9d66b3e04197dd5
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
meta-phosphor recently enabled target class config recipes. Those are
preferable to native class config recipes because native recipes cannot
be overridden based on MACHINE, so switch to target class config
recipes.
Switching to target class recipes consists of temporarily setting
PHOSPHOR_FAN_CONFIG_USE_NATIVE_SYSROOT to 0, overriding the phosphor
distro default of 1. After all OpenBMC BSP layers have moved to target
class config recipes PHOSPHOR_FAN_CONFIG_USE_NATIVE_SYSROOT can be
removed from meta-phosphor and any BSP layers.
Any references to -native recipes are replaced with their target class
counterparts.
Any -native bbappends are re-worked to apply to their target class
counterparts.
Finally, use BPN instead of PN when setting FILESEXTRAPATHS, to avoid
unfortunate directory hierarchies if these bbappends are copy/pasted and
then used to bbappend a native recipe. Since this patch moves to target
class recipes, this is a noop; however, this avoids unfortunate
directory hierarchies with native bbappends such as:
meta-base/recipes-foo/bar/baz-native.bb
meta-base/recipes-foo/bar/baz/a-file
meta-append/recipes-foo/bar/baz-native.bbappend
meta-append/recipes-foo/bar/baz-native/b-file
Using "${THISDIR}/${BPN}:" enables a more sensible hierarchy:
meta-base/recipes-foo/bar/baz-native.bb
meta-base/recipes-foo/bar/baz/a-file
meta-append/recipes-foo/bar/baz-native.bbappend
meta-append/recipes-foo/bar/baz/b-file
This behavior occurs because By default FILESPATH is set in base.bbclass
(in OE-Core) to look for files in ${BP}, ${BPN} and files (and a number
of subdirectories of those based on ${FILESOVERRIDES}).
(From meta-ibm rev: 589ee00a5ec7bc97c7d5c079cf66b3dbd3ac2b4f)
Change-Id: I1a593373f1b4bc82c554a9330cdd75f04f21d1d8
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: 8b843642e36fc9d1ac8921a98dd2710dccf1e514)
Change-Id: I5c6102045f5aaa6146dc1902b106063896d073b8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
openpower-occ-control requires a sensor header file generated from
occ_sensor.yaml. By default it uses an example yaml, which does not fit
for Romulus.
Add romulus-occ-control-config-native.bb to use its own
occ_sensor.yaml, so that the package uses the correct config.
Tested: Verify the build uses the correct config generated from
Romulus's occ_sensor.yaml.
(From meta-ibm rev: 54abf3c0be5618333cb37faebc55af48aa2a872b)
Change-Id: Iaa3adf0d20e5b6d080866dd1b19fa3ee7f4d7369
Signed-off-by: Lei YU <mine260309@gmail.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The distro feature phosphor-isolation is added into openbmc-openpower
distro feature and becomes common for all openpower machines.
So remove them from meta-witherspoon and meta-romulus.
This shall be merged after the commit of adding phosphor-isolation in
openbmc-openpower is merged.
Tested: Verify the Romulus build picks phosphor-isolation distro feature
(From meta-ibm rev: 90f4ccb72200c26d13d3bbd70b6eb7cd90c3dff7)
Change-Id: I8e64bee92eaa7c69928399ceedec6f889a713156
Signed-off-by: Lei YU <mine260309@gmail.com>
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-ibm rev: 97893b2c0bf39cfaee58ccfc4f85249f9a1d8abf)
Change-Id: I2e772add384637011a80acf52861b88ac71be98b
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
ibm.inc simply includes openpower.inc. That, and meta-ibm is a distro
policy layer and doesn't enable any specific hardware.
Update machine configurations to include openpower.inc directly. Add a
conf/distro/include/ibm.inc to meta-ibm at a later time when meta-ibm
has distro policy to apply.
(From meta-ibm rev: 3d1be91f99c646b350c02bfe1004a019cd436c13)
Change-Id: I4bf1e9badba105f4ed10c478f7d5473e3f169791
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
With the recent move to bmcweb we don't need meta-webserver anymore.
(From meta-ibm rev: a5231caf14dd78aa451621644bb60069eea17009)
Change-Id: I92f760321d38f99e651e3a6ae4d689f0bfb337ff
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
(From meta-ibm rev: e98ac73825bddbd95a4b931073c4481fe535cff8)
Change-Id: Ifb4a4e48c9767e1fb388e8f07b076cf55e92733d
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
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>
|
|
With meta-phosphor commit fd1f696f99 this is done by the distro
configuration; so, no need to do it in local.conf.
(From meta-ibm rev: 0525b1723095b6c47af7892ca90f328f92270815)
Change-Id: I6fdbf055b24adf768efdd86132faa7f1fffc56f9
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The meta-poky layer is unused. Remove from the layer configuration.
(From meta-ibm rev: 7bafd24c1b15a87e25c5386236527c863908121f)
Change-Id: Ia589ac6a06af433e8af8cb858ec1a91af962768b
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Set the license fields for the machine-readable-workbook.
(From meta-ibm rev: 7fc06531434db3ff03b148f7a8bd1925a094ec94)
Change-Id: I0d494889f62de9804f61b8a97b118482bbe2868b
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Typical upstream layers have a -layer suffix. Rename collections from
foo to foo-layer to match this de-facto standard. Some existing layers
that use this convention include:
openembedded-layer
networking-layer
perl-layer
virtualization-layer
(From meta-ibm rev: 32478afb0f68ba711b816d1dbaecf379c67cc928)
Change-Id: I5c22956cf289263d5cef1e3c1babb2d1f5a10a3d
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The new subtree model brings the subtrees up from the openbmc-machines
layer.
Change-Id: I58a03ae1be374bc79ae1438e65e888375d12d0c0
Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|