| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The obmc-system-mgmt feature is currently used in the image to trigger
inclusion of a virtual-provider which provides a number of packages many
systems need. Partially revert the removal of this feature so that
the outcome is:
1. The empty obmc-phosphor-sysd package is still removed.
2. By default the 'obmc-system-mgmt' feature is included, unless
specifically exempted.
3. All EVB platforms remove the 'obmc-system-mgmt' feature since
they have no system they are managing.
This partially reverts commit 060ad3ff7fcc30aff78a9e504efee9d8fa0d4526.
Tested:
* Built `bletchley` and confirmed `packagegroup-fb-apps-system` and
`entity-manager` are present.
```
entity-manager armv7ahf-vfpv4d16 0.1+git0+6bf41588ab-r0
packagegroup-fb-apps-system all 1.0-r1
```
* Built `witherspoon` and confirmed `packagegroup-op-apps-system` and
`pdbg` are present.
```
packagegroup-op-apps-system noarch 1.0
pdbg arm1176jzs 3.3
```
* Ran `bitbake -p` on `evb-ast2600` to confirm the undefined
`virtual-obmc-system-mgmt` is not being included in the image.
Change-Id: I8b7804d5101cc84a2c57473b3f85672bf7767c67
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Every machine layer treats 'system-management' as either part of a
package-group or removes the feature. The sample implementation in
meta-phosphor is a do-nothing shell script (and up until recently was a
Python script). There appears to be no useful purpose to this feature
as a stand-alone concept, so remove it.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20ca1fa8ff3cb01cac2d07d4ded84e0769e4514b
|
|
Clean up the final part of this indirect, which is the append of the
variable to the MACHINE_FEATURES one.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I2077d7acff5602b7bf333677f5866d979bdaa07c
|
|
The ast2500 shares the RGMII1 pin and the hw strap pins
for SPI interface mode selection ( pin[12:13] ).
In some systems, the RGMII/NCSI interface will use the pin.
It makes the SPI interface mode setting is not correct.
This patch adds a distro feature to enable the SPI master
mode by default.
Signed-off-by: Chanh Nguyen <chanh@os.amperecomputing.com>
Change-Id: I93e5dd5e86870601169974aa1aab4b5480a45ef1
|
|
Commit aff0243 added seccomp to the systemd PACKAGECONFIG. The
libseccomp recipe requires seccomp be a DISTRO_FEATURE.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Iee1d5e9b2efe8284454c0b5125d9de7b43c1bdb0
|
|
The meta-security layer requires the DISTRO_FEATURE 'security' set
otherwise it gives a warning:
WARNING: You have included the meta-security layer, but 'security'
has not been enabled in your DISTRO_FEATURES. Some bbappend files
and preferred version setting may not take effect. See the
meta-security README for details on enabling security support.
This DISTRO_FEATURE doesn't really seem to do anything except enable
an additional include file in the linux-yocto recipe (which itself
then checks other features). It seems entirely safe for us to enable
this feature everywhere to avoid the warning.
$ git grep -A4 "DISTRO_FEATURES" | grep "'security'"
meta-security/README:to have 'security' in DISTRO_FEATURES to have effect.
meta-security/README: 'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files
meta-security/classes/sanity-meta-security.bbclass: if 'security' not in e.data.getVar('DISTRO_FEATURES').split() and not skip_check:
meta-security/classes/sanity-meta-security.bbclass:'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files \
meta-security/recipes-kernel/linux/linux-yocto_5.%.bbappend:require ${@bb.utils.contains('DISTRO_FEATURES', 'security', '${BPN}_security.inc', '', d)}
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ife1549783b356f87f429466f260f34b9a41d002c
|
|
We want to build OpenBMC on ppc64le, so add it to QEMU_TARGETS.
Signed-off-by: Anton Blanchard <anton@ozlabs.org>
Change-Id: Ice8735a105f40c938dde42061d2e33ddf55a07dc
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
|
|
Background:
OpenBMC provisions the BMC firmware image with the root account password
in a form which is no longer acceptable to Linux-PAM version 1.5.1.
Specifically, [phosphor-defaults.inc][] sets the password hash into
/etc/shadow as "\$1\$UGMqyqdG\$FZiylVFmRRfl9Z0Ue8G7e/", where $1
indicates the deprecated [MD5 hash algorithm][]. Ref: [wikipedia passwd
entry][]. Beginning around PAM version 1.5.1, when you log in, the
[pam_unix.so module][] authenticates okay but requires the password to
be changed. (For example, you'll get a message like "You are required
to change your password immediately (administrator enforced)." This
behavior is undesirable for OpenBMC project defaults, and is not
tolerated by the project's current continuous integration tools.)
This change is to replace the password hash to keep the same cleartext
password but hashed with an acceptable algorithm.
Specifically, the password hash supplied in phosphor-defaults.inc is
updated to use the same password as before but encoded
with the SHA-512 algorithm. The hash was generated by the
`openssl passwd -6 0penBmc` command. This change ought to be
transparent and forward and backward compatible.
Note various meta-layers use this same hash string in
conf/local.conf.sample files. They are changed to match.
References:
[phosphor-defaults.inc]: https://github.com/openbmc/openbmc/blob/1a977b269ed437bebb9ae7810e3157746ec9174d/meta-phosphor/conf/distro/include/phosphor-defa
ults.inc#L245
[wikipedia passwd entry]: https://en.wikipedia.org/wiki/Passwd
[pam_unix.so module]: https://github.com/linux-pam/linux-pam/tree/master/modules/pam_unix
[MD5 hash algorithm]: https://en.wikipedia.org/wiki/MD5
Tested:
Created image with new password hash and PAM 1.5.1 and checked that
login works okay and does not require the passwod to be changed.
Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net>
Change-Id: I5b189374f08ba506dbed7f8b9b991f2808cc3bc5
|
|
Background: The OpenBmc project default root account password is set
in meta-phosphor/conf/distro/include/phosphor-defaults.inc and can be
customized in each layer's local.conf file.
Many of these local.conf.sample files had redundant code to set the
password, which probably should not have been there. Removing them
allows the defaults in phosphor-defaults.inc to take effect.
Tested: No. Only meta-ibm was tested.
Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net>
Change-Id: I76dce00d269d7afa005d7bcfd63f846d3cf45596
|
|
Improved practice to use DISTRO_VERSION instead of the undocumented
VERSION_ID.
DISTRO_VERSION is documented in yocto
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html
and specified in this section about creating your own distribution.
https://docs.yoctoproject.org/dev-manual/common-tasks.html#creating-your-own-distribution
VERSION_ID is undocumented and will more likely be changed compared
to the documented DISTRO_VERSION.
The VERSION_ID is set to DISTRO_VERSION in poky/.../os-release.bb
Use weak default to DISTRO_VERSION instead of overriding VERSION_ID.
This allows other layers to override in *.bbappend or *.conf.
Tested:
```
root@romulus:~# cat /etc/os-release
ID=openbmc-openpower
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="2.11.0-dev"
VERSION_ID=2.11.0-dev-165-g20885c497
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 2.11.0-dev"
BUILD_ID="2.11.0-dev"
OPENBMC_TARGET_MACHINE="romulus"
```
Signed-off-by: Willy Tu <wltu@google.com>
Change-Id: I25b5a165b764e6562fa8008c9d2a75a82fb09139
|
|
Build QEMU only for relevant targets to speed up compilation process.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I67c86d6c8fdd2b4969c35c98bec9d5d2342bbef6
|
|
We want to benefit from the space savings of being able to link time
optimize all of our binaries built through meson.
Change-Id: If36f9e76a27bfa8d00210492c2397a174e09dbd3
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
Add new QEMU targets 'riscv32' and 'riscv64' to be able to
use runqemu script on these architectures.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Ib4019e57a0167203fb42c2214a806709a923209a
|
|
DynamicUsers flag in systemd service configuration file required to create,
handle and recycle temporary users.
This is essential module for upcoming daemons' privilege separation work.
Reference: https://github.com/openbmc/openbmc/issues/3383
Signed-off-by: Anton D. Kachalov <gmouse@google.com>
Change-Id: Iabd709c4a20f754fc6ea505e640b2d361aba0be2
|
|
phosphor-led-manager has 3 packages
- phosphor-led-manager : Default
- phosphor-led-manager-ledmanager : Packages phosphor-ledmanager
- phosphor-ledmanager-faultmonitor : Packages phosphor-fru-fault-monitor
Because of this, it was not possible to install files via Makefile and
that always needed a corresponding update to FILES_{PN}-ledmanager.
Removing phosphor-led-manager-ledmanager will eliminate this problem.
Change-Id: I00ca4c34346a47f887872464b9050a46d8f5e8e9
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
The feature was implemented as an append to the kernel (BSP) layers in
meta-phsophor. This created a three way dance between machine layers,
BSP and meta-phosphor, when it should have been the kernel layer
providing this feature and machines could then opt in.
Fixing this means we could remove the KERNEL_DANGLING_FEATURES_WARN_ONLY
workaround.
As the feature is simply turning on a pair of kernel options without any
other impact, we can implement it by adding the options to our
defconfigs. In fact, aspeed and hpe kernel configurations enable the two
kernel options:
$ git grep CONFIG_KEYBOARD_GPIO=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_KEYBOARD_GPIO=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_KEYBOARD_GPIO=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_KEYBOARD_GPIO=y
meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_KEYBOARD_GPIO=y
$ git grep CONFIG_INPUT_EVDEV
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_INPUT_EVDEV=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_INPUT_EVDEV=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_INPUT_EVDEV=y
meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_INPUT_EVDEV=y
Other machines that wish to enable this feature should ensure it is
added to their BSP's defconfig, or add it to their machine specific
defconfig.
Change-Id: I0726836319022f96c1d13d4a0cbd73708047302c
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
This distro feature is not used anywhere. Remove it to reduce
the clutter.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I1dd4e5ae52197a377b552a8a0e7d1e6d7e7ebe7f
|
|
Yocto has a built-in class for applying compiler security flags to
builds. Some security concious projects within OpenBMC set these flags
manually. We should do this project wide, given that it has a
negligible performance impact, and brings us in line with modern
security requirements.
There are some whitepapers on the specifics of what these flags do,
which is a much better documentation than I am able to write here, but
the key takeaways are that this:
1. Enables position independent code.
2. Enables FORTIFY_SOURCE level 2.
3. Enables -wformat and -wformat-security
4. Enables strong stack protection.
None of these flags should have any change in functional behavior.
Section 4.3 of this doc goes through this file in more detail:
https://www.nccgroup.com/globalassets/our-research/us/whitepapers/2018/improving-embedded-linux-security-yocto3.pdf
croserver/eCMD doesn't currently compile with these flags, so it's
explicitly excluded for the moment. Patchset has been merged against
eCMD master to fix this, but we're so far behind, the bump doesn't build
obmc-libobmc-intf has an error that I can't quite understand yet about
unused results, which shouldn't have been effected by this, yet it seems
to be related to enabling the security hardening, so it is also excluded
from the security flags for the moment.
libpldm includes an IBM OEM command that relies on undefined behavior with
open() the proposed fix is here, but libpldm is excluded until that is
merged and bumped.
https://gerrit.openbmc-project.xyz/c/openbmc/pldm/+/3998412
Even with those three exceptions, getting a majority of the security flags
enabled on a majority of the repos should be an overall win.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I0483b1dbe1123a7beff8c5788363685487fb9c09
|
|
Upstream yocto removed these parameters in this commit:
d707fa30f8a24d1e50831846330757254f245791
packagegroup-core-device-devel: remove
https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=d707fa30f8a24d1e50831846330757254f245791
and now builds against a qemu machine fail to build. This commit
removes phosphors use of these items, as it isn't clear what they were
doing for us anyway, which the aformentioned commit also asserts.
(From meta-phosphor rev: 933b75141f46cefe838f298f793f7d49c9f1f2b3)
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I2c9ab4ade1ac1926094da9102ac2c047baa147e0
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add a fru-device package, packagegroup, and image feature.
Remove the ipmi-fru distro feature, since adding it in the first place
was a mistake - no projects have conditional ipmi-fru feature flags.
(From meta-phosphor rev: 4525a9d01a5f65438342a894f27c82f0dd61642c)
Change-Id: I6928ac67d4acb4568359a308b45cb0734d116054
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The ldap and libc-inet-anl DISTRO_FEATURES aren't used anywhere, so
don't set them.
(From meta-phosphor rev: 23140b75afb741ebcd9190efd825b7ef81576e29)
Change-Id: Iba881c25d572397b69b134174336f88b936bddd9
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
152695448 removed our openbmc-phosphor distro override. This had
minimal or no impact because distro overrides based on the DISTRO aren't
being used as they should. Add a distro override so they can be used
where appropriate (e.g. oe-core bbappends).
(From meta-phosphor rev: 1b9a74965ae664726e82ff7941b2d046392fb0f3)
Change-Id: I7ae07ac26c2ea4882d3b1b002b340f53d885c1e8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Create a distro feature for building images for a mmc chip. This
distro feature would allow to add/remove packages that only apply
to mmc.
(From meta-phosphor rev: 3633bca4309f6aa0417aa86e74f8b39e4d750528)
Change-Id: Icf5c39d7f66fd662dc02479263b67ef674b4b232
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Some packages have directory trees of YAML files arranged based on
canonical organization names. See
phosphor-logging-yaml-providers.bbclass as an example.
Add a variable that can be appended to by a layer to limit the number
of 'bbappends' that are necessary in a layer to add their
layer-specific organizations to all the YAML processing recipes.
(From meta-phosphor rev: 2f31e7a7a37f841c1b2586e92258a7759b36306f)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ie4754ba96a4542ce813869a1384b44ab88000be0
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
We do not use pygobject any more and the PREFERRED_VERSION does
not even exist (python2-based).
(From meta-phosphor rev: 6d6e2b31f98363c39b9b94cd1bdfb518e7669382)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8856b0900a1cdb6140b741c3a9639099f1154102
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
DISTRO_FEATURES_LIBC was removed from upstream poky in 2.7 (see
ref-manual/migration.xml), and we use to get ipv4 and ipv6 picked
up as DISTRO_FEATURES as a side-effect of this variable. It was
reported that ipv6 tools were missing from the image, so add this
back directly as a DISTRO_FEATURE.
Also, sort DISTRO_FEATURES_DEFAULT and remove any reference to the
now-deprecated DISTRO_FEATURES_LIBC.
(From meta-phosphor rev: 4877428408c6b2937c6e75d1cdb32f12ad975acf)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ic0d75deccf57147734849c3800b8b316a60971d0
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-phosphor rev: 26202e3e79ec092a6af7311b962d81b0576da926)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ib4fcc31b4d43807cb3b24cf131deca6744ed63d7
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This file originally was not written to be included. Once it was moved
to an include, should have removed the DISTRO override. The gsj system
recently moved to a custom distro that includes this file. Need to
ensure DISTRO is not overridden.
(From meta-phosphor rev: 15269544861c755661981d99711c120fce5410cd)
Change-Id: Iab75967dcaddf0d86b47d4339d82cce43197e73a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add an ipmi-fru distro feature. The ipmi-fru distro feature selects
support for the IPMI FRU format.
Initially this will be used by the entity-manager recipe to select the
fru-device meson option provided by that project for building the
fru-device application - an ipmi fru format parsing application with
dbus support.
(From meta-phosphor rev: 5a1fc9e6c9701eebd98c1ac94032206b3879aca1)
Change-Id: I86b8c5d2625b8ea856946e5e4de055bb14f8ffa7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Remove VIRTUAL-RUNTIME_obmc-settings-mgmt. phosphor-settings-manager is
the de-facto standard for settings management in OpenBMC.
This is a minor improvement to ease of consumption and
comprehensibility. If a popular alternative to
phosphor-settings-manager emerges, revisit the need for this abstraction
then. For un-popular alternatives, bitbake still provides the means for
doing this entirely in downstream layers.
(From meta-phosphor rev: a71cf481ef2f836c839542818e03eda058bc5ef9)
Change-Id: Id563e252c14627e5842c9353e0631901be876326
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
meta-virtualization was dropped from Phosphor OpenBMC awhile back.
There isn't any reason to continue setting this variable.
(From meta-phosphor rev: 5388be3ff1475f9214ff4372acbe6a2f1831bb4d)
Change-Id: I62dc934e07983623e924b657d7373714b42c9fa4
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
There isn't any recipe metadata with any conditional logic around this
distro feature. Remove, for a small improvement to comprehensibility.
(From meta-phosphor rev: b670a101cd22746227ca3fd7ef8615f04aa97fd4)
Change-Id: Ie893015545db146512ef4cb216d94e80e8ac5050
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Remove the obmc-phosphor-user-mgmt distro feature.
It doesn't have any references in any upstream metadata.
(From meta-phosphor rev: 123e391db9b2e23082dc087ae524b2624c6b13c1)
Change-Id: I37fad05647629af78236cd9fea0d1fd4b2faa7dc
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Uninative support was completely removed with commit
70e685ef45a926064d27a2937d6274832c7608b4 but this is a useful
feature on systems that support it (specifically x86_64) because
it enables sstate sharing across various distribution types.
Add in the minimal support for uninative but do not enable it.
This allows someone to optionally enable it by adding the
following to a conf/local.conf:
INHERIT += "uninative"
(From meta-phosphor rev: ea487839ed8566a43e8f9087fba850b1702f9534)
Change-Id: Ifb5ef4aee5886da676f0748c72646a1e8b775658
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
root user account is enabled with proper privilege and group,
only if debug-tweaks or allow-root-login FEATURES is defined.
Note: This will not remove root user getting managed from
phosphor-user-manager, instead it will make sure, the privilege
and groups are empty for the root user.
Tested:
1. Verified the default build, which has debug-tweaks, allowing
root user to be with priv-admin, and enabled for all groups.
2. Verified by removing debug-tweaks from the local.conf, and
root user privilege & groups are empty.
(From meta-phosphor rev: b1b8251f4e5f19189057cdeb998cf119be1c27b8)
Change-Id: Iec2a0b1a9f84c27dd4947125903ce43f3a9c3c2c
Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Other include files may set DISTRO_FEATURES prior to including this
file. Need to honor those features.
(From meta-phosphor rev: 17801b40a7143c6b80dd4318c94143e47ef1ead3)
Change-Id: I42593e07d67416d2dbb06f3958861ed4ebe762ff
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Right now, nuvoton overrides needed for generating and applying the
bootblock are not applied to images other than obmc-phosphor-image. This
means that core-image-minimal is unbootable on nuvoton platforms.
This change makes the nuvoton overrides apply globally to all images.
(From meta-phosphor rev: 9819cb9533f430797d47dadff558cf4462670976)
Change-Id: If4bef5f8106278fa6ebeb2198bc43fdd2b70a641
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
All of our images should remove these features as they are unnecessary
and impractical to run on any of our boards. Leaving these enabled for
core-image-minimal made booting take ~60s in userspace and it filled up
the rwfs on my machines. There doesn't seem to be any benefit to
providing these with any of our images currently.
(From meta-phosphor rev: 563b83bf8de93017e16ca46d3013333ee840818c)
Change-Id: Id2d29d27ffba3659b15ce73714b308362d862ec3
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
All of our images use systemd for booting, so we should deploy
dbus-broker everywhere.
(From meta-phosphor rev: f8196005aefa15dd249ff72036f717b629c8bd4e)
Change-Id: I3010e367a79d782db31050979f5f1bdd30944a11
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add a distro feature to enable aspeed nic driver to enable MAC1
and MAC2.
The aspeednic patch is copied from meta-ingrasys/meta-zaius, it is
also required by fp5280g2. To avoid duplication, this distro feature
has been added.
Both meta-fp5280g2 and meta-zaius will be updated to use the distro feature.
Tested: tested on fp5280g2, and both Ethernet ports worked
(From meta-phosphor rev: 5a8e7c5a6efea492b82d710c465125fc9d0afdb9)
Signed-off-by: John Wang <wangzqbj@inspur.com>
Change-Id: Ia754595c5e3762f69397c03021ffe29ea5b9afcc
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The existing scheme for selecting an entity configuration YAML for
building ipmid consists of a virtual (phosphor-ipmi-entity-config) with
the preferred provider set to a default recipe
(phosphor-ipmi-entity-inventory-native) in the Phosphor distro
configuration.
Instead, provide a reasonable default directly in the ipmid metadata.
This is a small step towards enabling ipmid to build without any distro
configuration and should lower the effort required (slightly) to
comprehend where the the entity YAML file is coming from.
There aren't any known clients overriding the entity YAML in the first
place, but a client could still override with an ipmid bbappend and
setting EXTRA_OECONF appropriately.
(From meta-phosphor rev: fe88ee4211c93f4ca4acba5ecec502aef17944ce)
Change-Id: Ie152c413ee6674735b6bf3192b01ec0bc5a39a29
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
All OpenBMC BSP layers have moved to target class config recipes. As
such, support for native class config recipes can be removed.
(From meta-phosphor rev: f3b437c327b94df6f22c7d821f25d76f1d1c2180)
Change-Id: I7729f7e34529a220af36b88017cb48a3ee887acb
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
There exists a number native class recipes throughout meta-phosphor that
simply provide a data (often YAML) file as input to building another
application.
Having these data file recipes implemented as native class recipes
prevents the use of machine overrides because bitbake (rightfully so)
discards machine qualifiers from native recipes. Further, data files
aren't really any different than library header files and those are
consumed by recipes as target class recipes that are DEPENDed on. Do
the same thing for data file recipes.
A number of steps (patches) are required to ensure backward
compatibility while other BSP layers make the transition to target class
recipes.
This patch is the first step in the sequence. Each native class recipe
is duplicated with (approximately) the following transformation applied:
1 - remove "inherit native"
2 - add "inherit allarch"
3 - Add appropriate files to FILES_${PN}
Also fixed a couple idiosyncrasies like SRC_URI += and LIC_FILES_CHKSUM
that are not required.
Finally, add a temporary layer of indirection around STAGING_DIR_NATIVE
and STAGING_DIR_HOST to the fan metadata until other BSP layers have
fully transitioned to target class config recipes.
(From meta-phosphor rev: 19ee51f5cdce2ff2f076a3ca9263dabc79072ba9)
Change-Id: I9671cc5343ed29a7ccfcee4cc00ebaaa9327e359
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The kernel version string by yocto by default is <tag>-<revision>, e.g.
5.0.7-b1b37a25644213428f4bab4c427581dd923e35da
Where the revision is the version specified by SRCREV, no matter if
there are additional pathces applied or not.
This commit improves it by
* If there are no yocto patches, keep the current version but use a
shorter revision, e.g. 5.0.7-b1b37a2
* If there are yocto patches, append -dirty-<new-short-revision> to the
version string, e.g. 5.0.7-b1b37a2-dirty-84fa553
Resolves openbmc/openbmc#1289
Tested: Verify the kernel version string is changed as above depending
on if there are yocto patches.
(From meta-phosphor rev: fcfd10d7380309bc274c4f5a8355ecaeb60ce439)
Change-Id: I4210227a981721a6b322d640984ea58c57802cb1
Signed-off-by: Lei YU <mine260309@gmail.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Allow another distro building from OpenBMC to specify their own default
virtual/obmc-system-mgmt to allow the meta-ingrasys/meta-openpower
distro-feature virtual/obmc-system-mgmt to set within a system providing
a different default.
(From meta-phosphor rev: 9af5e6419f1cbd9d6ea130812dccb347e4e76e53)
Tested: Zaius image built with correct openpower overrides. Other
platforms built with expected value.
Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: Ieee9d0b3cab9831bfe7201635bb1d79873f79e1c
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This application doesn't have any in-tree users. As such, drop the
recipe and its dependencies.
(From meta-phosphor rev: 296cc521f5a1c8c87c63a5b475b23c876241bf22)
Change-Id: Ie0ce809f84a133c023f96b4727550690583cb9df
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Point various meta-phosphor recipes to depend on phosphor-network
instead of network. Also, update the default for this feature to be
phosphor-network instead of network.
(From meta-phosphor rev: 98fa96164889d0eed896a731bcfb348d5d802bef)
Tested: Verified meta-ibm/meta-witherspoon built.
Change-Id: I1c4b8fdcb92bf216e50d9f88273a7ac7bdc20213
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
phosphor-host-ipmid no longer does anything with the information
specified by the ipmi-channel-config, therefore drop it.
(From meta-phosphor rev: 14e259d7b53de1bae200ee5c5dbf201ffd105543)
Change-Id: I74057fd68ba7e46e5cf5850eaf6434cb6bb37ec9
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
To provide a custom entity configuration, provide
a virtual phosphor-ipmi-entity-config. The entity.yaml file contains
metadata information for the SDR type 0x08h (Entity Association Record)
(From meta-phosphor rev: 47f26214a916246eeb52a9c2f4045e6375fa0bfe)
Change-Id: I812d5805edd547c2780604119bd6ae3f969d9886
Signed-off-by: Jaghathiswari Rankappagounder Natarajan <jaghu@google.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
