summaryrefslogtreecommitdiff
path: root/meta-ibm
AgeCommit message (Collapse)AuthorFilesLines
2020-11-18fans:witherspoon: Disable JSON on fan controlMatthew Barth1-1/+3
Witherspoon should still use YAML based configs for fan control instead of JSON. Once all of fan control's JSON support is available and witherspoon's YAML fan configs are converted to JSON, this can be removed to enable JSON. *Temporarily pin to 8e1b382122fed73e788d44f3a67cecbfbcc6972e to pass CI (From meta-ibm rev: 7ec9b860b5ea1d986702bb978b528ddcd28f2ce5) Change-Id: Ic31f5ab915d5478b9a2027732bd3ffd44f50b02f Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-11-18rainier: Add virtual ambient temp thresholdsMatt Spinler1-0/+7
The phosphor-virtual-sensor code recently started checking the values of the upper/lower warning/critical thresholds for the virtual sensors and prints to the journal if they are exceeded. If the threshold values to use aren't specified in the JSON file, it will just set them to zero so any nonzero sensor value will trigger the trace. So, even though code will not use the threshold values for the virtual ambient temperature sensor, put some into the JSON anyway that should never be exceeded to avoid these traces. If the temperature does happen to go outside the range of between 0 and 100, then seeing the trace may be interesting anyway. (From meta-ibm rev: 9fdb9598d0eee4d9820962320391bb9f7e4568ea) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I1c6c5f1faaaf58599a3840eed6ec4749a70a1364 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-11-18remove += from _appendAndrew Geissler1-1/+1
No need to use _append and += (From meta-ibm rev: 72b20dddfcd790a0a0398ec4c16e76b54866b989) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ibcbd5c83a137799f4f80d017e19a8d9b9a9f681f Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-11-17rainier: Only install one dbus-sensors serviceMatt Spinler1-0/+1
Rainier is only using the hwmontempsensor dbus-sensors service for now, so remove the other ones. Without this, 8 other services would be running at BMC ready state. (From meta-ibm rev: b51345ced440ca935f8678d8521a690301e63db5) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: If60d9a0ba585c029877c5fda77b5085cec394d04 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-11-12wistron-ipmi-oem: srcrev bump 44cee319dd..ba89a1ea57Andrew Geissler1-1/+1
Ben Pai (1): Add wistron oem command to switch 250 soc image (From meta-ibm rev: 3aa9904064a954031fac32b462c26c0b6d541ef1) Change-Id: I6cc97288c35a1ac1f97f55ad0fe179dce9636bb0 Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-11-12rainier: Add a virtual ambient temp sensorMatt Spinler3-1/+31
Use the virtual-sensor application to put a virtual ambient temperature sensor on D-Bus. Currently, it just mirrors the value of the TMP275 ambient temperature sensor, but in the future the output will be based on all three temp sensors on the panel after the remaining two show up on D-Bus. (From meta-ibm rev: f43eab1e5637cf87a38ca2e9a6acc33e5db3a0c3) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I187d88c7e1245c7014aee8b9b6c0840daf1e622d Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-11-12rainier: Add dbus-sensorsMatt Spinler1-1/+1
Add dbus-sensors to the Rainier flash image. This repository holds a suite of applications for managing various types of sensors. It uses D-Bus interfaces provided by entity-manager to know which sensors to monitor. Rainier will use it for at least some of the temperature sensors. (From meta-ibm rev: 29cc525d9cb736f4cfa0bc17bb45771fd812234e) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I81f9311adb9d72de1b04f9aed0a2d9e778b3e03a Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-11-12meta-ibm: Move Tacoma and Rainier to eMMC u-boot configJoel Stanley2-2/+2
The AST2600 systems booted from NOR during bringup, but now that we have eMMC support in u-boot they can run from eMMC. (From meta-ibm rev: 46419c51c3bd3d43873ecbab7fbbb6f1d6c54de4) Signed-off-by: Joel Stanley <joel@jms.id.au> Change-Id: Idd2389ab62e1b7cc32639f5547f1f1098631654f Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-11-06meta-ibm: update Yocto compat for gatesgarthPatrick Williams1-1/+1
The next release of Yocto is soon and most of the upstream layers have switched support strings for it. Support layer compat for gatesgarth (current) and dunsfell (previous). (From meta-ibm rev: 00e954d3100bb932d154273376620b40d6b8cad3) Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Iffd47517e7b9e85597fe97478375a48d0c2db927 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-11-03gatesgarth: add support for new seriesAndrew Geissler3-3/+3
As we add support for a new series, remove support for the oldest. Little to no testing is done with older ones. (From meta-ibm rev: 6255d23fd68023fdc838d0a2262b43883b86be58) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Id63754bdc8ec82628cad23427bfdadafca380c15 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-29Revert "tacoma: Remove CP0 reset"Andrew Geissler1-0/+3
This reverts commit 5ef58e42bd2c27605cd952bf590b2879759425d8. There is a unknown issue with Tacoma hardware in which the CP0 reset needs to happen within the power_control.exe. The theory is it is timing related (i.e. the CP0 reset needs to occur extremely close to the power being turned on). Given that Tacoma is a development system, time has not been allotted to getting to the bottom of this. It works fine on some systems, but fails catastrophically on others with an assortment of power fault errors. Due to this issue, we can not utilize the new kernel mechanism for controlling CP0 on Tacomas. (From meta-ibm rev: 4bc5a4720757e6aa8b349869adc2dceb53a8b9f1) Change-Id: Ib0afbfc4386bf74ffa264c1e0ac3aaa04016a040 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-29Use correct type for Dbus sensor interface in IPMI sensors YAML filesKonstantin Aladyshev6-163/+163
Dbus sensor interface 'xyz.openbmc_project.Sensor.Value' migrated from int to double. Therefore all old 'int64_t' types in "*-ipmi-sensor*.yaml" files for this interface should be changed to 'double'. (From meta-ibm rev: c769f790e14b9caa4fc842dc1e2035378de6ae60) Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com> Change-Id: Id8e164203541550eb19301ca429702cbf7d4b2f8 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-22wdt-on-panic: remove from withespoon and mihawkAndrew Geissler2-2/+0
At a high level, the purpose of this feature was to utilize the BMC hardware watchdogs to switch the BMC boot flash when certain errors were hit which were preventing the BMC from booting. At a high level, this worked but some critical issues were found with this: - No failure data is gathered to understand why the boot flash was switched - No event or error is logged to notify the user of the system that the boot flash has switched - At times, switching sides didn't help because the BMC network information was not properly copied to the other boot flash which caused even more confusion for the user Give the above, this patch proposes a reset on this logic until we can come back and address the above issues and get this working end to end. (From meta-ibm rev: d5069cffe865ea104915d8e0fdbe8d7d145644fc) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I8c8d2b30c80940f4674e6c6848bd22f759e943a5 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-21Enable mangement console code for ibm machinesManojkiran Eda1-0/+1
- This commit would enable the ibm-management-console compile-time option for all the ibm machines. (From meta-ibm rev: 9831b3a45141d4dc08b2624f07059299d65a9d7f) Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I69abd87d28903d27d2390f20153d730f658f8068 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-16sensors:max31785: Remove `x` perms from udev rule fileMatthew Barth1-1/+1
Remove executable permissions from the `70-max31785-hwmon.rules` file to eliminate the systemd-udevd warning that its marked executable. (From meta-ibm rev: 46984b5eda5c40e63cb9fab6aa5e667cec7f5b68) Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Change-Id: Ic7405ed73f2d7875c57696ae4e5b30e380502fd6 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-14ibm-specific: install hypervisor certificate manager serviceRavi Teja1-0/+2
this commit is to enable hypervisor certficate manager feature and install service for rainier and tacoma (From meta-ibm rev: cf7a5811a21645a556b5e66433ce08ff67cf7cb2) Signed-off-by: Ravi Teja <raviteja28031990@gmail.com> Change-Id: Ia38083851444134a55ff1b488f921b75cbd0d2e8 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-14Enable OpenPower dumps on supported systems.Dhruvaraj Subhashchandran1-0/+3
Enable OpenPower dumps on Tacoma and Rainier (From meta-ibm rev: 0ce518f660df9490da3373dd64b580ea8672c93d) Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> Change-Id: Ic756ecbd793ca465ce3d6dc31ad93ac5170654d0 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-14disable warm reboot on romulusAndrew Geissler1-0/+2
Similar to commit 567a8d for witherspoon, this issue has now popped up on Romulus hardware. The concept of warm reboot (reboot the host without removing chassis power) was added a while back as a part of clarifying support for the Redfish ComputerSystem.Reset Action. It has since been found that some IBM hardware, including Romulus, do not support warm reboots. The issue is intermittent and depends on the reboot being requested while the host is in the middle of some i2c transactions. If a warm reboot occurs during this window, then on the subsequent boot the i2c hardware will be in a bad state and the host firmware is unable to recover it. Given this issue, it has been requested that BMC software go back to doing cold reboots (cycling power to the chassis during any reboot request) on this hardware. (From meta-ibm rev: 718f2b5405c2c1f000cc0ccbf2860a283997c08a) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I31810e89977532d4368050871aba03d78deb9c59 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-07meta-ibm : switch bmcweb to meson build systemManojkiran Eda1-2/+2
- This commit would switch the bmcweb options to meson (From meta-ibm rev: fea636a8486e20e8ccd865670f56d34c9700a043) Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: Ieda83403ff381c616664170462915198fdf30507 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-07rainier: Enable pstore to expose ramoops dataAndrew Jeffery1-0/+4
(From meta-ibm rev: 03ff1fa3f6ce475760535c08dfea9b751aa71f65) Change-Id: I17ddb7eef0853cb0a3ae23ab0f67043b931afc34 Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-07meta-ibm: Enable com/ibm D-Bus interfaces on all systemsSantosh Puranik2-1/+2
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>
2020-10-02witherspoon-tacoma: do not install ikvmAndrew Geissler1-0/+2
witherspoon-tacoma systems do not utilize this feature (From meta-ibm rev: b32849212c59c6383543ba769b8b4f6e2fbbc48b) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I59c5b19b6ad140447f5cdf4184db5acf251c2842 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-02tacoma: Remove CP0 resetJoel Stanley1-3/+0
This is wired as to do nothing on normal Witherspoons, so the code to do so has questionable utility. On Tacoma systems, the Witherspoon motherboard is reworked to allow the BMC to control the reset. The control is provided as part of the FSI driver in the kernel, so it should be removed from the userspace power control tool. Fixing this should resolve this message when doing poweron: power_control.exe[250]: ERROR PowerControl: GPIO open error (gpio=BMC_CP0_RESET_N,rc=2) The GPIO device can't be opened as the kernel has control of it. (From meta-ibm rev: 5ef58e42bd2c27605cd952bf590b2879759425d8) Change-Id: Id6889d8d889272a82c80b64ea3fa31ac4a464458 Signed-off-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-02rainier: do not install ikvmAndrew Geissler1-0/+2
rainier systems do not utilize this feature (From meta-ibm rev: dcfa1a4d7ad4065d983e3bf77cc88d5167492e9d) Change-Id: I0a9b430c8245016237c0f168781ecf0b68438f96 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-10-02rainier and tacoma: Build U-Boot SPLAdriana Kobylak2-2/+4
Build the u-boot and the SPL binary. The image_types_phosphor.bbclass keys off these configs to concatenate them together into a single file which is used during code update to update the device where the SPL+U-Boot reside. (From meta-ibm rev: 2e8a6ac2986dfbfc62139355cf663ec5161cb1b9) Change-Id: Ia17635ef68c059bfa6fd937ac806c3f21fad8c84 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-09-30meta-ibm: rainier: install dump header scriptChirag Sharma1-2/+10
This commit will install the dump header script which will create dump header and impose the same on the dump.tar.xz file. Header format will consist of the following: -virtual file directory entry: one file directory entry for BMC DUMP, which will have file header and size of 40 bytes which consists of system serial number, dump identifier, time stamp of the dump. -section directory entry: This has SECTION as entry header, size is of 30 bytes consists of total size of the dump along with other details. -dump header: This has an eye catcher "BMC DUMP", dump identifier, system serial number, system name etc. -dump data table: This will have dump version, dump valid field and number of dump entries. (From meta-ibm rev: 49710574e0e40b98d1b671b95568314838d55985) Change-Id: I7906b6d602a8fd27655c90eb632ce55eaf8ab63a Signed-off-by: Chirag Sharma <chirshar@in.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-09-30meta-ibm: mihawk: Solve the issue of cannot reading 250 soc temperatureBen Pai5-4/+4
Mihawk cannot read the 250 soc sensor on the riser, this is because dts defines pca9545riser@70 instead of pca9545@70. (From meta-ibm rev: 731297ebde0eb4272d39260a30cd5f5b1f4e6f1a) Change-Id: Ibcb72ef6be7c953cc35cc216e8cc45e283949e61 Signed-off-by: Ben Pai <Ben_Pai@wistron.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-09-26meta-ibm: rainier: add processor includeBrad Bishop1-0/+1
Prior to this patch the Rainier system doesn't include any host processor configuration. Rainier is a server with a host processor, so include the correct host processor configuration. (From meta-ibm rev: 5b44384b92419673b1ce7cca40c5dc613cc6d60a) Change-Id: I3da77be772c3cd0f89539c8e56c5d0719ad84c44 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-09-17fans: Update service start limits for fan watchdogMatthew Barth1-2/+0
It was found that the fan control services were constantly getting restarted due to not failing within the previous start limits. After experimenting with different combinations of limits, using the default values for StartLimitBurst and StartLimitIntervalSec is sufficient. Tested: Changed limits, powered on, watched service fails in journal until fan watchdog monitor started Resolves: https://github.com/openbmc/phosphor-fan-presence/issues/23 (From meta-ibm rev: b8a65368cb39d6d82c4b025b25fdbe868dbbfe89) Change-Id: Ibcb35028e8dbc67d7df70dfeee25d098e6041fe8 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-09-17meta-ibm: phosphor-dbus-interfaces: remove unused bbappendPatrick Williams1-1/+0
The flags set by this bbappend are now handled automatically by the phosphor-dbus-interfaces recipe. (From meta-ibm rev: 73b735f30bb866b27e05fe6381064e5a9a55977b) Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Icf4e7beebaeea99ea74214989290d92ee4d006ee Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-09-03Move bmcweb bbappend files to interfacesManojkiran Eda1-0/+0
- meta-phosphor has bmcweb bitbake file under interfaces,so moving the append files accordingly. (From meta-ibm rev: b7952717a7c74b0ebda2d7971f75b1b060f8911c) Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I86ba09396f109f0987220bcdd070a0fff8e1e972 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-08-14Move Rainier and Witherspoon-tacoma to Vue GUIGunnar Mills1-4/+4
Leave the rest of the IBM AC Servers on phosphor-webui since things like two file firmware update and Virtual Media are not currently supported on webui-vue. The hope is in the near future to move all IBM Servers to webui-vue, including all ibm-ac-servers (e.g. Witherspooon). webui-vue is a complete rewrite of phosphor-webui. It uses the Redfish API, is translatable, themeable, does not suffer some the anti-patterns that exist in phosphor-webui today and is built on Vue. phosphor-webui was built on AngularJS and AngularJS goes End of Life June 2021. Huge shoutout to the team here, webui-vue is an impressive GUI! (From meta-ibm rev: 4d34f6c2bbde77d219d6a5ce306059661b80734c) Tested: Built Witherspoon, see the AngularJS GUI. Built witherspoon-tacoma see the Vue GUI. Change-Id: I2d4ac657070b694381779a5bfe0bb8b202db97e3 Signed-off-by: Gunnar Mills <gmills@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2020-08-06ibm: Remove fru-fault-monitor from 2 systemsMatt Spinler1-0/+2
This application sets LEDs based on the contents of OpenBMC event logs, and this will be done a different way on Rainier and Witherspoon-tacoma so remove it. (From meta-ibm rev: 553390e70165dc71f0efa3de074b497d998736e2) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I7831a225edc6382ee94b8c372ac6b2717bad172a Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-08-04Move tacoma and rainier to eMMC configurationAdriana Kobylak2-4/+10
For tacoma, adjusting the size of the eMMC image by making the hostfw partition smaller. (From meta-ibm rev: f12da2705f487a933cbf291c129d3832b91d1816) Change-Id: Ic13d141d41ab513f2af7bff790efc7529739b11d Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-08-04meta-ibm: collect PEL files during a dumpMatt Spinler2-0/+19
This collects all of the PEL files on user and elog dumps. They will show up in a subdirectory named 'logs' in the dump. (From meta-ibm rev: 1a247b7c27ec3021bf7396874d34844ca2e6b033) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ia23a2fb72acfc1e4473d3c47ad78e34b37529f34 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-07-15meta-ibm:implement phosphor-power for Mihawk platformAndyYFWang7-5/+63
Implement power-sequencer of phosphor-power for mihawk. (From meta-ibm rev: 65dbe8b7c2ed9507ea5842e6e91b637a9069b947) Change-Id: I00ee20fbcfcd6dc34724c2f7caf50cf7ae94d124 Signed-off-by: Andy YF Wang <Andy_YF_Wang@wistron.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-07-15meta-ibm: mihawk: Add 250 soc thermal sensorBen Pai10-0/+49
Mihawk can use up to eight 250-soc. Tested: The user can see the temperature when using 250-soc. (From meta-ibm rev: 74b7557b08ed2582861cd7da390d84371ec2ff86) Change-Id: I17b0d969d0902f6470287c6164f542ad84412f7d Signed-off-by: Ben Pai <Ben_Pai@wistron.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-07-15meta-ibm: Mihawk fan control support 250 soc thermal sensorBen Pai1-0/+50
Fan control must support 250 soc thermal sensor. Tested: Fan speed is automatically controlled when using 250 soc (From meta-ibm rev: 05540e77d337f466bc339715153704edff3f6b88) Change-Id: Ic17854a8556b5878bf506bfafd64762315390c39 Signed-off-by: Ben Pai <Ben_Pai@wistron.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-07-08disable warm reboot on witherspoonAndrew Geissler1-0/+1
The concept of warm reboot (reboot the host without removing chassis power) was added a while back as a part of clarifying support for the Redfish ComputerSystem.Reset Action. It has since been found that some IBM hardware, including Witherspoon, does not support warm reboots. The issue is intermittent and depends on the reboot being requested while the host is in the middle of some i2c transactions. If a warm reboot occurs during this window, then on the subsequent boot the i2c hardware will be in a bad state and the host firmware is unable to recover it. Given this issue, it has been requested that BMC software go back to doing cold reboots (cycling power to the chassis during any reboot request) on this hardware. The issue has only been reported on Witherspoon so for now only disable it on that platform. Tested: - Verified within QEMU that an image with this commit used the cold reboot target during a warm reboot request (From meta-ibm rev: 567a8dcf84dfb74e7bd27d6239be2878fcacdde6) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I8d77c5e8bf7378a3d1accc79b510f14626a333e5 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-07-08Add DHCP D-Bus objects for Hypervisor Virtual Management InterfaceSunitha Harish2-1/+24
This commit adds the D-Bus objects to enable the DHCP on the hypervisor's virtual management interface. New attributes are : 1. DHCPEnabled - At Interface level. Values will be "v4/v6/both/none". Default is "none" 2. Enabled - At IPv4 object level : To indicate if the Virtual Management Interface has consumed the IP address or not. Tested By: 1. busctl introspect xyz.openbmc_project.Settings /xyz/openbmc_project/network/hypervisor 2. busctl introspect xyz.openbmc_project.Settings /xyz/openbmc_project/network/hypervisor/eth0 3. busctl introspect xyz.openbmc_project.Settings /xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0 4. On rainier : similar tests for eth1 (From meta-ibm rev: 988412a2463a58f85f50648f9497a8779203087e) Signed-off-by: Sunitha Harish <sunithaharish04@gmail.com> Change-Id: I734347a8953cd11955eeaacfd67b815810587046 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-07-08Add Hypervisor Virtual Management D-Bus interface objectsSunitha Harish3-0/+94
This commit adds a new yaml file for holding the Hypervisor's Virtual Management Interface's network objects. This models two ethernet interfaces to the hypervisor and its static IPv4 attributes. Tested by: busctl tree xyz.openbmc_project.Settings (From meta-ibm rev: ae4ab28128052a57f8ddd4c910e27e04f92305d6) Signed-off-by: Sunitha Harish <sunithaharish04@gmail.com> Change-Id: I9a32d943867d26fbf215f248ab944e6f8750f415 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-07-08Update phosphor-powr build for Rainier IBM VPDBrandon Wyman1-1/+2
The phosphor-power updates for Rainier power supply VPD collection introduces ibm-vpd configuration option. Use -Dibm-vpd=true for Rainier builds. See Change-Id: I431ae3ec8a9cb9c80a824029f110d5fd58a7d5d8 (From meta-ibm rev: 2f9e6a3b7be4ad5ff15344a6c63fa7577ccac6bf) Change-Id: I14f9e573cc905fad72ea23c1195cb685f4be8c4c Signed-off-by: Brandon Wyman <bjwyman@gmail.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-07-03fans:monitor:witherspoon: Enable JSON configMatthew Barth2-80/+4
Use the installed `config.json` as the fan monitoring configuration to load at runtime. This replaces the need of the build time YAML `monitor.yaml` configuration. Tested: `monitor.yaml` removed from build image staging location Built/powered on image using the `config.json` file (From meta-ibm rev: 27be42e03193352d7c7ee51784448cb06d1b8e2c) Change-Id: I80c268b26dddd820e7c9c640eab2d39452ab3a29 Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-06-30Package service-config-manager for Rainier and TacomaTom Joseph1-2/+2
(From meta-ibm rev: 2c67f194f16568dac0de6dbf965e823790440639) Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com> Change-Id: Ib34136cd472803d01d398462814b14c0e876d52f Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-06-30fans:monitor:witherspoon: Install config.json fileMatthew Barth3-0/+135
In prep for switching the witherspoon machine over to using a runtime fan monitoring JSON configuration, install the configuration file into the image now. Tested: Verified both `monitor.yaml` and `config.json` in phosphor-fan Built/installed witherspoon image and config.json file present Verified YAML config still used instead of present JSON config (From meta-ibm rev: 36206800a699a1429d30ad32a36e4f960ac6c7b4) Change-Id: I75d72a2731f201d37d38c9d436eff2af522bc6da Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-06-24meta-ibm: drop witherspoon-128Brad Bishop6-20/+0
This system will no longer be supported or maintained. Drop to minimize cruft. (From meta-ibm rev: 7c17e6a1f826cdfbbb39ffa3f237025e56fab52f) Change-Id: Id954a1c91c754a1eb4eb67348c5fb01a115326ed Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-06-24ibm: Put ibm-logging back inMatt Spinler1-2/+2
It was temporarily removed so that the commit that moves the IBM D-Bus interface it uses from ibm-dbus-interfaces to phosphor-dbus-interfaces could go in without getting compile fails. The commit that removed it is bd17cae1d3a44f5fc82c4e037a91c97e092fcf57. (From meta-ibm rev: a26d3db37979aaeab4343db41f5316425e9233e5) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ia4463e27411c1075d36119e6121dc2163335d6e4 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-06-22ibm: Don't use ibm-dbus-ifaces in ibm-loggingMatt Spinler2-4/+4
The IBM D-Bus interfaces moved into phosphor-dbus-interfaces. Also temporarily remove ibm-logging from every image so that ibm-dbus-interfaces won't be pulled in and CI can work. (From meta-ibm rev: bd17cae1d3a44f5fc82c4e037a91c97e092fcf57) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ic8bf9106592c7e7d161d928708554a91d5bb407e Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-06-22Change the ibm-config flag to sync-macManojkiran Eda1-1/+1
- As per the commit merged in phosphor-networkd, the ibm-config flag is now changed to sync-mac. (From meta-ibm rev: 7bd9b4a226207205adf0093b7c64bc69f20ad1dc) Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: Ia02e350ffa3ca42e56f3cac4b0dbc14980fab3b7 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-06-18Enable IBM Config Flag Recipe Support for NetworkdManojkiran Eda1-0/+2
- This commit enables the ibm-config flag for phosphor-networkd service while compiling for IBM machines. - ibm-config compilation flag would enable the configurable Inventory-Interface Mapping JSON for setting the corresponding MAC Address that are obtanined from the Inventory on to the respective ethernet interface(s) during the first boot. (From meta-ibm rev: 4b0db6e07d3207e256f01f2f34d144aa93950224) Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Fixed minor typo in commit message Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Change-Id: I31d284839969ea55f13165f5957c164b9b1f6ce8 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
generated by cgit v1.2.3 (git 2.39.0) at 2024-06-28 08:00:21 +0300