summaryrefslogtreecommitdiff
path: root/meta-amd
AgeCommit message (Collapse)AuthorFilesLines
2023-12-07meta-amd: add Jayanth as co-ownerJayanth Othayoth1-0/+1
Adds Jayanth as co-owner of meta-amd. Change-Id: I7187e70d41265486adf858c71aa8aba2acaf1091 Signed-off-by: Jayanth Othayoth <ojayanth@gmail.com>
2023-11-25treewide: add scarthgap to LAYERSERIES_COMPAT2.16.0-devPatrick Williams3-3/+3
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I28ee50fa55ae47dd7fd8c99f8f6db8f5f6dfa53d
2023-11-24treewide: add nanbield to LAYERSERIES_COMPATPatrick Williams3-3/+3
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I85272779478b66452acd11be93f5fea99e4c3a34
2023-10-11treewide: clean up bmcweb in package groupsPatrick Williams1-1/+0
bmcweb is already added as a default in the meta-phosphor package groups. A large number of machines have mistakenly also explicitly added a RDEPEND on assorted package groups, which is not necessary. Clean these up. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ifd3726d18aab45475f80d054a4640196ac0b71d2
2023-10-11treewide: clean up webui selectionPatrick Williams1-1/+0
The webui-vue package is now enabled by default. Clean up all the meta layers to clean up the explicit enablement. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I4895be56c70d2c8666dd96cec18d2c097f0c05a3
2023-09-26linux-aspeed: Move to Linux v6.5Joel Stanley2-2/+2
This moves the OpenBMC kernel to a v6.5 base for ASPEED. The 6.5 kernel moved all 32-bit ARM device trees, so our BMC device tress are now under an 'aspeed' subdirectory. This change means systems must describe the KERNEL_DEVICETREE with the aspeed directory prefix. There are 78 patches in the tree, with 40 of those patches not yet queued for merging in v6.6. The remaining out of tree patches include: Andrew Jeffery (6): dt-bindings: hwmon: pmbus: Add Maxim MAX31785 documentation pmbus (max31785): Add support for devicetree configuration pmbus (core): One-shot retries for failure to set page pmbus (max31785): Wrap all I2C accessors in one-shot failure handlers ARM: dts: aspeed: witherspoon: Update max31785 node ipmi: kcs_bmc: Add a "raw" character device interface Cédric Le Goater (1): /dev/mem: add a devmem kernel parameter to activate the device Eddie James (16): ARM: dts: aspeed: bonnell: Add reserved memory for TPM event log dt-bindings: soc: Add Aspeed XDMA Engine soc: aspeed: Add XDMA Engine Driver soc: aspeed: xdma: Add user interface soc: aspeed: xdma: Add reset ioctl soc: aspeed: xdma: Add trace events i2c: core: Add mux root adapter operations iio: si7020: Lock root adapter to wait for reset eeprom: ee1004: Enable devices on multiple busses dt-bindings: trivial-devices: Add Atmel AT30TSE004A serial eeprom eeprom: ee1004: Add OF matching support leds: pca955x: Refactor with helper functions and renaming leds: pca955x: Use pointers to driver data rather than I2C client leds: pca955x: Optimize probe led selection leds: pca955x: Add HW blink support leds: Ensure hardware blinking turns off when requested Jae Hyun Yoo (1): clk: ast2600: enable BCLK for PCI/PCIe bus always Joel Stanley (14): net: ftgmac100: Ensure tx descriptor updates are visible ARM: aspeed: Add debugfs directory ARM: soc: aspeed: Add secure boot controller support dt-bindings: trivial-devices: Remove Infineon SLB9673 TPM ARM: dts: nuvoton: npmc750-evb: Add default console tpm: tis-i2c: Add more compatible strings leds: pca955x: Revert "Remove the unused function pca95xx_num_led_regs()" arm64: configs: Add Nuvoton NPCM defconfig ARM: configs: aspeed: Add new FSI drivers ARM: config: aspeed_g5: Enable SSIF BMC driver ARM: config: aspeed: Remove FIRMWARE_MEMMAP ARM: config: aspeed: Add Ampere SMPro drivers ARM: config: Add openbmc defconfig ARM: config: openbmc: Add HPE GPX and Nuvoton 7xx Johannes Holland (1): dt-bindings: tpm: Add schema for TIS I2C devices Potin Lai (1): mtd: spi-nor: winbond: Add support for w25q01jvq Change-Id: Ib97af192391af6e71c96fe14e12cfc88c23d7a7d Signed-off-by: Joel Stanley <joel@jms.id.au>
2023-07-20ipmi-fru-parser: srcrev bump 06514028f8..7153343816Andrew Geissler2-8/+4
Patrick Williams (6): clang-format: copy latest and re-format writefrudata: remove vla strgfnhandler: suppress unused parameter warnings frup: suppress stringop-truncation warning scripts: accept absolute paths to YAML build: enable meson builds build: install strgfnhandler into ipmi-providers dir Vernon Mauery (1): Set new maintainer as Patrick Williams Willy Tu (1): fru-parser: Remove the use of mktime Switch to Meson. Change-Id: Iec9c41cc17a72f84248b8cd75f70353e053f17e2 Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
2023-05-12Revert "Add socket-id for the first console"Andrew Jeffery2-2/+0
This reverts commit ec7cab9378f548e94ee4af83946b2583d1fc7194. ec7cab9378f5 ("Add socket-id for the first console") was only a partial fixup of the obmc-console configurations found in the tree. For historical reasons not all platforms that support multiple consoles install a client configuration file for all consoles. Instead they relied on some default behaviour that was removed in obmc-console's 4e7186918599 ("Fixed broken dbus interface for multiple consoles"). Applying the configuration changes in the manner of ec7cab9378f5 ("Add socket-id for the first console") resulted in an asymmetric configuration between the client and server, breaking some SSH SOL instances. As of ae2460d0b8e8 ("obmc-console: Provide a default value for `console-id`.") in obmc-console the requirement to specify `socket-id`[^1] is lifted. Instead, the configuration can choose to override a default value. This restores the original behaviour and unbreaks SSH SOL. [^1]: Now an alias of the `console-id` configuration key Websocket and IPMI consoles remain broken. A fix is under development that also takes a proper approach to supporting multiple consoles in bmcweb, and the same solution pattern can be applied in ipmid. More discussion of the problems involved can be found here: https://amboar.github.io/notes/2023/05/08/happenings-in-obmc-console.html Change-Id: I274284c791758f336da6d6301dc523bac2b5dd69 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
2023-04-21Add socket-id for the first consoleNinad Palsule2-0/+2
This drop adds socket-id for first console. This was left out before but with the new design this parameter is required and enforced by obmc-console code. It is decided to set "socket-id = console0" initially because that is the current path used by bmcweb but in future you can change this value to whatever is appropriate. The console information is now available through the DBUS interface. Each console server register it's object path on DBUS. The leaf node of the object path is used to create a console path. For example in the following console0 the leaf node "console0" is used to make up the console path and the GUI will use console path "/console/console0" to connect to the console. busctl tree xyz.openbmc_project.Console.console0 `-/xyz `-/xyz/openbmc_project `-/xyz/openbmc_project/console `-/xyz/openbmc_project/console/console0 Here is a discord thread where new design was discussed. https://discord.com/channels/775381525260664832/1083551792094249051 Tested: Tested on the rainier system. Related commits: 1) phosphor-dbus-interface: https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/61486 2) obmc-console: https://gerrit.openbmc.org/c/openbmc/obmc-console/+/62496 3) bmcweb: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/62525 Change-Id: I5fd06f3aac69872a3e5032d592a9b59711795cfe Signed-off-by: Ninad Palsule <ninadpalsule@us.ibm.com>
2023-04-14meta-amd: fix up new shellcheck warningsAndrew Geissler2-296/+296
New docker container is flagging some issues in this shell script: ``` SC2322 (style): In arithmetic contexts, ((x)) is the same as (x). Prefer only one layer of parentheses. SC2046 (warning): Quote this to prevent word splitting. SC2219 (style): Instead of 'let expr', prefer (( expr )). ``` Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I46dac4da799a9e3256bb5f1829784253be67716f
2023-04-14meta-daytonax: Enable ipmitool sol functionalityKonstantin Aladyshev2-0/+21
To enable Serial-Over-LAN functionality via the standard "ipmitool sol" command it is necessary to create a DBUS interface "xyz.openbmc_project.Ipmi.SOL" that would be used for the communication between the "phosphor-net-ipmid" and "phosphor-host-ipmid" applications. Change-Id: I8a63c233f321fe540d73ef33305beb0aa555796a Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-04-14meta-ethanolx: Relax ipmitool sol settingsKonstantin Aladyshev1-1/+1
Current SoL settings cause 'ipmitool sol' to crash after some working time. Increase RetryIntervalMS to fix the issue. Change-Id: I650b7d642f7f3e13df1f2d433b612cee6e1f5616 Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-04-14meta-amd: Change unit type of 'ip-to-fpga.service'Konstantin Aladyshev1-1/+1
Currently with the 'oneshot' unit type the 'ip-to-fpga.service' is always in the 'running' state: ``` root@ethanolx:~# systemctl list-jobs JOB UNIT TYPE STATE 88 obmc-led-group-start@bmc_booted.service start waiting 1 multi-user.target start waiting 126 ip-to-fpga.service start running 3 jobs listed. ``` This creates a problem since 'srvcfg-manager' service expects every startup job to finish. Change unit type to 'simple' to fix the issue. Change-Id: I45840ef432ce33be400b547420ab5ceeca949ba0 Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-04-14meta-amd: Add srvcfg-manager application for IPMI SoLKonstantin Aladyshev1-0/+1
'phosphor-net-ipmid' application now requires 'xyz.openbmc_project.Control.Service.Attributes' interface for the SoL functionality to work correctly. This interface is provided by the 'srvcfg-manager' application, therefore include it to the build. Change-Id: I0c0473df2d12cf7124dc07fa4c41e84d6e82bb5f Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-04-10meta-amd: Use correct syntax to append SRC_URI on overrideKonstantin Aladyshev2-4/+4
'SRC_URI:<machine> +=' syntax creates new variable 'SRC_URI:<machine>'. 'SRC_URI:append:<machine> =' syntax appends the variable 'SRC_URI' when appropriate machine is selected. hostlogger and obmc-console recipes incorrectly use the first syntax in places where they should use the second one. This leads to build error, when bitbake can't find added files. Correct recipes to fix ethanolx/daytonax boards build. Change-Id: Ibf424b95ae5aadf4c2ffd5915d746fb19f2a6d66 Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-03-27treewide: switch '/usr/share' to datadirPatrick Williams2-8/+8
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I8ea79d284356629f5b7b24ad3a99336e9e2e297e
2023-02-10meta-ethanolx: Add service to transfer BMC IP to FPGAKonstantin Aladyshev4-0/+70
If switch SW2-7 is on, FPGA shows BMC IP address on the 7-segment displays. For that functionality to work correctly BMC needs to write its own IP address to the paticular FPGA I2C registers. Add a service that performs this action on every IP change. Change-Id: Iead978ef3651448f4c32936402607fbb3267ee18 Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-02-08meta-amd: Remove skeleton_workbookKonstantin Aladyshev1-2/+2
Drop skeleton_workbook from the machine configuration. This is an obsolete feature that shouldn't be used for modern systems. Change-Id: I183044341548708265cd74f3d19c1b2266be3fc6 Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-02-08meta-amd: Create common machine configuration fileKonstantin Aladyshev3-49/+25
Move common machine configurations to the include file. Change-Id: Iafd07c4d6dc1abdcffede7568e6aef16e2f53ac4 Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-02-08meta-amd: Add AMD Daytonax CRBKonstantin Aladyshev32-1/+5010
Add AMD DaytonaX CRB to the meta-amd layer. Change-Id: I7df37f78640e9cc9c595da257bfc982d8f636acd Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-01-27meta-ethanolx: Prepare layer for daytonax boardKonstantin Aladyshev3-6/+6
All configurations that are specific for the EthanolX board are needed to have ":ethanolx" override. Change-Id: I7b3381a1f486168bcd12a1ac0fb4756a31fb0487 Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-01-27meta-ethanolx: Add JSON file for the x86-power-controlKonstantin Aladyshev2-0/+67
"x86-power-control" doesn't allow to set BMC_READY signal, but besides that everything is compatible with the upstream code. Change-Id: Ic60bfa7b7cbb85494c542fea9b3fd480beec0a12 Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-01-27meta-ethanolx: Populate "redfish/v1/Systems/system"Konstantin Aladyshev1-1/+2
The "redfish/v1/Systems/system" page is necessary to fill the "Server information" panel in the webui-vue application. Change-Id: Id8ee7b6ab504cd38916f92fd6dda9d99dfdd898c Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-01-27meta-ethanolx: Enable ipmitool sol functionalityKonstantin Aladyshev2-0/+21
To enable Serial-Over-LAN functionality via the standard "ipmitool sol" command it is necessary to create a DBUS interface "xyz.openbmc_project.Ipmi.SOL" that would be used for the communication between the "phosphor-net-ipmid" and "phosphor-host-ipmid" applications. Change-Id: I41eaac0eb53b66d135032c14e69abbe5e97509ce Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
2023-01-27meta-ethanolx: Add PID control for fansKonstantin Aladyshev5-26/+344
Add support for dynamic fan RPM control based on the values from temperature sensors. Control is based on PIDs and is splitted to 3 thermal zones: Zone 1: - CPU0 SB-TSI temp with a setpoint 60.0 C - P0 FAN Zone 2: - CPU1 SB-TSI temp with a setpoint 60.0 C - P1 FAN Zone 3: - All LM75A sensors on board with a setpoint 35.0 C - SYS FAN1 - SYS FAN6 Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com> Change-Id: Ifca359ba23777e2b1f46783272cf98ff0b08fe68
2023-01-13yocto:mickledore: add support for new yocto layerAndrew Geissler2-2/+2
Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
2022-12-12Remove patches against OpenBMC projectsEd Tanous2-823/+0
It's not clear why these patches were added in this manner, but they can't really remain here from a maintenance perspective. Pinning one platform on an old version of x86-power-control, as well as setting a specific patch means that it's impossible for people to test and use upstream code with it. It is also explicitly called out as item #1 on the meta layer guidelines for this reason: https://github.com/openbmc/docs/blob/master/meta-layer-guidelines.md To the maintainters of this meta layer, please work with Jason and Kwin (the x86-power-control maintainers) to get your features accounted for in the normal build, adding build flags and configuration entries where appropriate. Tested: This almost certainly breaks power control on ethanolx, but given the way this patch was merged, there's really no way to avoid that. Signed-off-by: Ed Tanous <ed@tanous.net> Change-Id: I1f6a40e5b01c36441ff8d66e8e73265e0e009a4f
2022-11-30meta-ethanolx: switch u-boot to 2019.04Konstantin Aladyshev1-5/+2
Switch the u-boot branch from the 2016.07-aspeed-openbmc to the 2019.04-aspeed-openbmc. Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com> Change-Id: I7f17b31abe32c374b01cb037ba03ed2608c1190d
2022-10-14treewide: remove obmc-op-control-host for non-openpower machinesPatrick Williams1-1/+0
The code for obmc-op-control-host is only useful for OpenPower machines, but somehow it is being included in many other machines. Remove it from all of them except meta-openpower. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I4e7c7365eb320c3fb9ea7a57aca2ed0b1832e85e
2022-10-13meta-ethanolx: Correct 'obmc-console' configuration fileKonstantin Aladyshev1-1/+0
In the AMD EthanolX board CPU0 UART1 is connected to the BMC UART0. Therefore from the point of BMC UART0 is an upstream (host) UART. 'obmc-console' application gets this information from its configuration file name ('server.ttyS0.conf'). On the other case setting 'local-tty' inside the configuration file is intended for the downstream UART settings, which is not present on the AMD EthanolX board. Therefore remove this setting. Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com> Change-Id: I3daa1528cb5a7b5ff748189f29da3c3d91899ca4
2022-09-30add langdale to compatible layerAndrew Geissler2-2/+2
Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I65febeeec11e6e5b40ee728f42cfbe77023dae1e
2022-09-12treewide: handle more upstream TEMPLATECONF movePatrick Williams1-0/+0
We also need to move the conf-notes.txt files. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ic44e015c0216b526de4fec277ad42f162bca1f33
2022-09-09treewide: handle upstream TEMPLATECONF movePatrick Williams2-0/+0
The latest poky commit is requiring us to have all of our template configs in a subdirectory instead of directly in the `conf` directory. Without this we end up with errors during setup like: ``` Error: TEMPLATECONF value (which is .../openbmc/meta-facebook/meta-bletchley/conf) must point to meta-some-layer/conf/templates/template-name ``` Fix this by moving all of our template files into the 'default' template subdirectory (following the pattern of poky) and modifying `setup` as necessary to follow. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Iecefde73d55acbb6bc63ae3d68c4311adaf327ae
2022-06-21phosphor-host-ipmid: srcrev bump 33d90e182d..0e7a8af0e5Andrew Geissler1-3/+3
Harvey.Wu (2): dbus-sdr: fix SEL record Generator ID to fit SPEC dbus-sdr: fix the vector size in sdrWriteTable and sdrStatsTable Jian Zhang (1): Add data types to Value to extend setDbusProperty Vernon Mauery (1): fix header install Willy Tu (4): cleanup: Remove all warning errors for the Meson build support build: Add meson build for phosphor-host-ipmi build: move all shared_library/module to library with version suffix build: Remove dynamicsensor library if it is not enabled Change-Id: I92503c6625d1ec2bf88c0a28afac9b4eeb8fbd75 Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com> Signed-off-by: Willy Tu <wltu@google.com>
2022-04-30treewide: remove meta-perlPatrick Williams1-1/+0
The only recipes which use content from meta-perl are openpower machines: ``` meta-openpower/recipes-bsp/pdata/pdata_git.bb: libxml-libxml-perl-native \ meta-yadro/meta-nicole/recipes-phosphor/logging/openpower-esel-parser_git.bb: libxml-libxml-perl-native \ ``` Remove meta-perl from the bblayers of every layer except openpower machines. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I51f1a8fbfbe879295c64d2339fc115dbd8823681
2022-04-22treewide: drop unused meta-security layerBrad Bishop1-1/+0
This was added with cde0f094f for libseccomp, but shortly after that upstream moved libseccomp from meta-security to core (241c7d2e6). As such, meta-security is no longer used or required. Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Change-Id: I371e54b11f6336720dfc6edf0ef733d22b7fb4f2
2022-04-12treewide: Update BB_DISKMON_DIRS useGeorge Liu1-4/+4
Per [1][2], Yocto is starting to deprecate ABORT and has replaced the "ABORT" action in BB_DISKMON_DIRS entries with "HALT". 1. https://wiki.yoctoproject.org/wiki/Inclusive_language 2. https://git.yoctoproject.org/poky/commit/?id=4f77505d94a8f6260933f457e9848d1d2fa98ce5 Tested: Built obmc-phosphor-image successfully and eliminate the following warnings: ``` WARNING: The BB_DISKMON_DIRS "ABORT" action has been renamed to "HALT", update configuration ``` Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: If57d0ded9fac41e23b31b01e2a0e309ac7388148
2022-02-26treewide: remove image-prelink bbclass usagePatrick Williams1-2/+1
Upstream has removed the image-prelink bbclass[1], so remove it from any local.conf.sample that still has it enabled. 1. https://git.openembedded.org/openembedded-core/commit/?id=857baaf9e3d181ca18264e85d90b899fd94acff9 Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I70f42f8816f5dea207fcf5c34837d6796b3f6bb6
2022-02-26treewide: support yocto kirkstone releasePatrick Williams2-2/+2
* Deprecate N-1 release (hardknott). * Enable N+1 release (kirkstone). Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
2022-02-22treewide: remove MAINTAINERSPatrick Williams1-45/+0
The MAINTAINERS files are no longer used and are out of date (references to IRC still exist in most of them). Remove them and rely on the OWNERS exclusively. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I0f5d2719ad97e218ce03c4503efe1b1c92ac455e
2022-01-18u-boot: Specify u-boot package for AST2500 machinesJoel Stanley1-0/+4
This sets u-boot to the package containing the v2016.07-aspeed-openbmc branch. This ensures there will be no change if the default changes in the future. Change-Id: Iea12e1691dbdda34a3f95d6d0862add0b15bcf37 Signed-off-by: Joel Stanley <joel@jms.id.au>
2021-12-02Remove BBLAYERS_NON_REMOVABLE variableAlexander Filippov1-12/+0
`BBLAYERS_NON_REMOVABLE` is obsolete and no longer required. As it said by Yocto documentation it can be used by `Hob` https://www.yoctoproject.org/docs/1.5.2/ref-manual/ref-manual.html#var-BBLAYERS_NON_REMOVABLE that already removed since Yocto-2.1 https://www.yoctoproject.org/tools-resources/projects/hob Change-Id: Ibc2d8268a9d837a81e9cf6b0131dba8d0a030a3f Signed-off-by: Alexander Filippov <a.filippov@yadro.com>
2021-11-04Partially revert "treewide: remove obmc-system-mgmt feature"Patrick Williams2-0/+3
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>
2021-10-26treewide: remove obmc-system-mgmt featurePatrick Williams2-3/+0
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
2021-10-26treewide: clean up use of OBMC_MACHINE_FEATURESPatrick Williams1-1/+1
Modify the machine meta-layer configs to remove the use of the OBMC_MACHINE_FEATURES indirection and favor the Yocto MACHINE_FEATURES variable instead. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ifafb79e4e4c010e9476b9547cd4982f5b645060e
2021-09-16treewide: fix comments for rpm/ipkPatrick Williams1-1/+1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ia05891430c6c97a89b7bc8ba4558ae496866bf7d
2021-09-16bitbake: Use IPK packaging for rootfs assemblyAndrew Jeffery1-1/+1
bitbake offers a choice of DEB, RPM or IPK packaging. To a degree the choice is functionally arbitrary for image generation but control over the package format becomes important if we want to: 1. Include runtime package management functionality in the firmware image 2. Mess about with the packages on the build system With respect to 1 the IPK format and opkg (an ipk package manager) are designed for embedded systems[1] - by contrast to RPMs have heavier dependencies and a greater impact on the size and complexity of the firmware image. Regarding 2, the embedded nature and the need for opkg to work without much fuss leads to a lower configuration barrier by comparison to RPMs. With ipk it becomes possible to reuse the packages built during image preparation for core analysis without needing to generate an SDK: ``` $ export LD_LIBRARY_PATH=./tmp/work/x86_64-linux/opkg-native/*/recipe-sysroot-native/usr/lib $ MY_DEBUG_ROOT=tmp/rootfs-debug $ ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \ -f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/*/opkg.conf \ -o $MY_DEBUG_ROOT \ update $ fakeroot ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \ -f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/opkg.conf \ -o $MY_DEBUG_ROOT \ install dbus-sensors dbus-sensors-dbg $ gdb-multiarch (gdb) set solib-absolute-prefix .../tmp/rootfs-debug (gdb) add-auto-load-safe-path .../tmp/rootfs-debug (gdb) file tmp/rootfs-debug/usr/bin/nvmesensor (gdb) core-file obmcdump_17_9597/core.nvmesensor.0.aae91b519d0e4e0e8bbe746e3f6cd25f.2779.9594000000 Core was generated by `/usr/bin/nvmesensor'. Program terminated with signal SIGABRT, Aborted. pthread_kill.c:45 45 pthread_kill.c: No such file or directory. (gdb) bt pthread_kill.c:45 ../sysdeps/posix/raise.c:26 /home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6 /home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6 /home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6 /home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6 "xyz.openbmc_project.NVMeSensor", this=0x488f04) at /usr/include/sdbusplus/bus.hpp:234 ../../../../../../workspace/sources/dbus-sensors/src/NVMeSensorMain.cpp:159 (gdb) ``` This approach documented in the Poky Reference Manual: https://www.yoctoproject.org/docs/1.0/poky-ref-manual/poky-ref-manual.html#platdev-gdb-remotedebug-launch-gdb-inferiorbins Switch all machines to IPK to align the debugging experience with upstream's documentation and to facilitate efficient use of packaged software at runtime. [1] https://openwrt.org/docs/guide-user/additional-software/opkg Change-Id: I8ef526add2d7a6790de1b3eb3fb85cd39b864f23 Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
2021-09-10meta-amd: fix compilation errors with latest YoctoKonstantin Aladyshev19-43/+43
Make the following changes to fix compilation errors: - add honister to the LAYERSERIES_COMPAT variable, - increase CONF_VERSION to 2, - use new bitbake override syntax Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com> Change-Id: I971f0f0f7110e0350994ced151ca429444885056
2021-09-10meta-ethanolx: Add driver for the FRU EEPROMKonstantin Aladyshev1-0/+1
AMD EthanolX CRB uses 24LC128 EEPROM as a device that is supposed to store FRU information. Add necessary Linux driver that adds support for this chip. Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com> Change-Id: Iaf54bfd5bfbc3266d2a18861ee47339df78c777b
2021-08-30meta-ethanolx: Fix CPU fan names in IPMI YAML fileKonstantin Aladyshev1-2/+2
The BMC on the AMD Ethanol CRB uses entity-manager for sensor configuration. Therefore IPMI configuration YAML file should use DBus paths to sensors based on the names from the entity-manager JSON files. Currently 'ethanolx-chassis.json' exports CPU fans on a DBus as "P0_Fan"/"P1_Fan". Use these names to correctly populate CPU fans to the IPMI. Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com> Change-Id: I0425e42771e1bfb36ad067dfcad5a23e5f180d67
generated by cgit v1.2.3 (git 2.39.0) at 2024-06-28 15:25:00 +0300