BMC/tmp/openbmc.git/meta-phosphor/classes, branch 2.18.0-dev

styhead: update WORKDIR usage

2024-12-05T21:54:29+00:00

The latest yocto release(styhead,5.1) has made a significant change[1] to the use of the WORKDIR parameter. This is not the complete change required but gets us going in the right direction. [1]: https://docs.yoctoproject.org/next/migration-guides/migration-5.1.html#workdir-changes Signed-off-by: Andrew Geissler Signed-off-by: Patrick Williams Change-Id: I4f184b361be69e7704a0657a4a00cdad981aff8a

skeleton: srcrev bump bba48eafa2..fd84bfa397

2024-11-12T21:30:34+00:00

Jonico Eustaquio (1): Add support for multiple gpio banks Change-Id: Ib935b9cbe0d7a7739b1904a1a357a88bf688d181 Signed-off-by: Andrew Geissler

meta-phosphor: remove obmc-fru-ipmi IMAGE_FEATURE

2024-10-30T11:08:33+00:00

There is currently a lot of complexity of setting up an image feature which is only used to enable the fru-device feature of entity-manager. Simplify this by using RRECOMMENDS, in entity-manager, and eliminating the IMAGE_FEATURE. Tested: Ran `bitbake entity-manager -ne` and observed the following on two affected platforms: In witherspoon: ``` # $PACKAGECONFIG [5 operations] # :remove[pn-entity-manager] openbmc/openbmc/meta-ibm/conf/machine/witherspoon.conf:41 # "ipmi-fru" # set openbmc/openbmc/meta/conf/documentation.conf:321 # [doc] "This variable provides a means of enabling or disabling features of a recipe on a per-recipe basis." # set openbmc/openbmc/meta-phosphor/recipes-phosphor/configuration/entity-manager_git.bb:14 # [_defaultval] "ipmi-fru" # set openbmc/openbmc/meta-phosphor/recipes-phosphor/configuration/entity-manager_git.bb:15 # [ipmi-fru] "-Dfru-device=true, -Dfru-device=false, i2c-tools," # set openbmc/openbmc/meta-phosphor/recipes-phosphor/configuration/entity-manager_git.bb:18 # [validate-json] "-Dvalidate-json=true, -Dvalidate-json=false, ${PYTHON_PN}-jsonschema-native" # pre-expansion value: # "ipmi-fru" PACKAGECONFIG="" ``` In p10bmc: ``` # $PACKAGECONFIG [7 operations] # :append[pn-debug-trigger] openbmc/openbmc/meta-ibm/conf/machine/p10bmc.conf:72 # " triggers" # :remove[pn-entity-manager] openbmc/openbmc/meta-ibm/conf/machine/p10bmc.conf:75 # "ipmi-fru" # set openbmc/openbmc/meta/conf/documentation.conf:321 # [doc] "This variable provides a means of enabling or disabling features of a recipe on a per-recipe basis." # set openbmc/openbmc/meta-phosphor/recipes-phosphor/configuration/entity-manager_git.bb:14 # [_defaultval] "ipmi-fru" # set openbmc/openbmc/meta-phosphor/recipes-phosphor/configuration/entity-manager_git.bb:15 # [ipmi-fru] "-Dfru-device=true, -Dfru-device=false, i2c-tools," # set openbmc/openbmc/meta-phosphor/recipes-phosphor/configuration/entity-manager_git.bb:18 # [validate-json] "-Dvalidate-json=true, -Dvalidate-json=false, ${PYTHON_PN}-jsonschema-native" # override[pn-opkg]:set openbmc/openbmc/meta-ibm/conf/machine/p10bmc.conf:74 # "curl openssl ssl-curl" # pre-expansion value: # "ipmi-fru" PACKAGECONFIG="" ``` Built an image for yosemite4 and confirmed that fru-device is still installed: ``` root@yosemite4:~# systemctl | grep -i Fru xyz.openbmc_project.FruDevice.service loaded active running Fru Device root@yosemite4:~# systemctl status xyz.openbmc_project.FruDevice.service * xyz.openbmc_project.FruDevice.service - Fru Device Loaded: loaded (/usr/lib/systemd/system/xyz.openbmc_project.FruDevice.service; enabled; preset: enabled) Active: active (running) since Tue 2024-02-27 09:26:26 PST; 8 months 1 day ago Main PID: 368 (fru-device) CPU: 757ms CGroup: /system.slice/xyz.openbmc_project.FruDevice.service `-368 /usr/libexec/entity-manager/fru-device ``` Signed-off-by: Patrick Williams Change-Id: Iaa3d9a8c2a2cf521816b42e36e15de21cf2a0bc2

skeleton: srcrev bump d8c6f5a38f..bba48eafa2

2024-10-13T00:41:04+00:00

George Liu (2): Remove libmapper dependency Fix MD040 warnings Patrick Williams (7): pgood_wait: fix bool include openbmc_intf: regenerate with latest gdbus-codegen libopenbmc_intf: fix various warnings op-pwrctl: fix various warnings pgood_wait: fix various warnings op-hostctl: fix various warnings meson: add basic meson Change-Id: I9bbabd0beca3d277fec3762dd2de63e87d5d5f72 Signed-off-by: Andrew Geissler

meta-phosphor: Reuse dreport utility function

2024-06-28T18:43:58+00:00

install_dreport_user_script function is intended to be reused in meta-openpower layer. To enable this, the function is being moved to a bbclass which would be inherited in the openpower-debug-collector recipe in the meta-openpower layer. dreport.conf file is a variable, hence making it an argument to the function, so that other layer can give a custom dreport.conf as input. Tested: Verified that plugin scripts are getting installed from openpower-debug-collector repository and BMC Dump collection is successful. Change-Id: I8d13bc7e381cd1b957d5770926fb712165a07185 Signed-off-by: Gopichand Paturi

meta-nuvoton: npcm8xx-bootloader: initial recipe

2024-06-27T13:28:28+00:00

Add new recipe npcm8xx-bootloader to replace npcm8xx-igps-native, and also remove relative merge/sign functions and settings. Tested: TIP/No TIP/SA boot OK. Settings replace function work, hardening replace work. Change-Id: I1db20b483cf1de72ce05ca2a14df0a75fdb37d36 Signed-off-by: Brian Ma

meta-phosphor: image_types_phosphor_nuvoton: Don't write u-boot twice

2024-06-15T09:02:41+00:00

The merged binary already gets written once by the `do_generate_static` function in the primary phosphor bbclass. Change-Id: I11a3000ac40063bc2246a23f075a282ebddcb12f Signed-off-by: William A. Kennington III

fit-image.bbclass: correct compress algorithm for kernel image

2024-06-15T07:35:52+00:00

Change default `linux_comp` from `none` to `${FIT_KERNEL_COMP_ALG}` Fixes: 650d9dc ("meta-phosphor: fit-image.bbclass: support compress kernel image") Signed-off-by: James Chiang Signed-off-by: Tim Lee Change-Id: Ib4baba203219ead75f7f3f0d1b082301f2e01ac1

meta-nuvoton: support build norootfs

2024-02-26T11:50:22+00:00

default-distrovars.inc depend on ARCH_DEFAULT_KERNELIMAGETYPE to set KERNEL_IMAGETYPE, vendor could overwrite KERNEL_IMAGETYPE in configuration file to change kernel target build. since static-norootfs.inc set KERNEL_IMAGETYPE and KERNEL_IMAGETYPES as ARCH_DEFAULT_KERNELIMAGETYPE, we overwrite both value to "Image" since arm64 kernel doesn't support zImage target. Add FLASH_MANIFEST_OFFSET and merge_bootloader in nuvoton npcm8xx. Add compress kernel image when build norootfs. Tested: build norootfs evb-npcm845 target ok flash norootfs flash-evb-npcm845 image ok Signed-off-by: James Chiang Signed-off-by: Tim Lee Change-Id: I688cd48f2cc43f464e23f4a1f5408ce5b7195c56

meta-phosphor: fit-image.bbclass: support compress kernel image

2024-01-31T05:44:15+00:00

Extract relevant functions from upstream's kernel-uboot.bbclass in order to be able to support compress kernel image. Signed-off-by: James Chiang Signed-off-by: Tim Lee Change-Id: I74c144e2d60d8276b74dc45767b88ff174e11937