Age | Commit message (Collapse) | Author | Files | Lines |
|
The recipe previously had a hard coded removal of `/lib` which will no
longer exist under usrmerge. I think the purpose of this was to delete
the systemd units, but leave the library. Therefore I've adjusted the
removal to be systemd_unitdir instead of `/lib`.
This results in the following package structure:
```
$ find tmp/work/armv7a-openbmc-linux-gnueabi/google-ipmi-sys/0.1+gitAUTOINC+59445f5e21-r1/packages-split/google-ipmi-sys -type f
tmp/work/armv7a-openbmc-linux-gnueabi/google-ipmi-sys/0.1+gitAUTOINC+59445f5e21-r1/packages-split/google-ipmi-sys/usr/lib/systemd/system-preset/98-google-ipmi-sys.preset
tmp/work/armv7a-openbmc-linux-gnueabi/google-ipmi-sys/0.1+gitAUTOINC+59445f5e21-r1/packages-split/google-ipmi-sys/usr/lib/ipmid-providers/libgooglesys.so
```
The `98-google-ipmi-sys.preset` file is empty.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I05dd016fcc8dfd8dc33ba90acad100afafb18073
|
|
Use the libhoth recipe in meta-security instead of openbmc one. Set the
source rev override until that bump is submitted and subtree updated.
libhoth source bump in
- https://lore.kernel.org/yocto/20230517172730.3837643-1-jebr@google.com/T/#u
Change-Id: I6099d6351417dcef9eb3b4d297de43a5e229d7dd
Signed-off-by: Willy Tu <wltu@google.com>
|
|
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>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I189baf142cc86d44ebbf615edd3bb0ec1785be8d
|
|
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>
|
|
The latest version of shellcheck is stricter. Fix a few warnings.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I7f94205aef6d348e9c53dca261ea996dd4f84a6a
|
|
Mapper ships with systemd unit and dbus configuration files now, so
remove unnecessary bitbake classes.
Mapper is dbus-activated, so obmc-mapper.target dependencies are
redundant and no longer necessary.
obmc-mapper.target is the last target in obmc-targets, so remove that
recipe and any dependencies on it.
Change-Id: I59ff8dcd480b4449d0ef59422ba80c12848dade9
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
|
|
The nic-ethtool option was removed from phosphor-network, so we also
need to remove the PACKAGECONFIG option to build the phosphor-network
bump.
Tested:
Confirmed that the latest phosphor-network builds successfully.
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
Change-Id: Id1e12f3f2af2450500ec6c0b2acef284cb69d0a7
|
|
This enables timesync support for the gbmc distro.
Change-Id: Idb653e6b98a347b5d8c3a0b3a16c6a4abbe268ac
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
obmc-host-ctl is defined as a MACHINE, DISTRO, and IMAGE feature.
The IMAGE feature pulls in a virtual provider only if the COMBINED
feature (MACHINE + DISTRO) is enabled. This is only done on openpower
machines. There are a lot of other places where machines are half-way
disabling this feature and/or changing variables which have zero effect
anyhow. Clean up almost all references to `obmc-host-ctl`.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I090d782bb6a34dc4e3c43df97e8ccf6e1812fed5
|
|
All of these abstractions have exactly one implementation. Remove the
indirection to improve at a glance comprehension.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I5d701aff6d0876fa3b2d16c841cbdcb0433b221f
|
|
Josh Lehan(1):
Caching services and values for fast performance
Harvey Wu(1):
Update to c++20, meson >= 0.57.0
Signed-off-by: Harvey.Wu <Harvey.Wu@quantatw.com>
Change-Id: I8ec80185c228bf50e0c373214ec607810800642b
|
|
Added do_install in base recipe for phosphor-health-monitor to
copy the json file from WORKDIR to target for monitoring the CPU
and Memory usage of BMC. Therefore, this can be removed in each
bbappend files.
Tested: Tested in Facebook YosemiteV2 platform.
Signed-off-by: Jayashree Dhanapal <jayashree-d@hcl.com>
Change-Id: I78eed7efb3e0be81a952c4bc3c3ae64579a48f7d
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I65febeeec11e6e5b40ee728f42cfbe77023dae1e
|
|
We also need to move the conf-notes.txt files.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ic44e015c0216b526de4fec277ad42f162bca1f33
|
|
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
|
|
phosphor-defaults.inc now automatically inherits extrausers and
configures the default root/0penBmc account, so individual platforms no
longer need to specify either explicitly.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ic2b725f0eaadfafef67069449497e57438fa0fba
|
|
For the moment, phosphor-webui is deprecated and unmaintained. The
replacement for it is webui-vue, which already has feature parity, and
many more features than its predecessor. Several calls have been made
asking if there is anyone still using phosphor-webui and would like to
maintain it into the future, but no such volunteer has stepped up.
Moving to webui-vue is the recommended option these days, and this
patchset is done under the assumption that these platforms would
actually like to move off the deprecated UI, and just don't have patches
to that effect. For the machine maintainers reading this, if you would
like to stay on phosphor-webui, please start that discussion here about
who would like to maintain it.
This commit ports the last few platforms over to webui-vue.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I9c74442b850aceca130545f37d5bc694a4f4424d
|
|
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>
|
|
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
|
|
No systems use content from meta-webserver (nginx, apache, etc.), so
remove the clutter from our bblayers.conf.samples.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I89ab5ac8c19cd8aa486a2f42d24dcf68688e2408
|
|
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
|
|
phosphor-dbus-monitor still uses autoconf and has a hard dependency on
phosphor-snmp, causing phosphor-snmp to be brought in on systems that
have no interest in using SNMP. The vast majority of systems do not
supply any config for phosphor-dbus-monitor, so the usage of it does not
seem wide enough to enable the IMAGE_FEATURE by default.
- Remove 'obmc-dbus-monitor' from IMAGE_FEATURE by default.
- Clean up all systems that manually remove the dbus-monitor feature or
package.
- Explicitly add the 'obmc-dbus-monitor' to the following systems:
- meta-ibm: all
- meta-inspur: fp5280g2
- meta-quanta: s6q
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iad6c4104466e21d1b9843dac964a634019eb6935
|
|
We want it to be possible to order units prior to the powercycle event
if state needs to be persisted prior to a powercycle.
We can also remove the time_delay functionality as this is now provided
globally by the gbmc-psu-hardreset.target.
Change-Id: I15b33e120be0246dd821d0dfe9d61b5aae7d1492
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
William A. Kennington III (1):
systemd: Handle PSU delay globally
Change-Id: Ia80f0c4f230cc08e4344c2b53acdb6ffb1d2dbef
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
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
|
|
New systems should be using the 'use-json' model by default, but it
currently requires a bbappend in order to enable it. Automatically
detect based on the PREFERRED_PROVIDER of virtual/...-config-native if
the intended use is JSON or YAML.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ie674d1b901395b4fd41838b6e978ca1ff00b0277
|
|
1. Fix the sytle of systemd-conf.bbappend to wrap with 80 characters.
2. Add usb0 network interface.
3. Disable ipv4 link-local address to avoid routing problems.
Tested:
Set the host's network interface to a link-local address and
successfully communicate with the BMC via usb0.
Signed-off-by: Jerry Wan <jerry.wan@quantatw.com>
Change-Id: I9e6a9946a2beb8cf85872abe1919e92052fe46cc
|
|
The phosphor-watchdog_%.bbappend has a syntax error of colon.
Tested:
built image successfully and solved the warning message.
Signed-off-by: Joseph Fu <joseph.fu@quantatw.com>
Change-Id: If8bd002e6f140c145c56b7bd0964ad415158d619
|
|
Add heartbeat LED and identification LED for S6Q.
Tested:
The LEDs work properly according to their function.
Signed-off-by: Jerry Wan <jerry.wan@quantatw.com>
Change-Id: I3abde7552b7ebd415ae77e21e51c699c5b9f5474
|
|
Add inventory yaml and enable SEL option to trigger an alarm.
Tested:
Using settable temperature of ExternalSensor to trigger UCT/LCT signel.The result is verified on S6Q board.
Signed-off-by: Joseph Fu <joseph.fu@quantatw.com>
Change-Id: I72f3cc553e78864524761e541bdd6f56469ce290
|
|
* Deprecate N-1 release (hardknott).
* Enable N+1 release (kirkstone).
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
|
|
Noticed that the " were right next to = sign with no spaces. Added
a space between =" in the bbappend file.
Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: I957610d65d1465f268b3b93b4ff565d36020f09f
|
|
Commit 605c37cb989a95c02633fcb93efb45102781b4bb switched the tree to use
'package_ipk' instead of 'package_rpm'. Since then a few other systems
have gone in which used an old package setting. Sync them to use IPK.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iecd2f65871038d6139c87f910c7c7fb19a115067
|
|
Add configuration to store sensor.
Add CPU temperatur sensor by using virtual sensor to get maximum value between DTS_CPU and Die_CPU.
Tested:
using 'ipmitool sdr type' command and Redfish client command to verify on S6Q board.
Signed-off-by: Joseph Fu <joseph.fu@quantatw.com>
Change-Id: I324230922e03f60c080858150b476c3f50fb62d6
|
|
Add service files to enable ipmitool watchdog command.
Tested:
1.setting watchdog action hard reset
~# ipmitool raw 0x06 0x24 0x01 0x01 0x01 0x02 0x64 0x00
starting reset
~# ipmitool raw 0x06 0x22
2.power off
~# ipmitool raw 0x06 0x24 0x01 0x02 0x01 0x02 0x64 0x00
~# ipmitool raw 0x06 0x22
3.power cycle
~# ipmitool raw 0x06 0x24 0x01 0x02 0x01 0x02 0x64 0x00
~# ipmitool raw 0x06 0x22
Use these commands to verify the result matches service settings.
Signed-off-by: Joseph Fu <joseph.fu@quantatw.com>
Change-Id: I738d0d86b6a9729d488f22e841e207aaab219796
|
|
Enable the BIOS boot type. Add 'boot_type' option for phosphor-settings-manager to support both EFI and Legacy boot.
Tested:
~# ipmitool raw 0x00 0x09 0x05 0x00 0x00
01 05 60 00 00 00 00
~# ipmitool chassis bootparam get 5
Boot parameter version: 1
Boot parameter 5 is valid/unlocked
Boot parameter data: 6000000000
Boot Flags :
BIOS EFI boot
~# ipmitool raw 0x00 0x08 0x05 0x80 0x00 0x00 0x00 0x00
~# ipmitool raw 0x00 0x09 0x05 0x00 0x00
01 05 80 00 00 00 00
~# ipmitool chassis bootparam get 5
Boot parameter version: 1
Boot parameter 5 is valid/unlocked
Boot parameter data: 8000000000
Boot Flags :
BIOS PC Compatible (legacy) boot
Signed-off-by: Joseph Fu <joseph.fu@quantatw.com>
Change-Id: I3ff030dd65fad1a2492c20a6622c6dce68832b45
|
|
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
|
|
As mentioned by I970e06ca6f9d0a9792af122eb25da1bb9a06f058, append and
remove directives with '+=' are no longer valid Yocto syntax and raise a
warning.
See https://git.yoctoproject.org/poky/tree/documentation/migration-guides/migration-3.5.rst#n40
One interesting caveat has to do with the difference between "append"
and "+=".
foo:append = "a"
foo:append = "b"
Results in `foo = "ab"`, but
foo += "a"
foo += "b"
Results in `foo = "a b"`. When `:append +=` is used it has behavior
like the `+=` operator. Therefore, in some cases we need to insert
additional whitespace after the `:append = "` to ensure concatenation
behaves as expected. I've manually reviewed the results to ensure there
is no ill side-effects from an additional space potentially being added.
Fix up the entire tree with the following one-liner (and similar for
`remove`):
git ls-files -- ':!:poky/**' ':!:meta-security/**' \
':!:meta-raspberrypi/**' ':!:meta-openembedded/**' \
| grep "\.bb" | xargs grep -l ":append.*+=" \
| xargs sed -i 's/:append\(.*\)+=\([^"]*\)" */:append\1=\2" /'
or ...
| xargs grep -l ":remove.*+=" \
| xargs sed -i "s/:remove\(.*\)+=/:remove\1=/"
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iea6235e7c76e252f4d473652957c2925f6b8845a
|
|
e.g.
install: cannot stat '/home/peter/openbmc/build/quanta-q71l/tmp/work/armv5e-openbmc-linux-gnueabi/quanta-powerctrl/1.0-r0init_once.sh': No such file or directory
Signed-off-by: Peter Foley <pefoley@google.com>
Change-Id: I40ff36dd1b640c5410c79fbd91642f658d9cc2b7
|
|
e.g.
ERROR: Nothing RPROVIDES 'virtual-obmc-system-mgmt' (but /home/peter/openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb RDEPENDS on or otherwise requires it)
Signed-off-by: Peter Foley <pefoley@google.com>
Change-Id: I40f1dc3537073dbf02a702c9f1f64ada36384179
|
|
e.g.
ERROR: Nothing RPROVIDES 'virtual-obmc-system-mgmt' (but /home/peter/openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb RDEPENDS on or otherwise requires it)
Signed-off-by: Peter Foley <pefoley@google.com>
Change-Id: I6da15718cbe2741647fbc5531e8fa989909ca46a
|
|
e.g.
WARNING: /home/peter/openbmc/meta-quanta/meta-q71l/recipes-phosphor/ipmi/q71l-ipmi-inventory-map-native.bb: QA Issue: q71l-ipmi-inventory-map-native: native/nativesdk class is not inherited last, this can result in unexpected behaviour. Classes inherited after native/nativesdk: phosphor-ipmi-fru.bbclass [native-last]
WARNING: /home/peter/openbmc/meta-quanta/meta-q71l/recipes-phosphor/ipmi/q71l-ipmi-sensor-map-native.bb: QA Issue: q71l-ipmi-sensor-map-native: native/nativesdk class is not inherited last, this can result in unexpected behaviour. Classes inherited after native/nativesdk: phosphor-ipmi-host.bbclass [native-last]
Signed-off-by: Peter Foley <pefoley@google.com>
Change-Id: I001b0b0d38067f4533748f5bf0f49de03f238ce9
|
|
e.g.
WARNING: /home/peter/openbmc/meta-quanta/meta-f0b/recipes-phosphor/ipmi/f0b-ipmi-inventory-map-native.bb: QA Issue: f0b-ipmi-inventory-map-native: native/nativesdk class is not inherited last, this can result in unexpected behaviour. Classes inherited after native/nativesdk: phosphor-ipmi-fru.bbclass [native-last]
WARNING: /home/peter/openbmc/meta-quanta/meta-f0b/recipes-phosphor/ipmi/f0b-ipmi-fru-read-inventory-native.bb: QA Issue: f0b-ipmi-fru-read-inventory-native: native/nativesdk class is not inherited last, this can result in unexpected behaviour. Classes inherited after native/nativesdk: phosphor-ipmi-host.bbclass [native-last]
Signed-off-by: Peter Foley <pefoley@google.com>
Change-Id: I3bc1e1cc2e581b0b191e191e32cfdbd6e2e278b7
|
|
Set the max size to 512 since 0x300 is used for something else.
Change-Id: Ic7772247cb3cbcff4a27a12a4f85be97fd6b0b4d
Signed-off-by: Willy Tu <wltu@google.com>
|
|
This settings is according to IPMI SPEC chassis capabilities to provide intrusion sensor.
Adding chassis intrusion sensor monitor to implement 'ChassisIntrusionEnabled' property functionally.
Tested:
get chassis capabilities, first 01 is meant to enable intrusion sensor
~# ipmitool raw 0x00 0x00
01 20 20 20 20 20
check the intrusion sensor Status
~# systemctl status xyz.openbmc_project.intrusionsensor.service
● xyz.openbmc_project.intrusionsensor.service - Intrusion Sensor
Loaded: loaded (/lib/systemd/system/xyz.openbmc_project.intrusionsensor.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-01-10 01:53:48 UTC; 10min ago
Main PID: 478 (intrusionsensor)
CGroup: /system.slice/xyz.openbmc_project.intrusionsensor.service
└─478 intrusionsensor
then, set no provided any chassis capabilities function.
~# ipmitool raw 0x00 0x05 0x00 0x20 0x20 0x20 0x20 0x20
check chassis capabilities status.
~# ipmitool raw 0x00 0x00
00 20 20 20 20 20
now, intrusion sensor is not provided.
~# systemctl status xyz.openbmc_project.intrusionsensor.service
○ xyz.openbmc_project.intrusionsensor.service - Intrusion Sensor
Loaded: loaded (/lib/systemd/system/xyz.openbmc_project.intrusionsensor.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Mon 2022-01-10 02:05:44 UTC; 5s ago
Process: 478 ExecStart=/usr/bin/env intrusionsensor (code=killed, signal=TERM)
Main PID: 478 (code=killed, signal=TERM)
Signed-off-by: Joseph Fu <joseph.fu@quantatw.com>
Change-Id: Ib3e3811f9ae9ab79dab52921fb0e6e065d44c444
|
|
phosphor-ipmi-ipmb: Enable ME communication
Tested:
root@s6q-dev:~# busctl tree xyz.openbmc_project.Ipmi.Channel.Ipmb
`-/xyz
`-/xyz/openbmc_project
`-/xyz/openbmc_project/Ipmi
`-/xyz/openbmc_project/Ipmi/Channel
`-/xyz/openbmc_project/Ipmi/Channel/Ipmb
Use 'busctl call xyz.openbmc_project.Ipmi.Channel.Ipmb \
/xyz/openbmc_project/Ipmi/Channel/Ipmb org.openbmc.Ipmb \
sendRequest yyyyay 1 6 0 0x1 0'
to get device id
Signed-off-by: Tim Chao <Tim.Chao@quantatw.com>
Change-Id: I01af849bbe3c290dda88969267f092c11bf9e8fc
|
|
The power restore policy can be set to "AlwaysOn","Restore" or "None".
Set power policy to Restore by default.
Tested:
~# ipmitool chassis status
Power Restore Policy : previous
Signed-off-by: Joseph Fu <joseph.fu@quantatw.com>
Change-Id: I48baef59461233276b2402a3a61b89a5e3eaa3a4
|
|
This commit enables sync-mac and nic-ethtool in the phosphor-network.
The "sync-mac" function can initialize the mac address on first boot, if it can find the object in the inventory.
When phosphor-network triggers systemd to set the mac address, it must be set together with the interface enslaved by bond.
And "nic-ethtool" provides the necessary data through network interface analysis.
Tested:
Check the network object if it worked.
~# busctl introspect xyz.openbmc_project.Network /xyz/openbmc_project/network/bond0
Signed-off-by: Jerry Wan <jerry.wan@quantatw.com>
Change-Id: I63d80b4491f3aa42cae401658a189acaaddb592f
|