Age | Commit message (Collapse) | Author | Files | Lines |
|
Since the OpenBMC is it's own distribution, we should not be strictly
dependent upon poky.
Using require poky.conf breaks our ability to update the
variable LOCALCONF_VERSION since it is set to 1 by poky.conf. If we want
to continue getting updates as poky changes, they should be brought over
manually.
Change-Id: I1e098d0e884640f3e0dbb242753656c01f6c1b79
Signed-off-by: David Cobbley <david.j.cobbley@linux.intel.com>
|
|
Typical upstream layers have a -layer suffix. Rename
from obmc-phosphor to phosphor-layer to match this de-facto
standard. Some existing layers that use this convention
include:
openembedded-layer
networking-layer
perl-layer
virtualization-layer
Change-Id: I5df5273b7ef4a0d8742b74a9b1ecd680a8598b04
Tested: Built a palmetto image
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Starting with sumo, bitbake emits a warning if this variable is
not set. Indicate sumo branch compatibility.
Change-Id: I0832841e92aea4e707131221b8992f8999da395a
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Yocto 2.5 will bring us a systemd built with meson, so we will no longer
be able to use EXTRA_OECONF to prevent inclusion of the udev database
in images.
Disable it via BAD_RECOMMENDATIONS in the distro configuration instead.
Tested: Built a witherspoon image
Change-Id: I5eb9239a0f41f65df1823bc4ab6f593a31d2f4ec
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Begin to remove content from this non-sensical file. Any BSP
configuration should be in a BSP layer, not the phosphor layer.
KERNEL_EXTRA_ARGS: should be set by BSP, and this isn't required at
all at the moment by the currently supported BSPs.
UBOOT_SUFFIX: should be set by a BSP or distro configuration.
MACHINEOVERRIDES: this was nonsensical in the bitbake sense - there
is no such thing as an openbmc machine. If there is a need for
an openbmc override in the future it can be added as a distro
override (there is no such need at the moment).
MACHINE_FEATURES_BACKFILL_CONSIDERED: BSPs should be considering
backfilled machine features.
Tested: Built witherspoon and palmetto images
Change-Id: Idf252c92cb718d076ea556f2b389f15c13716fd2
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Move the Aspeed u-boot tree patches to a directory where they can
be conditionally applied when the Aspeed layer is in the build
configuration.
This is a better way to achieve 273ec60e436 since it enables the Aspeed
BSP layer to name its u-boot/kernel recipes whatever it wants.
Remove stubbed do_configure from u-boot_%.bbappend. It is no longer
required since the bbappend is only activated when the aspeed layer
and associated u-boot recipes are in the layer configuration.
Tested: Built u-boot recipe for witherspoon and palmetto targets
Change-Id: I52dceb65598e0cf660ad035a8f14e9894325ca71
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
One use case on some systems for this layer will be to pull
in Nginx
Signed-Off-By: Chris Austen <austenc@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I1ac55bc182e7d24704d0fe3405438d8e1c97f1a4
|
|
Install u-boot-fw-utils via dependency, rather than explicitly
attempting to include it in all images.
Tested: Built witherspoon, qemux86 images
Change-Id: I371cb4b848d67d75816a6d0d3b35bc7615f2ec39
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
For most incremental builds, the critical path is generating a new
installed obmc-phosphor-image fs, then compressing it to put into a
.lzma.u-boot container. However, the latter step doesn't seem necessary
except for the out-of-kernel initrd (obmc-phosphor-initramfs) because
obmc-phosphor-image is packaged as a squashfs-xz and not seen by U-Boot.
qemu.inc has its own IMAGE_FSTYPE appends, so qemuarm builds should not
be affected.
This reduces incremental build time by about a third, when doing
'bitbake obmc-phosphor-image' with no changes.
before:
150.74s user 66.01s system 148% cpu 2:25.96 total
after:
94.78s user 64.87s system 159% cpu 1:39.97 total
This reflects the removal of the single-threaded, CPU-bound 'lzma'
invocation from the critical path.
Netbootable images can still by generated by adding:
IMAGE_FSTYPES += "cpio.${INITRAMFS_CTYPE}.u-boot"
to local.conf.
Signed-off-by: Xo Wang <xow@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I867500589ffe0a36cbe1193843907d7882239227
|
|
We don't need a distro feature for net IPMI at this point, so
simplify things a bit.
Additionally, remove the net-ipmi virtual since we don't have
any alternative implementations today and it just adds unnecessary
complexity.
Tested: Built a witherspoon image and validated manifest
Change-Id: I2784f13b3e8897e855ac128422081ec3ee207bf1
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Remove the phosphor-logging virtuals. They were unused.
Add a logging packagegroup so other layers can add additional
logging applications predicated on the logging distro feature
being enabled.
Change-Id: Ic82843cb2b1229df55005bad93576c14f468073b
Tested: Built witherspoon, palmetto and qemu images
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Drop support for RHEL6 which has been unsupported by Poky
since 2.1.
This reverts commit c83cf1ce570d4771b1e42ded308bf4110e70408b.
Tested: Built a witherspoon image
Change-Id: Idd8dda940c72a69a7a228733c34018f906ec9b8f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
There were a number of places that inherited this class but did not
use it. A number of classes that did use it did not inherit it.
This was possible because the class was pulled in by the distro
configuration but that has been removed here as well.
Tested: Built and verified a witherspoon image
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I73511cdcc609875b4fe016967c1b84c5200fb703
|
|
Consider (this is a Yocto verb) a number of backfilled features:
pulseaudio
bluez5
ldconfig
gobject-introspection-data
Put OpenBMC specific distro features in their own variable
DISTRO_FEATURES_OBMC. This has no functional impact but does
make looking at DISTRO_FEATURES with bitbake -e a little easier
on the eyes.
Change-Id: I78a9e2f0807cac41bc119b04b42f32db5d1b9dbf
Tested: Build and verified witherspoon and palmetto images
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
In the previous review it was noted that it didn't make much sense
for host-check to be it's own provided function in OpenBMC. It's more
of a recommended piece of the base host state function.
Change-Id: I024472e96ea00f411e8348e0221c210f84700019
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
As with MRW the use of the UBI image scheme is distro policy.
Convert the existing machine feature to a distro feature.
Enable the new distro feature on the systems that use
it(Witherspoon).
Add a distro override and fix-up MF checks to use this override
instead for improved readability.
Tested: Built a Witherspoon image and validated image
Change-Id: I8ab03115bbfc2ecc77cff5c9eb8628903ae88051
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Now that obmc-mrw is no longer a machine feature we can organize
a bit and enable MRW providers off to the side with a disto override,
de-cluttering wherever non-MRW defaults are specified.
No functional impact but slightly easier for humans to parse.
Change-Id: If2731206b94e16e0b0132a385756eb11178118f2
Tested: Built a Witherspoon image and validated manifest
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Using MRW or not is distro policy. As such remove the obmc-mrw
machine feature.
Do not enable the remaining obmc-mrw distro feature in the base
phosphor distro configuration.
Create new distro configs for the systems that use MRW today
(i.e. Witherspoon) that enables the obmc-mrw distro feature and point
the local.conf.sample at the new distro configuration.
Change-Id: If4cedc745b3ee942518fbfd4d5cf2cd5b60f346d
Tested: Built a Witherspoon image and validate the manifest
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add MRW distro policy includes to prepare for removing the
obmc-mrw feature from the default distro policy. Custom distros
can enable MRW by including the MRW include(s) from their distro
configuration.
The content is a little light at the moment but it is anticipated
it will grow in subsequent patches.
Tested: No functional changes
Change-Id: I9120662618b45f0b73902edc666c7684b499a40c
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Enable other distro config files to require/include a proper include
rather than directly including openbmc-phosphor.conf
Tested: Built a Witherspoon image
Change-Id: I2e94c9a7f9ecc1527ece86099407cdc4f34a5e36
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This is a minor reorganization by grouping of the
overrides specified in the phosphor-defaults.inc file.
Change-Id: I1634552a286e0f0b04b4c0d3c7c07e4a0aa03c06
Signed-off-by: Patrick Venture <venture@google.com>
|
|
Starting with Rocko the meta-virtualization layer will emit a
warning about missing virtualization in DISTRO_FEATURES.
Silence the warning rather than adding the feature as true
virtualization support is not required on OpenBMC at the
moment.
Tested: Built witherspoon and palmetto images with Rocko
Change-Id: Icd0d4a7fa918770e7f40e57657bf81f854d50acd
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
xyz.openbmc_project.Settings has replaced this function
Resolves openbmc/openbmc#2339
Change-Id: Ifec6a2fda088c4631e3835d3276a54e09b5d7147
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Two un-needed applications are getting installed and started on
UBI enabled systems:
- download_manager.py (obmc-mgr-download.bb)
- bmc_update.py (obmc-flash-bmc.bb)
Remove these if it is a BMC UBI enabled system.
Moved all of the BMC flash logic to the phosphor layer where
it really belongs since the ability to update your OpenBMC
should come by default when bringing in phosphor.
Tested: Verified 2 python applications not present on witherspoon and
system boots and code updates fine. Verified romulus image still had
python applications and made it to Ready states.
Resolves openbmc/openbmc#2480
Change-Id: I42317ece1b75fd6bb05e766e486dfecdb7d4ccf3
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The current dual-use of packagegroup-ipmid-providers as a
dependency insertion point for both native (whitelists) and
runtime (provider libs) doesn't work under Yocto 2.3.
Move the ipmi provider configuration from recipe scope to
the global configuration scope so we can continue to avoid
dually maintaining whitelist and provider lists _and_ build
under Yocto 2.3.
Also rename OBMC_IPMID_PROVIDERS with the more conventional
VIRTUAL-RUNTIME_phosphor-ipmi-providers.
Change-Id: I1acce0b08047cba2312f60542942cccbcff66aec
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
To provide a custom channel configuration, provide
a virtual phosphor-ipmi-channel-config.
Change-Id: I00d8e8aed11a18d193a9066a098611784600da56
Signed-off-by: Patrick Venture <venture@google.com>
|
|
With this patch, the build system supports the tools-profile feature,
We can add it into the EXTRA_IMAGE_FEATURES in conf/local.conf,
to add more debug/profile tools into the image
Change-Id: Ic3c3811d9bca3f99a9e94d7c9da5a71ce1321d02
Signed-off-by: Yong Li <yong.b.li@linux.intel.com>
|
|
Removed the obmc-phosphor-user and put the new one
Also, removed the usage of PREFERRED_PROVIDER and replaced by
VIRTUAL_RUNTIME for this feature
Change-Id: I6f0825f8d51eecb9c666a95d9fd702a8ea8bb08b
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Change-Id: I06f511350e025144a8612c8077427a1d35cdfe10
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Change-Id: Ie064ea9595742b78ccb7fe8a59c923b147ebfff6
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
More refactoring in preparation for ubi based mtd images.
Promote tar file generation to a real image_fstype. This allows tar
generation to be turned on or off as needed.
Move image-overlay function to image_types_phosphor. Perhaps phosphor
is not the best name but for now we only have a handful of image types and
the generation logic is to interdependant to warrant seperate classes
for each.
Attempt to improve readability throughout.
Drop ext4 override to discourage mtd block emulation.
Change-Id: Idbdc03444549b955ef2180622d133904cb191b28
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
phosphor-software-manager-version provides a set of dbus
interfaces that are only useful if there is an 'updater'
package also installed. Rather than explicitly install
phosphor-software-manager-version, have it RPROVIDE a
virtual package and set up RDEPENDS correctly so it is
added to the image whenever an 'updater' package is
installed.
Change-Id: Id6850aca023bb546881fe1583c57d9a24405e25a
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Solve the problem resulting in the addition of this variable
differently, such that it can be removed and image type
selection can be selected in the standard way using IMAGE_FSTYPES.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: Ice94e8f278f00b8b4d344244bfb87dddeb173a23
|
|
Remove the building by default of cpios and squashfs images.
The cpio isn't used at all. Allow the squashfs image to be
build via dependency (overlay).
Change-Id: I03372def60468cdca5a7084e1312e80f405758e7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Removed a handful of unused variables.
Use upstream style conventions, which seem to be:
- pep8 for python
- tabs for shellcode
- 8 space indent everywhere else
Change-Id: I4de549ecf02472096a54234379cd7cce8c219c48
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Replace the fan-presence example recipe with a re-usable
"hardcoded" config recipe.
Change-Id: I47fba19eb9243d123a44e448ebf4322593074e1c
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Change-Id: I03382dbcbd350d7e3a8991633b4548658e4e4b1e
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
|
|
Resolves openbmc/openbmc#1559
Change-Id: I3c663693df78cdf8daac83d49ca35982be27165a
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
|
|
Change-Id: I460e086e1e5d3d5db5405ac29927a7b460f56ff6
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Change-Id: I7f61a48b31d2997c1710c7d0bdde387e5c41a598
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
|
|
The records.events implementation has been replaced with
xyz.openbmc_project.Logging
Closes: openbmc/openbmc#1313
Change-Id: Ie2cc3dc48763301989de63214c37edb601290c91
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Change-Id: I28b3454c0066649b0c163616247f9ca1bbf3abb3
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
|
|
phosphor-gpio-monitor is a generic GPIO monitor application which
can be used for any purpose where a GPIO needs to be monitored for
certain state. Due to this need, it has been added to obmc package
group.
Change-Id: I8e11e8d5567d6f4c56479b335d1f6bd9b39401fd
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Change-Id: I9a5b8977072c30d7c2c8a8402ca5bf627d8b79bd
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
This virtual provides a YAML file that serves as a mapping between
inventory and sensor number for phosphor-ipmi-host. Add a native
recipe that builds the YAML from the MRW. This is the default for
the machines that support obmc-mrw.
Resolves openbmc/openbmc#1514
Change-Id: I3d856ab00c34d3e71926b863f207dd69f7fc8f3f
Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
|
|
Resolves openbmc/openbmc#941
Change-Id: I3e5672af468185f6bae50c438820a10d57d60d55
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
|
|
Change-Id: I2724bcadc0a44c2f2d6c59e8c481e9d7e16e59a9
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Resolves openbmc/openbmc#1503
Change-Id: Id42d8c5042af4a9a74a9a284f3601989a65c5054
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
|
|
This application and services will be used by the host reset service
to determine if the host is running after a BMC has been rebooted
Change-Id: I8299546b0f275ebbb46aa775ab7b0633cc3fd5e0
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
This provides the phosphor-fan-control-fan-config virtual to
define the fans required by phosphor-fan-control.
On systems with the MRW, phosphor-fan-control-fan-config-mrw-native.bb
will be used and will run a perl script to generate the yaml
from data in the MRW XML.
On systems without the MRW, if nothing else is done a default
fans.yaml file will be installed into the correct location
by phosphor-fan-control-fan-config-native.bb. To install a
system specific version, put it into that system's layer along
with a .bbappend of this recipe.
Change-Id: I36889a33e16a456a04b94aba7326dd674bfd2904
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|