Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
Change Ie1a7c389edb6b7a048836a49283ceb62de51bba5 will be transitioning
the 'Type' property in Inventory.Item.Chassis to an enumeration.
In order to avoid crashing in PIM we need these default values in the
starting YAML to be fully-qualified enumeration names that will match
the values which will start in Ie1a7c.
This code is safe to merge as is without any PDI or PIM changes. Prior
to the PDI change, we must make a change to PIM that allows conversion
automatic from string->enum, leveraging library interfaces available in
sdbusplus. These will be submitted independently.
I checked the codebase for usage of this string. It appears that the
value is currently, effectively, write-only. There is code in bmcweb
that fills in the equivalent Redfish value but currently just hard-codes
the string 'RackMount'.
Tested: Booted Witherspoon in a QEMU model with this change and proposed
changes to sdbusplus + PIM. PIM no longer coredumps with the PDI change
and yields an expected persistence file:
```
$ pwd
/var/lib/phosphor-inventory-manager/xyz/openbmc_project/inventory/system/chassis
$ cat xyz.openbmc_project.Inventory.Item.Chassis
{
"value0": {
"cereal_class_version": 2,
"Type": 3
}
}
```
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Icaf9447f31ccdd945cdf74b3e017682e4aed686f
|
|
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 repository supports it, so switch it over in bitbake.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I8d96c79b395ee2614ddd869091569f245426c5c7
|
|
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>
|
|
Dbus sensor interface 'xyz.openbmc_project.Sensor.Value' migrated
from int to double. Therefore all old 'int64_t' types in
"*-ipmi-sensor*.yaml" files for this interface should be changed to
'double'.
(From meta-ibm rev: c769f790e14b9caa4fc842dc1e2035378de6ae60)
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Id8e164203541550eb19301ca429702cbf7d4b2f8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Similar to commit 567a8d for witherspoon, this issue has now popped
up on Romulus hardware.
The concept of warm reboot (reboot the host without removing chassis
power) was added a while back as a part of clarifying support for
the Redfish ComputerSystem.Reset Action. It has since been found that
some IBM hardware, including Romulus, do not support warm reboots.
The issue is intermittent and depends on the reboot being requested
while the host is in the middle of some i2c transactions. If a warm
reboot occurs during this window, then on the subsequent boot the i2c
hardware will be in a bad state and the host firmware is unable to
recover it.
Given this issue, it has been requested that BMC software go back to
doing cold reboots (cycling power to the chassis during any reboot
request) on this hardware.
(From meta-ibm rev: 718f2b5405c2c1f000cc0ccbf2860a283997c08a)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I31810e89977532d4368050871aba03d78deb9c59
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>
|
|
The yaml add the "xyz.openbmc_project.Inventory.Item.Chassis" interface
to "/xyz/openbmc_project/inventory/system/chassis" object.
This is needed for bmcweb to correctly get the chassis id in
/redfish/v1/Chassis/.
Tested: Verify that /redfish/v1/Chassis/chassis exists on Romulus with
this change. It was 404 without this change.
(From meta-ibm rev: 41b829feead473e5541f7d4c3c075e2b1a525c45)
Signed-off-by: Lei YU <mine260309@gmail.com>
Change-Id: Ie091ad32315fb4b4e45d8b35966a7a238dd1d539
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.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>
|
|
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>
|
|
The cooling-type in phosphor-fan is optional, and Romulus is a
air-cooled system and does not require cooling-type application at all.
Remove the cooling-type app and the related configuration files.
Tested: Verify the generated phosphor-fan related hpp and cpp files are
identical as before, and the system is able to power on and do
fan monitor/control without problem.
(From meta-ibm rev: 3168f5e5fb59bd37eed1600d42a8d6fc02875fea)
Change-Id: I30f47ef63f4ff5bea89f31966273930baaf070ea
Signed-off-by: Lei YU <mine260309@gmail.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
(From meta-ibm rev: 8f7ff601395419a933eb0506d5cc07fd805f7708)
Change-Id: Iffb2c550511b4024b721c2ba81aec1f909ce7703
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
With updated from openbmc/openbmc#2911, event actions are now able to be
configured with group subsets and event timers are now included in the
available event triggers. Actions with group subsets allow a single
event's set of triggers to run actions against a given group subset
instead of the entire event groups. Also, with timers being included as
a trigger, events can be configured with or without a timer instead of a
disabled timer being created for events that previously did not require
a timer.
Tested:
Generated code is functionally equivalent to previous yaml
(From meta-ibm rev: 03eacc4ef87b3b89cf36aab977ff4eab68f8b4fc)
Change-Id: Ib7eadf5b7c2cb27440e5944348460295334b9f13
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This allows upstream to drop some backward-incompatible changes while
the yaml in meta-ibm gets updated to the new format coming in from
upstream.
(From meta-ibm rev: 81ca4572471629b5114a52afb50a84d9e2cc92d1)
Change-Id: Ia554f14c624d236e02d7898d2f95e7a90384dadf
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
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>
|
|
YAML configuration files exist scattered throughout the OpenBMC tree and
how they are used is controlled with layers dependencies of virtuals and
preferred providers.
Most of the time the above scheme is very difficult to comprehend. This
patch continues a re-thinking of that approach towards a more
centralized scheme.
Specifically this patch implements a single YAML config recipe for the
Romulus systems. The logic contained in the recipe was pulled from all
over the OpenBMC tree - the ability to comprehend how the different YAML
files are generated and consumed should be greatly eased.
One notable detail - unlike the upstream recipes, romulus-yaml-config
is a target recipe and as such enables MACHINE based overrides.
YAML files were copied from different locations in the tree, and run
through a styling application (pyyaml dump(load(yaml))):
romulus-ipmi-fru-properties-native:extra-properties.yaml ->
romulus-yaml-config:romulus-ipmi-fru-properties.yaml
romulus-ipmi-fru-read-inventory-native:config.yaml ->
romulus-yaml-config:romulus-ipmi-fru.yaml
romulus-ipmi-fru-read-bmc-inventory-native:bmc-fru-config.yaml ->
romulus-yaml-config:romulus-ipmi-fru-properties.yaml
romulus-ipmi-inventory-sel-native:sel-config.yaml ->
romulus-yaml-config:romulus-ipmi-inventory-sensors.yaml
romulus-ipmi-sensor-inventory-native:config.yaml ->
romulus-yaml-config:romulus-ipmi-sensors.yaml
(From meta-ibm rev: 67b17f7aa658b71908de47aa0b0814530da36259)
Change-Id: I3953274db23f9ccf8cb74d3962e797bf935d61a8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
These files aren't used by ipmid anymore, so drop. See host-ipmid
change 41ac50530a for details.
(From meta-ibm rev: dfd8a072958aa531a41d7fbb190675c66b75e15c)
Change-Id: I3aaab61c24fa0a4167cb04b60e577c1761605887
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The service phosphor-cooling-type is required by multi-user.target and
thus will be started by default. In case multi-user.target is started
for multiple times, this service will be startd for multiple times as
well, and eventually get start-limit-hit failure.
This commit adds RemainAfterExit=true so the service will be treated as
started and thus will not be started for multiple times.
Resolves openbmc/openbmc#3544
Tested: Reboot Romulus BMC when the host is on, and verify the BMC gets
READY state after reboot.
(From meta-ibm rev: fdd8f7bb1cca6b505d6b92c741d04a9c6bbfafa7)
Change-Id: Ie3817296265c860d770333c59b591da9d083139c
Signed-off-by: Lei YU <mine260309@gmail.com>
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>
|
|
Typically it does not make any sense to append to FILESEXTRAPATHS.
FILESEXTRAPATHS is set in a bbappend when overriding something from
another layer. The typical desire will be to make bitbake search for
files in the layer with the bbappend and not some other layer earlier in
the priority list. Further, appending to FILESEXTRAPATHS will introduce
unexpected behavior when multiple layers append the same recipe - layers
with higher layer priorities that append to FILESEXTRAPATHS will find
their files overriden by files in layers with lower priorities.
(From meta-ibm rev: e11f36155c0fc8a6cc4bb6ef5abee777b8ae6b5a)
Change-Id: Idcd839211e009f260a38ae9cb6351154a8074c28
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add overrides to variable assignments as described in "Modify Variables
to Support a Different Machine" in the yocto development tasks manual:
https://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#best-practices-to-follow-when-creating-layers
In a nutshell this allows multiple BSP layers to be included
simultaneously in bblayers.conf, which increases the potential for meta
data sharing between layers.
(From meta-ibm rev: 0ccb228f770fe8688fd926ad822244fab6926298)
Change-Id: I4f648d1c2232a6f246b63b8e46731b7ef1af13ac
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This recipe is only required by the legacy inventory manager, which
is no longer used on Romulus.
(From meta-ibm rev: 952dd07412311c294ad3ad767da97eb2512a781f)
Change-Id: Ide0596e3834d94e1884a470c836bd7717246ec33
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>
|
|
Patrick Venture (1):
build: install into bin instead of sbin
meta-ibm: phosphor-fan: grab cooling-type from bindir
The output binaries from phosphor-fan-presence are now installed into
bin instead of sbin.
Change-Id: I2d42f62b4535775ffd0d1b9473375dd8dc66bb61
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Patrick Venture <venture@google.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>
|
|
Instead of obmc-standby.target, use multi-user.target.
(From meta-ibm rev: 85cff8cc9e66049d8ac26271c13f82d894ac572f)
Change-Id: I03c3d41c031343fa584511889c70e3def92cb83d
Signed-off-by: Patrick Venture <venture@google.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>
|
|
In the 5.0 Linux kernel, an I2C device path segment changed:
i2c@1e78a000 -> bus@1e78a000
(From meta-ibm rev: 3de23010065c681179a508af1cda2daee31f2725)
Tested: Verified paths visually, but not tested on hardware.
Change-Id: Ia5474cf5c0b952cc765582a59868d0138570b2ef
Signed-off-by: Patrick Venture <venture@google.com>
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>
|
|
Update meta-ibm to master HEAD.
Patrick Venture (21):
meta-ibm: add IBMBASE
meta-ibm: romulus: chassis: avsbus-control: set LICENSE field
meta-ibm: romulus: chassis: vrm-control: set LICENSE field
meta-ibm: romulus: gpio: id-button: set LICENSE field
meta-ibm: romulus: ipmi-fru-read-inventory-native: set LICENSE field
meta-ibm: romulus: ipmi-inventory-map-native: set LICENSE field
meta-ibm: romulus: ipmi-inventory-sel-native: set LICENSE field
meta-ibm: romulus: led-manager-config-native: set LICENSE field
meta-ibm: romulus; phosphor-logging-callouts-native: set LICENSE field
meta-ibm: witherspoon: chassis: avsbus-control: set LICENSE field
meta-ibm: witherspoon: chassis: vrm-control: set LICENSE field
meta-ibm: witherspoon: events-policy-native: set LICENSE field
meta-ibm: witherspoon: fan-policy-native: set LICENSE field
meta-ibm: witherspoon: fan-watchdog: set LICENSE field
meta-ibm: witherspoon: thermal-policy-native: set LICENSE field
meta-ibm: witherspoon: inventory-cleanup-native: set LICENSE field
meta-ibm: witherspoon: power-supply-policy-native: set LICENSE field
meta-ibm: witherspoon: power-supply-sync: set LICENSE field
meta-ibm: palmetto: ipmi-inventory-map-native: set LICENSE field
meta-ibm: palmetto: led-manager-config-native: set LICENSE field
meta-ibm: dbus-interfaces-mapper-config-native: set LICENSE field
Change-Id: Ic74e30b1cdd013c7d293dffc9423035632f92e43
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This was a workaround for DD1 (pre-production) hardware.
Jordan Keuseman <jkeusema@us.ibm.com> wrote:
> That was an issue back in DD1 time frame where the VRM needed to
> change their signal voltage thresholds for AVS bus to work around a
> problem where the processor was putting out a runt pulse in the final
> bit of the transaction. They fixed that in the silicon so we got rid
> of the work around.
This was removed from Witherspoon when dropping DD1 support from
OpenBMC. We can remove it from Romulus and other platforms too.
(From meta-ibm rev: baedc91099960c0e582a98e465e190ff9c3aa9cc)
Change-Id: I8266c154505d3b4fb268cd7c44aa84f5a4be0301
Signed-off-by: Joel Stanley <joel@jms.id.au>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Drop symlink and rename bbappend for phosphor-software-manager.
(From meta-ibm rev: b4a0a983ff709f0fb60916e5b7bd11ea60ce0fec)
Change-Id: Ibc07e2011f712a9b5a60416c88c95dd7e72d7f64
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Set the wildcard for version phosphor-software-manager_%.bbappend
(From meta-ibm rev: a9b4b696c565d5a50021452809704ab5aa480516)
Change-Id: Icd4835674be6ddc90ec1412b5d31d9100e3883ce
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|