| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Remove fp5280g2-psu-update-tool, we no longer need it.
Signed-off-by: Chicago Duan <duanzhijia01@inspur.com>
Change-Id: I5fa4370e6c5b7905314bd957241e9b924904b148
|
|
the Inspur NF5280M7 is an x86 platform server with an AST2600-based BMC.
Tested: Built nf5280m7 and verified the image-bmc is generated.
Change-Id: Iab86a8682d1fc8f3320590e63613a22a14571fcd
Signed-off-by: Xiaoyu Ma <maxiaoyu@inspur.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>
|
|
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>
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
|
|
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ib35c88eee0dcbcbf180c5540ca3975bcae8833fa
|
|
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ie254145438e5e5f80781af12605b567a5260a376
|
|
Update the association configuration of identify according to
the latest association interface[1].
[1] https://github.com/openbmc/phosphor-dbus-interfaces/commit/9eb460c6cfc2d7c2feb29c86f4beb31d4c3d9250
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I40e5c87e9e2838c42f855d786ccdf3478827e0f4
|
|
Update the associated configuration of fans and chassis according to
the latest associated interface[1].
[1] https://github.com/openbmc/phosphor-dbus-interfaces/commit/d0aa13b446ee1738d53fb1e04341946f5b0b7616
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I1d9979ec379cd1aa12151d382601ba4af6d1cb91
|
|
Update the led-group-config.json and add warning & critical level.
Tested:
~# busctl tree xyz.openbmc_project.LED.GroupManager
`-/xyz
`-/xyz/openbmc_project
`-/xyz/openbmc_project/led
`-/xyz/openbmc_project/led/groups
|-/xyz/openbmc_project/led/groups/bmc_booted
|-/xyz/openbmc_project/led/groups/dimm_fault_critical
|-/xyz/openbmc_project/led/groups/dimm_fault_warning
|-/xyz/openbmc_project/led/groups/enclosure_identify
|-/xyz/openbmc_project/led/groups/enclosure_identify_blink
|-/xyz/openbmc_project/led/groups/fan_fault_critical
|-/xyz/openbmc_project/led/groups/fan_fault_warning
|-/xyz/openbmc_project/led/groups/lamp_test
|-/xyz/openbmc_project/led/groups/power_on
|-/xyz/openbmc_project/led/groups/powersupply_fault_critical
|-/xyz/openbmc_project/led/groups/powersupply_fault_warning
|-/xyz/openbmc_project/led/groups/system_fault_critical
|-/xyz/openbmc_project/led/groups/system_fault_warning
|-/xyz/openbmc_project/led/groups/system_hot_fault_critical
`-/xyz/openbmc_project/led/groups/system_hot_fault_warning
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I0b63e830ac1cb6b94c4f57c28fa8e281e0edf29e
|
|
Per association document[1], add the association between PowerSupply and
Chassis.
[1] https://github.com/openbmc/phosphor-dbus-interfaces/commit/11efbb3c856af9d760e2d27ff276090d7b3510d5
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I6b98879f57f2f43ab5d07270ab59c444e2147235
|
|
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
|
|
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
|
|
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>
|
|
Since phosphor-power-psu-monitor is only applicable to IBM's p10
system and is disabled by default, it will not be applicable to
Inspur's fp5280g2 system, remove it.
refer to: https://gerrit.openbmc.org/c/openbmc/openbmc/+/53572
Tested: Successfully build image-bmc on fp5280g2
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I2682324dc5bf04078d2b16c0796e5f86f49d3f31
|
|
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
|
|
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
|
|
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
|
|
* Deprecate N-1 release (hardknott).
* Enable N+1 release (kirkstone).
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
|
|
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
|
|
The size of the zoneinfo file generated by adding tzdate is 1004B,
The size of the zoneinfo file generated by adding tzdate-core is
572B,and the time zone related functions can still be used normally,
but it can save 432B of space.
Signed-off-by: Albert Zhang <zhanghaodi@inspur.com>
Change-Id: Idd5211efc86274d12226cff65b847ffc04fe1cf5
|
|
Per [1], Yocto is going to start requiring both branch names and
`protocol=https` in GitHub SRC_URI variables. Ran the upstream tool to
automatically fix our URIs.
1. https://git.yoctoproject.org/poky/tree/documentation/migration-guides/migration-3.5.rst#n10
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5f9619f7ff707050b469ae74c8aa16846568c5e4
|
|
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>
|
|
Chassis dependencies (obmc-control-chassis, obmc-op-control-power,
obmc-host-failure-reboots) have been deprecated, use
x86-power-control instead.
Flash dependencies (obmc-flash-bmc, obmc-mgr-download,
obmc-control-bmc) have been deprecated, use phosphor-software-manager
instead.
Tested: built on5263m5 successuflly.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ib676ddccae91607fbf8eabdf3a22d69624a9da25
|
|
This layer has nothing in it. The current direction is for anything
architecture specific to end up in meta-phosphor. Remove this "layer"
so that it doesn't keep getting copied into new machines.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ied03175589840490bcd1eda8c704c73e224ba9a9
|
|
`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>
|
|
Add the fru YAML configuration of Power Supply for fp5280g2.
Tested:
ipmitool -I lanplus -H ${IP} -U root -P 0penBmc -C 17 fru list
FRU Device Description : Builtin FRU Device (ID 0)
Board Mfg Date : Mon Jan 1 08:00:00 1996
Board Serial : 000000000000
Board Part Number : 0000000
FRU Device Description : cpu0 (ID 1)
Board Mfg Date : Mon Jan 1 08:00:00 1996
Board Mfg : IBM
Board Product : PROCESSOR MODULE
Board Serial : YA1934426664
Board Part Number : 02CY296
FRU Device Description : dimm2 (ID 5)
Product Manufacturer : Samsung Electronics
Product Name : DDR4-2666 16GiB 64-bit ECC RDIMM
Product Part Number : M393A2K43BB1-CTD
Product Serial : 367f4c9d
FRU Device Description : powersupply0 (ID 20)
Product Name : powersupply0
Product Part Number : PS-2801-12L
Product Serial : 6K12A0118446MM
FRU Device Description : powersupply1 (ID 21)
Product Name : powersupply1
Product Part Number : PS-2801-12L
Product Serial : 6K12A0118362NS
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I04b45f5839f991f98b3f628db2246d4dced804c8
|
|
Generally we will set the fruID of the board to 0.
Tested:
ipmitool -I lanplus -H ${IP} -U root -P 0penBmc -C 17 fru list
FRU Device Description : Builtin FRU Device (ID 0)
Board Mfg Date : Mon Jan 1 08:00:00 1996
Board Serial : 000000000000
Board Part Number : 0000000
FRU Device Description : cpu0 (ID 1)
Board Mfg Date : Mon Jan 1 08:00:00 1996
Board Mfg : IBM
Board Product : PROCESSOR MODULE
Board Serial : YA1934426664
Board Part Number : 02CY296
...
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I3912636105310855e59810cbc1fab4a4cad53a1b
|
|
Enable tzdata by default.
Tested: built image successufully and verified that
`/usr/share/zoneinfo` already exists.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I9f244cd50c5898c8f72247414e18b0c72c5a0c1a
|
|
Enable phosphor-sel-logger by default.
Tested: built image successufully and saw that the sel-logger
has been started.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I50062f8225d95f1092512c0956bdc1bdeb83949e
|
|
Enable service-config-manager by default.
Tested: built image successufully and saw that
the phosphor-srvcfg-manager has been started.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Id5f66cea66d35f373b8157a3b0a2732edd018b40
|
|
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
|
|
This commit changes the uboot to u-boot-aspeed-sdk to
fit the 64M layout
Tested: tested on the real machine, the image booted sucessfully
Signed-off-by: John Wang <wangzhiqiang02@inspur.com>
Change-Id: If6087abe489f157ac3f75e7428dbfe329caa0957
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ia05891430c6c97a89b7bc8ba4558ae496866bf7d
|
|
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>
|
|
`install -d ${D}${sysconfdir}/default` has been configured
in the libmctp_git.bb file, remove it.
Tested:
1. Successfully build libmctp and image-bmc
2. Saw the `/etc/default/mctp` file in image-bmc
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I162d10b4a09ebe87388f4e3e4d9f79aa32a94230
|
|
Since the upstream has renamed the mctp package name (debf2b5),
it will fail when building fp5280g2.
Synchronously update the mctp package name of fp5280g2.
Tested: built fp5280g2 image successfully.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ifdf4bc7955d182617532537f1f5fc59931d27eca
|
|
We're about to introduce a package for mctp utilities, called 'mctp'.
However, the libmctp package already uses that name.
This change renames 'mctp' to the upstream name of 'libmctp'.
Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
Change-Id: Ia49a40c822e920d3bc36584cbc2c97b83828cfdd
|
|
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I2b967fb31d9930074df17c108d06cfed489d1cf7
|
|
Add xyz.openbmc_project.Inventory.Item.CpuCore interfaces
to all processor cores.
Tested:
busctl introspect xyz.openbmc_project.Inventory.Manager /xyz/openbmc_project/inventory/system/chassis/motherboard/cpu0/core2
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
org.freedesktop.DBus.Introspectable interface - - -
.Introspect method - s -
org.freedesktop.DBus.Peer interface - - -
.GetMachineId method - s -
.Ping method - - -
org.freedesktop.DBus.Properties interface - - -
.Get method ss v -
.GetAll method s a{sv} -
.Set method ssv - -
.PropertiesChanged signal sa{sv}as - -
xyz.openbmc_project.Association.Definitions interface - - -
.Associations property a(sss) 1 "sensors" "inventory" "/xyz/openbmc_p… emits-change writable
xyz.openbmc_project.Inventory.Item interface - - -
.Present property b true emits-change writable
.PrettyName property s "" emits-change writable
xyz.openbmc_project.Inventory.Item.CpuCore interface - - -
xyz.openbmc_project.State.Decorator.OperationalStatus interface - - -
.Functional property b true emits-change writable
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ia7acfbf8b0a90f7b97cb7df090a7469815a6434d
|
|
Upstream bbclasses changed to typically use the `:${PN}` override
syntax, including the SYSTEMD_ variables. Change our systemd.bbclass
to do the same for consistency and perform a tree-wide variable
replacement.
Spot checked by building bletchley and witherspoon and checking
some of the SYSTEMD_LINK directives on installed packages under qemu.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20a9dd809bff8af8759488734f80486c7228c6eb
|
|
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ia66f5b4a95f54f7e537d0f0fba1ac70009002de5
|
|
We've typically kept these LAYERSERIES_COMPAT to 2 releases: the current
and the upcoming. Remove 'gatesgarth' is it is now 2 releases back.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5e812a94fed1738898af75c0fdee81996a5bbf20
|
