| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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>
|
|
This distro feature is not used anywhere. Remove it to reduce
the clutter.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I1dd4e5ae52197a377b552a8a0e7d1e6d7e7ebe7f
|
|
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
|
|
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>
|
|
(From meta-ibm rev: dcb69381073974467c462609a4c0ebaba19f6b7f)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8dfa84af12606fbb8d6b6874d6642b89d55dc6cd
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>
|
