Age | Commit message (Collapse) | Author | Files | Lines |
|
Images built for HPE machines become too large when bash is added as a dependency.
Change-Id: Ib6e49647c22f1d0345ef44ffc9140ac73ed999b1
Signed-off-by: Charles Kearney <charles.kearney@hpe.com>
|
|
Change-Id: I8682f9334f4c771d0acda97f45d0cc7b374afd35
Signed-off-by: Charles Kearney <charles.kearney@hpe.com>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I30885f8c2577c3c2aa333a61210e6738fbf016c7
|
|
Cleaning up the OWNERS files to reduce the amount of "does not resolve
to any account" errors that pop up consistently in the gerrit logs.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I4fb7ff1946b21ab95d4d5bb47461fed6a7f7d07f
|
|
Signed-off-by: Charles Kearney <charles.kearney@hpe.com>
Change-Id: I650f926349ef2a57c352aac36a801b07fb4001ca
|
|
Change-Id: Ifa9b38e824619fff9f7c6c228252c56714871d1d
Signed-off-by: charles kearney <charles.kearney@hpe.com>
|
|
Change-Id: I03f741a0e11cecd49028d78a740f1d9e8678f878
Signed-off-by: Charles Kearney <charles.kearney@hpe.com>
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
|
|
This standard ipmi-kcs rule (as implemented in internal hpe builds)
resolves an issue with the obmc being hammered by kcs interrupts
when the host is booted on HPE platforms.
Signed-off-by: Chris Sides <christopher.sides@hpe.com>
Change-Id: Ieac607e95c36c53d1bc9f4ef3634dd67e1ece858
|
|
Part of an ongoing effort to upstream changes from the latest
internal hpe builds. This addition resolves an lpc-snoop startup
error on hpe platforms during host boot.
Signed-off-by: Chris Sides <christopher.sides@hpe.com>
Change-Id: I7014a075981d5d1a4056583e51aca95163a9cdc8
|
|
This power control implementation is not specific to openpower systems
(as seen by the variety of systems including it) so rename it to
something more appropriate.
This is using code from skeleton which is not ideal but that's a change
for another day.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Iffe6427b5494558b53cd6f5716a08cce82cb90d8
|
|
obmc-host-ctl is defined as a MACHINE, DISTRO, and IMAGE feature.
The IMAGE feature pulls in a virtual provider only if the COMBINED
feature (MACHINE + DISTRO) is enabled. This is only done on openpower
machines. There are a lot of other places where machines are half-way
disabling this feature and/or changing variables which have zero effect
anyhow. Clean up almost all references to `obmc-host-ctl`.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I090d782bb6a34dc4e3c43df97e8ccf6e1812fed5
|
|
This package is an old interface from 'skeleton' for which there
are no users outside of an IBM IPMI OEM handler, but the package isn't
even installed on any IBM machines. Remove all references to this
package from the tree so that it can be further removed.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Icda5c156940450ab033365d7f93d5542d6646696
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I65febeeec11e6e5b40ee728f42cfbe77023dae1e
|
|
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
|
|
For the moment, phosphor-webui is deprecated and unmaintained. The
replacement for it is webui-vue, which already has feature parity, and
many more features than its predecessor. Several calls have been made
asking if there is anyone still using phosphor-webui and would like to
maintain it into the future, but no such volunteer has stepped up.
Moving to webui-vue is the recommended option these days, and this
patchset is done under the assumption that these platforms would
actually like to move off the deprecated UI, and just don't have patches
to that effect. For the machine maintainers reading this, if you would
like to stay on phosphor-webui, please start that discussion here about
who would like to maintain it.
This commit ports the last few platforms over to webui-vue.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I9c74442b850aceca130545f37d5bc694a4f4424d
|
|
After updates Gerrit is now hosted at https://gerrit.openbmc.org.
Urls in the documentation are now updated to reflect this change.
Signed-off-by: Corey Hardesty <corey.hardesty@icloud.com>
Change-Id: I3a7f7d338ca1ce600ccf7b41fa03bd62007925ba
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I746b04e1e36abaf2ff3852beb8a04535692442c1
|
|
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
|
|
The LICENSE string 'GPLv2+' is considered obsolete by Yocto and raises a
warning. Switch them too the accepted tag 'GPL-2.0-or-later'.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I88c639dbb45762e2e019a3503f1f1930b65c09d6
|
|
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
|
|
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
|
|
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
|
|
`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>
|
|
Fix to conform to new model where we don't commit to the meta-hpe repo
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I38970e8f871ded204831d1009a5d9ba32349a483
|
|
Fixed the path to the common layer for HPE systems
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I9f0b0d1445ccd7de72669a317a331a2aa7bb18f6
|
|
This is a temporary stop on the way to 5.15
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I5c750c61b3d3e1561eb4cfb53989bde9fd2b1e58
|
|
New I2C driver and FRU EEPROM detect and read
Fetch MAC address for network boot of BMC
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I8ff7fc7b40fa720babbc9912642f500086573743
|
|
Update OWNERS and MAINTAINERS files with updated contact info.
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I2816d27b714e1fcc88d767049b2b95d874890eda
|
|
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
|
|
As a follow up to 400d9dab03e25d992429f94296caa4938c281fbd, fix the
deprecated SafeConfigParser to ConfigParser across the tree.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iabf941889eed97a996b739d77c8107f1f35ce5bf
|
|
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>
|
|
Add a post boot command to sync time
Use x86-power-control for chassis host power management
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I2f52cfc15eab4f2a63434e44b4e0c8f7d8eb0393
|
|
Code restructured to make the DL360poc the override case
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I615e040a3329d1af7f8861d751794be5f4a31836
|
|
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: If827b0d5e66a403942b28692ca738c99adc9da72
|
|
Linux kernel and DTS updates
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I365e1b6d1d060c131c9d7a1b0f76ef9256f0e73f
|
|
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I538f9e74fdc90d3eb1e7e778b2ff99777b0d07d7
|
|
Update the build recipes for the GXP binary bootblock that runs before U-Boot.
The code has been restructured such that the DL360POC machine is the exception,
so this includes the overrides for the DL360POC.
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I507a6e32c7c72613dbd1239824f528f0f60d1f6f
|
|
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I5cc4285e6a0459a8aab5bf8494c23d4235d43193
|
|
Changes to support Yocto syntax changes and latest 'honister' release
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I9cc4eb78b90d9b73bcd0440e6f6f6334fe459481
|
|
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
|
|
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
|
|
Background: The OpenBmc project default root account password is set
in meta-phosphor/conf/distro/include/phosphor-defaults.inc and can be
customized in each layer's local.conf file.
Many of these local.conf.sample files had redundant code to set the
password, which probably should not have been there. Removing them
allows the defaults in phosphor-defaults.inc to take effect.
Tested: No. Only meta-ibm was tested.
Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net>
Change-Id: I76dce00d269d7afa005d7bcfd63f846d3cf45596
|
|
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>
|