Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I28ee50fa55ae47dd7fd8c99f8f6db8f5f6dfa53d
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I85272779478b66452acd11be93f5fea99e4c3a34
|
|
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: I5fd106fcc9de9895bc0d79f265e5c0ab06ee624a
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
|
|
This enables timesync support for the gbmc distro.
Change-Id: Idb653e6b98a347b5d8c3a0b3a16c6a4abbe268ac
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
The only machine in this layer is the google / rackspace zaius system so
we should have maintainers that own in.
Change-Id: I4ba35e53efaa4eb0d4b824e0fc3c0edb5d6f9e9a
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
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>
|
|
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
|
|
* Deprecate N-1 release (hardknott).
* Enable N+1 release (kirkstone).
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
|
|
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
|
|
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>
|
|
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>
|
|
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
|
|
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
|
|
Cleanup with
```
convert-overrides.py meta-ingrasys
git grep -l _zaius -- meta-ingrasys \
| xargs sed -i 's/_zaius/:zaius/'
```
After cleanup
```
$ git grep "_[a-z0-9_/-]*[ :]" -- meta-ingrasys | grep '.bb'
meta-ingrasys/meta-zaius/recipes-phosphor/sensors/phosphor-hwmon_%.bbappend:# compose_list is not defined immediately so don't use :=
```
Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: Ib2da97530167688313ac16aedd69168137788c86
|
|
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>
|
|
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
|
|
Most openpower machines use DISTRO="openbmc-openpower" but
Zaius has a "openbmc-zaius" distro config file. This
config file has nothing except an inclusion of the openpower
one, so remove this useless indirection.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I58a5c8b8990f4ba2d18df1a4c731a5134e373f87
|
|
We have a distro feature used within u-boot-aspeed to control the
use of MAC2. This is effectively a function of the machine and
not a function of the distro. Move the 'require' statement from
the openbmc-zaius distro into the zaius machine config to reflect
this.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I56a6f57b26915908b5c05bc922e54e764cf72300
|
|
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 dunfell (previous).
(From meta-ingrasys rev: 7dfbc01f6787cf41bf9be2bd0f5b3c46ce710016)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I359e4ce2c8dcbcfbe77bea3c36cc38398a60c6ba
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-ingrasys rev: 52368129e9b624f9acd98c6156ea7a5d6d21ba4f)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: If78b0ef8b9db95b8af2254d4b299a6c28e262044
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Dbus sensor interface 'xyz.openbmc_project.Sensor.Value' migrated
from int to double. Therefore all old 'int64_t' types in
"*-ipmi-sensor*.yaml" files for this interface should be changed to
'double'.
(From meta-ingrasys rev: a77281516cf6aa609bb64196b6f48dbf0c52d725)
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Ic14b9488d4da964a1d48052d9a8b334dbb753996
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Enable the postcode-7seg support as part of phosphor-host-postd.
(From meta-ingrasys rev: b23cce18cfd15c88984c6ed781c75d926ae381c5)
Signed-off-by: Kun Yi <kunyi731@gmail.com>
Change-Id: Iec63f90460e6b4fd711b256bac0ee781b5535a0d
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Time.Owner has been removed from phosphor-dbus-interfaces so this
override is no longer appropriate.
(From meta-ingrasys rev: 5d9fdf55c5d0400cfb92b27a9a5e4755e4c1e0c5)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iaa96326d0f624df72054b0be53698f85d3d48fac
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This was a P9 DD1 workaround. These systems are no longer supported and
are not found in the wild, so the workaround has been retired.
Zaius opted to use it's own application for vcs control. We can now add
that directly instead of overriding vcs workaround with vcs control.
(From meta-ingrasys rev: 721db18e94f400a0b81d4a92ad2336be76fe1a6d)
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: I4e9b26e5791a9b1dc8a5de343e52d5859154330a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-ingrasys rev: f6f1bf099107971f737a87b8fd4f85fadc0a3e78)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: If877cad79cb8f581c1b28e012837402e5e73d956
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
(From meta-ingrasys rev: 3ffec70944abf2a222f8a57839584519fd4efd92)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ifedf4a3183af5ba3269b7edc28087e0ebd650528
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This reverts commit 66419549bc438ce800b9149ccae0ef02bf7e3bca.
This patch is still under development and as is breaks the build.
(From meta-ingrasys rev: df05e2d9f5843abf8cf4ef81a6b42752475ad6d8)
Change-Id: I2158c28a2033c2bcf5f8a9cded8e345e39d5df6b
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Our previous start_hwmon.sh script was not escaping the filenames
properly, resulting in configuration filepaths that differed from the
actual filepaths.
(From meta-ingrasys rev: 66419549bc438ce800b9149ccae0ef02bf7e3bca)
Change-Id: I4d7c634c8cbe0987ae4407d9fd1431ff16064119
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
OE-core master will be dropping warrior soon; zeus is the next release.
(From meta-ingrasys rev: 9e946a348a50d439bbacafaf4f27f9910983d23b)
Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: I302038aaab5a120587e734bc1c8bbf30d93cbe20
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
INGRASYSBASE is only used for pointing at licenses...point at the
licenses in oe-core in meta/files/common-licenses instead. to match the
defacto convention used in other oe layers like meta-openembedded.
(From meta-ingrasys rev: fcd2b2998a76f00307bb2ff821efa8ff8ef87c68)
Change-Id: I76d73574778db36a649f20ccc0a5149f616743af
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add errnos produced by the OCC driver stack to the REMOVERCS environment
configuration. Zaius has a persistent issue with OCC unbind operations
taking too long during host power off, resulting in hwmon errors as
phosphor-hwmon attempts to poll the OCC.
(From meta-ingrasys rev: b821af616c2bca5021bd28d80209341328371225)
Signed-off-by: Eddie James <eajames@linux.ibm.com>
Change-Id: Id010a7269e641d81f1b074565d2c684a2c8e04ea
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Enable the distro feature phosphor-aspeednic-use-mac2
to support MAC2
This solution is not desirable but it works for now,
For details please refer to
https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/23415
Noted that this changed local.conf.sample, which means you need to
modify the build/conf/local.conf accordingly
Tested: devtool modify u-boot and saw the aspeednic patch is applied.
(From meta-ingrasys rev: c827e2bd3ec4dfddc3e895bf3643390a0d44b79d)
Signed-off-by: John Wang <wangzqbj@inspur.com>
Change-Id: I691671434ca143add029df6d66d86059f4e309c1
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
All the IPMI virtuals and PREFERRED_PROVIDERS in meta-phosphor are in
the process of being deprecated. Prepare for that and move to a simpler
scheme for providing the YAML configuration for Zaius systems.
(From meta-ingrasys rev: a01ad654ff32e8f16ab36033ca1656d6b15bd1a0)
Change-Id: I3d9cd4194d71d994e3f3dcff9a7174d61b2e7c53
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Bitbake uses this regex to associate recipes and bbappends from BBFILES
(which contains recipes and bbappends from -all- layers listed in
bblayers.conf) to this layer. The association is then used to map the
BBFILE_PRIORITY value for this layer onto the recipes provided by this
layer.
BBFILE_PRIORITY is used to determine which recipe to use when the same
recipe appears in multiple layers.
Without BBFILE_PATTERN set, recipes in this layer will get a default
priority and not the priority specified in BBFILE_PRIORITY.
This layer doesn't set a priority anyway, so functionally this patch is
a noop but it is an improvement from a correctness standpoint, and it
makes a warning go away.
(From meta-ingrasys rev: 67480036566266a3501bf42e230b5a0c0b7fd82e)
Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: I9e9075907fe994606a09fd6965888e9585463381
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Bitbake uses this regex to associate recipes and bbappends from BBFILES
(which contains recipes and bbappends from -all- layers listed in
bblayers.conf) to this layer. The association is then used to map the
BBFILE_PRIORITY value for this layer onto the recipes provided by this
layer.
BBFILE_PRIORITY is used to determine which recipe to use when the same
recipe appears in multiple layers.
Without BBFILE_PATTERN set, recipes in this layer will get a default
priority and not the priority specified in BBFILE_PRIORITY.
This layer doesn't set a priority anyway, so functionally this patch is
a noop but it is an improvement from a correctness standpoint, and it
makes a warning go away.
(From meta-ingrasys rev: 7a286ca0dba71a6ef309ff031cafc06e2c00cb8d)
Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: If0d38267efdf74a6d010278b5604ac517f4487da
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
meta-aspeed: c8d791ede6..35a494ecb3:
Andrew Jeffery (1):
linux-aspeed: OCC, ISL68137, ASPEED spi-nor updates
meta-ingrasys: 67bcaf389f..71846afdc6:
Patrick Venture (5):
meta-ingrasys: zaius: hwmon: udc90160 specify informative names
meta-ingrasys: zaius: enable isl68137 and ir38064
meta-ingrasys: zaius: phosphor-hwmon: add vrm nodes
meta-ingrasys: zaius: phosphor-hwmon: add power-brick nodes
meta-ingrasys: zaius: update ipmi sensor inventory
Robert Lippert (3):
meta-ingrasys: zaius: remove reflock fixup recipe
meta-ingrasys: zaius: avsbus-control: use linux driver instead of raw I2C commands
meta-ingrasys: zaius: no longer need to set VDN VOUT_MAX during host boot
Change-Id: I5dbcfae6f937e0f01e5fca4c1f686be0e82b7ee1
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
A number of corequisites exist so squashing these all into one patch.
meta-ingrasys - refresh master bc513127f4..67bcaf389f
meta-hxt - refresh master 86a4df514f..8fe0d38bbb
meta-phosphor - refresh master 06c09d7cce..df6ddae3d2
meta-quanta - refresh master 4f126361a1..53f3025271
Change-Id: I3daeef2a0467d8ea4f1fd1c617e526f8b11258af
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
oe-core branched in preparation for the upcoming 2.7 Yocto release and
as of 13e45ff requires core layer compatibility to "warrior" instead of
"thud". We'll retain compatibility for both until we do our own branch
or stop testing thud.
(From meta-ingrasys rev: bc513127f473da3cdadf59f4836043e8dbf2e3bf)
Change-Id: Ic35d93d2d24506a9a8f50bda9f5f76af0c97208b
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|