Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
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
|
|
The node manager is maintained in
https://github.com/Intel-BMC/node-manager and it is not buildable with
latest OpenBMC.
The OpenBMC guideline[1] and the repotest[2] does not accept pathces in
machine layers, so the patches to node-manager are not accepted.
Remove the recipe for now, otherwise the build fails.
[1]:
https://github.com/openbmc/docs/blob/master/meta-layer-guidelines.md
[2]:
https://github.com/openbmc/openbmc-build-scripts/blob/master/build-setup.sh#L141
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I735f5b4d9b1cfa0ff4c0e47d349f99e847c0a7bd
|
|
Remove ipmb patch that is upstreamed
Fix uart patch conflict
Tested: Build ok
Signed-off-by: Lotus Xu <xuxiaohan@bytedance.com>
Change-Id: I3749aafb5957e1fda4d31ef44fb2b6b956baa94a
|
|
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>
|
|
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
|
|
Fix the environment variables of the destination directory
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: Iffd1ca218da9d9aeaff560ecf96c8b8267702994
|
|
Config additional device Support and manufacturer ID
Tested: ipmitool mc info and ipmitool fru
Signed-off-by: Henry Tian <tianxiaofeng@bytedance.com>
Change-Id: I08488b2c9f19e086eee8082242a9efdb96957e61
|
|
It adjusts some sensors' number and adds the total power sensor.
Tested: Verify the "Total_Power" is shwon in ipmi sensor list.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I334fe602f949bbd95cb59bcdfba390ea5147df33
|
|
Add virtual sensor's associations so that the sensors could be shown in
Redfish and WebUI.
Tested: Verify the Total_Power is shown in Redfish as below
$ curl -k -H "X-Auth-Token: $token" https://${bmc}/redfish/v1/Chassis/G220A/Sensors/Total_Power
{
"@odata.id": "/redfish/v1/Chassis/G220A/Sensors/Total_Power",
"@odata.type": "#Sensor.v1_0_0.Sensor",
"Id": "Total_Power",
"Name": "Total Power",
"Reading": 514.0,
"ReadingRangeMax": null,
"ReadingRangeMin": null,
"ReadingType": "Power",
"ReadingUnits": "W",
"Status": {
"Health": "OK",
"State": "Enabled"
}
}
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I0c9c84917364cad701f00fc3041d427a6e8750bc
|
|
Add below virtual sensors based on VR sensors:
P0_DIMM_VR_Pwr = CPU0_DIMM_VR_0_Input_Power + CPU0_DIMM_VR_1_Input_Power
P1_DIMM_VR_Pwr = CPU1_DIMM_VR_0_Output_Voltage + CPU1_DIMM_VR_1_Output_Voltage
CPU0_VR_Pwr = CPU0_VR_0_Input_Power + CPU0_VR_1_Input_Power + CPU0_VR_2_Input_Power
CPU1_VR_Pwr = CPU1_VR_0_Input_Power + CPU1_VR_1_Input_Power + CPU1_VR_2_Input_Power
CPU0_VR_Temp = max(CPU0_VR_0_Temperature, CPU0_VR_1_Temperature, CPU0_VR_2_Temperature)
CPU1_VR_Temp = max(CPU1_VR_0_Temperature , CPU1_VR_1_Temperature, CPU1_VR_2_Temperature)
P0_DIMM_VR_Temp = max(CPU0_DIMM_VR_0_Temperature, CPU0_DIMM_VR_1_Temperature)
P1_DIMM_VR_Temp = max(CPU1_DIMM_VR_0_Temperature, CPU1_DIMM_VR_1_Temperature)
Tested: Verify the above sensors appear on DBus and the values are
expected.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I9412e7da1a147b64cb43a5f9981042623cfb6423
|
|
Add phosphor-virtual-sensor pakcage and configure it to enable
"total_power" sensor that is the sum of PSU0/1's input power.
Tested: Verify the Total_Power sensor is on DBus and the value is the
sum or PSU0 and PSU1's input power.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: Ie8f61800299bef01a8bb74256c24d1f0a90df258
|
|
Use nonarch_base_libdir instead of base_libdir, because the files are
always in /lib/udev/rules.d/. On ppc64le base_libdir is lib64, and the
files end up in the wrong spot.
Signed-off-by: Anton Blanchard <anton@ozlabs.org>
Change-Id: I3c24dae293f4166f1ed1826d09d4bde7cd7d0357
|
|
The `PREFERRED_PROVIDER` still uses `_` instead of `:`, fix it.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I34f27870ff35de8b14a8a546d42ab4a1fb5f30d1
|
|
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I5aa8948c3eb5800b5b371403d3745d4c794d4eec
|
|
convert-overrides.py meta-bytedance
git grep -l _g220a -- meta-bytedance | grep ".bb" | \
xargs sed -i 's/_g220a/:g220a/'
git grep -l _u-boot -- meta-bytedance | xargs sed -i \
's/_u-boot/:u-boot/'
Tested:
$ git grep "_[a-z0-9_/-]*[ :]" -- meta-bytedance | grep ".bb"
meta-bytedance/meta-g220a/recipes-phosphor/chassis/x86-power-control_%.bbappend:do_install:append() {
meta-bytedance/meta-g220a/recipes-phosphor/configuration/entity-manager_%.bbappend:do_install:append() {
meta-bytedance/meta-g220a/recipes-phosphor/console/obmc-console_%.bbappend:do_install:append() {
meta-bytedance/meta-g220a/recipes-phosphor/ipmi/phosphor-ipmi-ipmb_%.bbappend:do_install:append(){
meta-bytedance/meta-g220a/recipes-phosphor/ipmi/phosphor-ipmi-kcs_%.bbappend:do_install:append() {
meta-bytedance/recipes-core/systemd/systemd-conf_%.bbappend:do_install:append() {
meta-bytedance/recipes-core/systemd/systemd_%.bbappend:do_install:append () {
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I26fb4c52012ee407ceb26c5a4120bf7b0b7a165a
|
|
Add `honister` to LAYERSERIES_COMPAT for the next Yocto release.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I13918bf18f29e1d4ccb6e4421a94a005abb25c9e
|
|
Tested: Run ipmitool sensor list and verify the output is as
expected.
Signed-off-by: Lotus Xu <xuxiaohan@bytedance.com>
Change-Id: Ibd81144adf8cb1477a8963cc3b8331b72c1a928b
|
|
ipmb may not be ready for communication when me-time-sync start.
Add some retry so that the time could be synced.
Tested: Test 10 times, me-time-sync can work well
Signed-off-by: Lotus Xu <xuxiaohan@bytedance.com>
Change-Id: I93343d2ac17fc13b1d094bf05f424d9cb54cfa3f
|
|
The Total_Power sensor is not available on g220a system, add patch to
remove it.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: Ibc70bec3d56b13740d3f17a666a8d0b0fa7c8429
|
|
Tested: Verify the CPU_Power and Memory_Power sensors are OK.
Signed-off-by: Lotus Xu <xuxiaohan@bytedance.com>
Change-Id: I13fde13adc4062d5586167e411c129a986e3ad76
|
|
Signed-off-by: Lotus Xu <xuxiaohan@bytedance.com>
Change-Id: I78521f447c361c1bb3c4746a2d28016d123d2029
|
|
The upstream has defined the 64MiB layout, use the upstream one.
Tested: Verify g220a's image boots fine in QEMU.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: Id69df5796c11f1d86bc1340fdb7127f0eb3f3e18
|
|
Use the new u-boot-aspeed-sdk as the uboot.
Tested: Verify the image boots u-boot in g220a QEMU, and boots the
OpenBMC if bootcmd is modified to fit the image.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I93c3a083a81f09d37627749c8d0692ae9a75466a
|
|
This is apparently not actually working anymore and is removed in the
next poky update.
Change-Id: Ia1c6a258d124a4a30a14fc42e8e0bba95e64faeb
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
Add the power related config to enable power on.
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Signed-off-by: Lotus Xu <xuxiaohan@bytedance.com>
Change-Id: I3912fc603cf249bb2a1f48f69b7e14d458a6e0f1
|
|
Tested:now we can see ipmi-kcs4 and eth1
Signed-off-by: Lotus Xu <xuxiaohan@bytedance.com>
Change-Id: I85166e66c0b37a7b5b3f5b8387b6056afc66e1cd
|
|
Latest upstream yocto has moved on to the 3.3 hardknott release
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ieae36798d66d21c2c642931f06407d3bb2acf163
|
|
This layer provides libseccomp.
Signed-off-by: Anton D. Kachalov <gmouse@google.com>
Change-Id: I84513d56f2ed75fab49043196b98ef8b858e394f
|
|
Although hostlogger does not read the serial port, its systemd unit
depends on the obmc-console and waits for the obmc-console of the
specified serial port instance, which is vuart by default, ttyS2
on the g220a
Tested: journalctl |grep VUART, no realted log
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: I4136e6f376e71d3590ab2a787784446bcc7647df
|
|
This patch is for phosphor-ipmi-host
(From meta-bytedance rev: 588f458cf553f84e1cc2cc9e7dca07ed6ebd3d86)
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: I41a0c113ec6853f8a49ac1664c66595419b570e8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
read a byte at one time eg:
for the first byte
i2cset -y 1 0x50 0x00 0x00
i2cget -y 1 0x50
(From meta-bytedance rev: 6389a4f03a518e49241d13843cf005f4a85d7cc8)
Tested: Verify the eeprom mac addr can be read
use `fw_printenv`,`ip a` can read device
mac addr
Signed-off-by: Lotus Xu <xuxiaohan@bytedance.com>
Change-Id: I5fbf28e5bb3bb2ccc2a074388f4166e35da48afc
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Do not enter the failmode if a temperature sensor's value is
NAN, It's useful for debug. We always want the pid-controler to
run, when debugging.
(From meta-bytedance rev: ae79ff9e289c85498e656172e99d44b11d969109)
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: I957528b2e2f336bdf3abbd78ec105bdc249e3716
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Tested: Login in the webui, it works.
(From meta-bytedance rev: 69a07b424834dc1f78046177c1314988812e27e9)
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: I2c89ce0cddfb0f68b788b855b67cbc56e321c3f4
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Tested: Run ipmitool fru print 0 and ipmitool sensor list,
the output is as expected.
(From meta-bytedance rev: 9e8a65aa85782b09f21fda3df0f502f6037e0f02)
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: I0ab25c386a418d039f05a4c4e96553152322194f
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
g220a BMC needs to get time from ME on start.
Add me-time-sync package that fetches time from ME via ipmb, and set the
time to BMC via `date` command.
Tested: Verify the time is set on BMC boots
(From meta-bytedance rev: c8640d007d25676261acc04317e5612269bd3ed5)
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I0e7f1d249cf743e3477843a67a6d2e6250c43aa6
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Tested : we can see /dev/ipmb-4 on g220a
Use `busctl call xyz.openbmc_project.Ipmi.Channel.Ipmb \
"/xyz/openbmc_project/Ipmi/Channel/Ipmb" org.openbmc.Ipmb \
sendRequest yyyyay 0x01 0x0a 0x00 0x48 0`
to get ME time correctly
(From meta-bytedance rev: 58c6841aee1bd93c1070401ce7ca589367b8e6d0)
Signed-off-by: Lotus Xu <xuxiaohan@bytrdance.com>
Change-Id: Ic45173405ec9cd1806b5caa7a5081b6ed0d8fc3e
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Tested: boot the host, and see cpu/dimm sensors under
/sys/class/hwmon
(From meta-bytedance rev: 76f1849431b2dcafbe96ca4ece33841ba66e0fd9)
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: I3125bd6f42c8de0d85a2fb49946e8e219f46ab54
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Tested: ssh -p 2200, SOL works well.
(From meta-bytedance rev: 1f40f6da4fc2e00fc06128ae6ba7dd1f045c8a84)
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: I2abd1e11c5158da887ac382bb2a98f94d85a4749
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-bytedance rev: 5b738226c37418f6c98935bb747db509e63a5466)
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: Ia0f32176b25d14ee35481dc413d463edb50eb98c
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-bytedance rev: 5729e59f3a7f1202deccb8d90738a32f8821c215)
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: I115935112219927a9ac77720adeae646a62aec12
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-bytedance rev: aec4880792267c1d8a00ba8a77b3fd23640691f3)
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: I729b66aa82c4bde434879e9ef696c03d4015c624
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The upstream is updated to support Yocto gatesgarth tag, fix the
meta-g220a layer:
* Remove meta-x86 which is empty and does not support gatesgarth yet;
* Add gatesgarth in meta-g220a layer.
Tested: Verify meta-g220a builds fine with upstream code.
(From meta-bytedance rev: 5ba67f07bc7d145712d56eaa70d892cb8ba9fc3e)
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I98eebe6472dccf88837df23de7b4f8f757d64f19
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
G220a is an x86 server platform with an ast2500 BMC
(From meta-bytedance rev: f6d9fbafdfa3e5b0088f4d72792f2f3a031009a6)
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
Change-Id: Ie0851a3e689fa7348cbb812e9ff51ea570632123
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|