Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
|
|
It's not clear why these patches were added in this manner, but they
can't really remain here from a maintenance perspective. Pinning one
platform on an old version of x86-power-control, as well as setting a
specific patch means that it's impossible for people to test and use
upstream code with it. It is also explicitly called out as item #1 on
the meta layer guidelines for this reason:
https://github.com/openbmc/docs/blob/master/meta-layer-guidelines.md
To the maintainters of this meta layer, please work with Jason and Kwin
(the x86-power-control maintainers) to get your features accounted for
in the normal build, adding build flags and configuration entries where
appropriate.
Tested:
This almost certainly breaks power control on ethanolx, but given the
way this patch was merged, there's really no way to avoid that.
Signed-off-by: Ed Tanous <ed@tanous.net>
Change-Id: I1f6a40e5b01c36441ff8d66e8e73265e0e009a4f
|
|
Switch the u-boot branch from the 2016.07-aspeed-openbmc
to the 2019.04-aspeed-openbmc.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I7f17b31abe32c374b01cb037ba03ed2608c1190d
|
|
The code for obmc-op-control-host is only useful for OpenPower
machines, but somehow it is being included in many other machines.
Remove it from all of them except meta-openpower.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I4e7c7365eb320c3fb9ea7a57aca2ed0b1832e85e
|
|
In the AMD EthanolX board CPU0 UART1 is connected to the BMC UART0.
Therefore from the point of BMC UART0 is an upstream (host) UART.
'obmc-console' application gets this information from its configuration
file name ('server.ttyS0.conf').
On the other case setting 'local-tty' inside the configuration file is
intended for the downstream UART settings, which is not present on the
AMD EthanolX board. Therefore remove this setting.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I3daa1528cb5a7b5ff748189f29da3c3d91899ca4
|
|
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
|
|
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
|
|
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>
|
|
`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>
|
|
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
|
|
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>
|
|
Make the following changes to fix compilation errors:
- add honister to the LAYERSERIES_COMPAT variable,
- increase CONF_VERSION to 2,
- use new bitbake override syntax
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I971f0f0f7110e0350994ced151ca429444885056
|
|
AMD EthanolX CRB uses 24LC128 EEPROM as a device that is supposed
to store FRU information.
Add necessary Linux driver that adds support for this chip.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Iaf54bfd5bfbc3266d2a18861ee47339df78c777b
|
|
The BMC on the AMD Ethanol CRB uses entity-manager for sensor
configuration. Therefore IPMI configuration YAML file should
use DBus paths to sensors based on the names from the entity-manager
JSON files.
Currently 'ethanolx-chassis.json' exports CPU fans on a DBus as
"P0_Fan"/"P1_Fan". Use these names to correctly populate CPU fans
to the IPMI.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I0425e42771e1bfb36ad067dfcad5a23e5f180d67
|
|
AMD EthanolX CRB is a board with x86-64 CPU, which means it can support
both EFI and Legacy boot.
Add 'boot_type' PACKAGECONFIG option for the phosphor-settings-manager
package to support EFI/Legacy selector in the BMC boot override feature.
This setting is designed for the possibility of setting boot override
as:
- "PC compatible" boot (legacy)
- Extensible Firmware Interface Boot (EFI)
Change-Id: I173c5b439b929e80f3a106f5e7775862f889ee16
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Populate ADC sensor data to the system. This change make ADC data
accessible over DBus, IPMI, Redfish and webui-vue.
The threshold values were calculated as 10% from the target values.
The "PowerState: On" entity-manager parameter on the "*_RUN" channels
is used to make thresholds active only when the board is powered on.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I5322e83fdbfa0815bed454ea81b83725a2221d2c
|
|
Populate voltage regulator sensors to the system. This change make
voltage regulator data accessible over DBus, IPMI, Redfish and
webui-vue.
AMD EthanolX CRB has 4 voltage regulators per each of its CPUs (P0/P1):
-ISL69147 - Px VDD core regulator
-ISL69144 - Px VDD SoC regulator
-ISL68127 - Px VDD Mem / VPP ABCD regulator
-ISL68127 - Px VDD Mem / VPP EFGH regulator
All of these voltage regulators are 1st generation multiphase devices.
They can be covered with a ISL68137 Linux driver initialized with a
"isl68137" parameter, which would bring the necessary "raa_dmpvr1_2rail"
initialization.
The threshold values were spoofed from the original voltage regulators
configuration in the AMD EthanolX CRB.
The "PowerState: On" entity-manager parameter is used to make thresholds
active only when the board is powered on.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I123db2e356f525e0d269aef780d34d218209592a
|
|
Populate SB-TSI CPU sensors to the system.
This change make SB-TSI CPU sensors accessible over DBus, IPMI,
Redfish and webui-vue.
The entity-manager configuration make use of "PowerState: On"
parameter as SB-TSI sensors are active only with a powered on CPU.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I80390bb0baa291e7a9d5b49b2e9542cef719da69
|
|
On the AMD EthanolX CRB only few of the dbus-sensors apps are
relevant. The rest of them aren't needed and will only waste
cpu time and produce ambiguous fail messages at the initilization
stage.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I9ce01d93d79b40386a59757244e8b9b8a6008289
|
|
Some I2C addresses can't be probed for a FRU. For example,
device at this address can be already connected to a driver
or the I2C bus is not scannable like the APML bus.
In this case 'fru-device' app will be producing messages
like this:
'fru-device[XXX]: device at bus X address XX busy'
To avoid these unnecessary log messages add I2C bus blacklist
json file for the 'fru-device' app.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I0618943c9362117d9931defa1e17bcd999621197
|
|
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
|
|
This makes it possible for us to change out build specific settings.
Change-Id: Idf3643556f7cf134841043d955a5ee057906fba6
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
'phosphor-webui' is no longer developed.
It was built on AngularJS and AngularJS goes
End of Life June 30, 2021.
'webui-vue' is a modern replacement for the
web UI app.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I2b907784a06feeaa48c1336c9eab72828706d9ea
|
|
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 system fans to entity manager configuration files
and to IPMI YAML configuration files.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Ib86a09553073b6ecf112232ca939758ecc5516c9
|
|
As now 'entity-manager' and 'dbus-sensors' apps are used for the
sensor monitoring, 'phosphor-hwmon' app and its configuration files
are no longer needed.
Moreover if 'phosphor-hwmon' app is present alongside with the
'dbus-sensors' app, it would produce duplicate sensors on Redfish.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I251663a05a8447ad84e13855c02284930ba8d8f4
|
|
The current 'amd-fpga' recipe leads to constant warning
messages in a bitbake build:
"""
WARNING: Recipe amd-fpga sets S variable with trailing slash,
remove it.
WARNING: Recipe amd-fpga sets B variable with trailing slash,
remove it.
"""
Remove the trailing slash from the recipe to get rid of the
messages.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Icb262d38f21cd0a08ddc1af01db7db01ddbc97e4
|
|
The repository supports it, so switch it over in bitbake.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I8d96c79b395ee2614ddd869091569f245426c5c7
|
|
Usage: fpgardu.sh
Uses i2c bus 2 to access FPGA registers and display the data
Signed-off-by: Paul Erb <paul.erb@amd.com>
Signed-off-by: Supreeth Venkatesh <supreeth.venkatesh@amd.com>
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I2608eb48fa4cb3ef2d8837bc22a8efe3dc339d37
|
|
Configures the kernel configuration to include support for SB-TSI
driver.
Signed-off-by: Supreeth Venkatesh <supreeth.venkatesh@amd.com>
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I718375d70550edf90c407ac8595f00347061e9a4
|
|
Add entity-manager baseboard and chassis json configurations for AMD
EthanolX.
bb append entity-manager recipe to include above files.
Sigened-off-by: Supreeth Venkatesh <supreeth.venkatesh@amd.com>
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I766be9587149fe54034ff8e01aa1013797f873a9
|
|
Enable dbus-sensors application.
It will be used in conjunction with the
Entity-manager application to provide all
the necessary sensor monitoring services.
Signed-off-by: Supreeth Venkatesh <supreeth.venkatesh@amd.com>
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Ia358e630cd4518ca6ec1722fa383b6786b835e82
|
|
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
|
|
Devicetree patch is no longer needed as all the changes are now merged
upstream and will be by default in the next kernel release.
As to the current OpenBMC kernel release, all the changes were backported
and therefore the devicetree patch is no needed here too.
(From meta-amd rev: a6dd837fee1cd0ff765d9f84150baea32b4ab35d)
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I81b5a8bd139dcf1da32da6b5005b3e9e015d2fd7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Please see https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/39379
for details about why this is necessary.
(From meta-amd rev: 0674e6ad3c53aa12cf56962b3d5627bc541356bd)
Signed-off-by: Ed Tanous <ed@tanous.net>
Change-Id: Ie48ce1f7af59b2413565d3b9e66875596486a179
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
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-amd rev: 053aaa505b711929800bffdcc1f748ddb89e50e7)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I98a0b761a51db8813ac50fb89ba3923b89a39259
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add 'channel_config.json' file with configuration settings for
the AMD EthanolX Customer Reference Board
(From meta-amd rev: 6ea0bb93cc31d9caeb876411849229c8c49c1a2a)
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I42bbb4f3593e51f845a28e2d7b6c2e040c299819
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Adds MAINTAINERS file which lists the initial maintainer for the
meta-amd repository.
(From meta-amd rev: bf95777b8150cef8772d825124b9d72c5a727e9e)
Signed-off-by: Supreeth Venkatesh <supreeth.venkatesh@amd.com>
Change-Id: I498ecb9403c2c4cbfea3a0b4a2e1113fdf244d64
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|