Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
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>
|
|
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: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I49f7334245394be03e77cb455d9e4d461fdb5705
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ie51238a6ab7baa9980b2a28014b036e5bd88a11a
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8ea79d284356629f5b7b24ad3a99336e9e2e297e
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
|
|
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>
|
|
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
|
|
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
|
|
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
|
|
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
|
|
Tested: Test on qemu ipmi chassis status cmd work correct
Signed-off-by: Lotus Xu <xuxiaohan@bytedance.com>
Change-Id: I60d20bf58c21b5c81d5fbad7649c1e2b43351392
|
|
`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>
|
|
With the upstream aspeed-uart-routing changes, the user space interface needs
to be updated to use the new path.
Tested: Verify the SOL is working fine on g220a.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I4313d240b2778ef8070214eb19029b559588bcea
|
|
The aspeed-uart-routing patches are in openbmc linux tree now. Remove
them from this layer.
The remaining patch will be submitted to the openbmc linux tree as well
and will be removed after it's merged.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I5d9db3701fe7b2e92e4960155c9b3e24fefdaf23
|
|
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
|
|
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
|