Age | Commit message (Collapse) | Author | Files | Lines |
|
The first dtb listed in the KERNEL_DEVICETREE list is the default used
for the BMC's genesis boot. The Bonnell device tree specifies an eeprom
that's larger in size than other p10bmc systems. Therefore the device
driver currently truncates the data on this eeprom when doing a genesis
boot on Bonnell since the default device tree is for Rainier.
Move Bonnell to the top of the list to be the default since it has the
larger eeprom size.
Tested: Booted Rainier and Everest on simulation to test a genesis BMC
boot. Verified they first booted with the Bonnell's device tree, then
the BMC automatically rebooted after the machine type was identified and
the device tree corresponding to the system was loaded.
Change-Id: Icb9abe7d8b04d42befd9eb906d095f4fa046ab3c
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The switch enables AF_MCTP and adds the `mctp` tool and `mctpd` so we
can setup and manage an in-kernel MCTP network.
Enable it for p10bmc and also add CONFIG_TUN so we can use a tun device
to transport packets between the kernel and the astlpc interface
implemented in libmctp.
Change-Id: I21d0af9e751f91975c760b4b4708b3b401b95417
Signed-off-by: Rashmica Gupta <rashmica@linux.ibm.com>
|
|
This new machine will be based on the p10bmc machine. It will be
utilized to prototype and develop next generation distributed OpenBMC
technology.
Change-Id: Id9cef6fae52867a8eabf9e38a210c26dfa04ed25
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Similar to previous generation of the POWER processor, introduce a
p10.inc that can be included on P10 systems.
Without this, the needed op-proc-control services and functions are not
brought in.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I58490e95e69ef8b4b31b0f4bc9213787058f0bba
|
|
Witherspoon uses UBI instead of static partitioning for flash
management, so make sure the qemu helper script can find the flash
image.
Tested: Reached a login prompt with `runqemu nographic slirp`.
Change-Id: I513d0a5b878c553456d70bef25adedfa25bf9c90
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
The witherspoon-tacoma server has the larger flash and will be utilized
for some OpenBMC prototype work. Add in some useful debug tools.
Change-Id: Ie3276088b1137a838a72e22a68a2c9fcf9bacb82
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Tested:
- Confirmed tools are in p10bmc flash image
Change-Id: I808f38f410eaaad3077bb7eeaf36a166faf5beb4
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Explicitly set FLASH_SIZE to prevent SPI-flash related configurations
being pulled into the build. Specifically this prevents the default
value provided by meta-phosphor triggering the uboot-flash-32768
override. The override pulls the u-boot_flash_32M.cfg configuration into
the build, breaking the environment handling for p10bmc machines which
exclusively use eMMC.
Change-Id: Ice0e2be27d5bd7ca207dcaf91ea311137fc55439
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
A recent refactoring requires the mmc include be first to ensure we
build an mmc based image
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I7d4112dc5b39f0f21cc1dbc61e88b12ae3418215
|
|
We have reached branch-capacity in the bb.utils.contains checks
at 3 image types. In order to be able to more easily add additional
image types, split the differences out into additional inc-snippets
for each image type.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ibcdb5c885c67cb6d8728dfd315eb07f99b1a2173
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
|
|
The org.freedesktop interfaces have the same "use everywhere" status
as xyz.openbmc_project, since they are not specific to any company
or architecture. Enable them in meta-phosphor.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I3261a6777b2c9003f5476061e4df30811321f73d
|
|
Since the p10 machine relies on the org/freedesktop, but it is disabled
by default, resulting in failure to build the bmc image.
This commit needs to modify OBMC_ORG_YAML_SUBDIRS and enable
org/freedesktop by default.
Tested: built p10bmc image successfully.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ife87f359bf5a0f8c682ccb56ddbdeec84b12ca3a
|
|
Qemu boots kernel+dtb directly, and mounts wic image (full filesystem)
as an emulated mmc device.
We add zImage as a KERNEL_IMAGETYPES (plural is important) so it is
copied to the deploy directory.
Currently there is only a wic.xz which cannot be booted directly. We add
wic.qcow2 so the wic image is exported as a usable image for Qemu. This
is a sparse image so empty space does not take up disk.
TODO:
1. qemu requires the image size to be a power of two. Current
workaround:
qemu-img resize p10bmc/tmp/deploy/images/p10bmc/*.wic.qcow2 16G
2. Boot via u-boot. Requires qemu mmc patches from Cédric's tree, and
creating an image with the boot0/boot1 partitions in it.
Change-Id: Ic64023b2d7f9bce80a025a1d847228e90e0b72bd
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
A fork of it is maintained but its upstream layer has largely been
unmaintained.
No future products are planned to be based on this layer.
Mihawk is similar to Witherspoon.
Signed-off-by: Myung Bae <myungbae@us.ibm.com>
Change-Id: I82f7d777b78cd126237d51e42f1e11abdf80ae68
|
|
Witherspoon has a Qemu model called witherspoon-bmc.
Change-Id: I086b350182c0deb990b93d88461162181c29e815
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I65febeeec11e6e5b40ee728f42cfbe77023dae1e
|
|
Bonnell is a new IBM system which will be supported within the p10bmc
image. Load its device tree into the p10bmc image.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Idad1aed9aebafcca847a1c2a7749bb29f432601f
|
|
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
|
|
Joel Stanley (2):
ARM: dts: Rename Rainier to P10 BMC
ARM: dts: ast2600: Fix indentation
Change-Id: I732324d89b7c0f731160d69942051e4d4cadc778
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
This configures the distro name printed at system boot to indicate that
p10bmc is a combination of OpenBMC and custom components.
Change-Id: I130ce058244bd989a36855000cb4412215a74015
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
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
|
|
Providing `opkg` in the image allows us to easily install packages
after-the-fact, usually to debug systems in the lab.
This is not a mechanism for providing firmware updates.
No specific configuration is supplied to enable its use, and hosting of
package archives is left as an exercise to the user. That said, bitbake
generates its own package archive in the course of creating the output
image. It also provides a `package-index` target, which after execution,
allows you to expose the archive with no more work than:
```
$ python3 -m http.server --directory tmp/deploy/ipk 8080`
```
The addition of opkg with the chosen options increases the uncompressed
filesystem size by 3855360 bytes (~3.68MiB).
Change-Id: I7731a4ebe08249e2216e8ca1984f8e8d87558687
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Don't support the hardware root-of-trust on Tacoma boards.
Change-Id: I144d3bf445063f6341ae1958611873f79c9c00c7
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
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
|
|
This enables the TPM driver in the kernel configuration.
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: I0278543d753c7526d14eb971ac678ff364719d49
|
|
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>
|
|
Witherspoon is running tight on space, and as our primary hardware CI
machine, we need to keep it going.
The GUI has already been pulled out so the KVM package doesn't make much
sense anyway.
Tested:
- Reduced image size by ~200KB
- Will rely on CI to regression test
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I3e55702da764e4e1ca1673e158c7acf4f74c9bda
|
|
`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>
|
|
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
|
|
openpower-pnor-code-mgmt: srcrev bump 9c2ef681e3..6fc7fcd6b1
Adriana Kobylak (2):
Add a new pldm feature option
Add support for the host PLDM transport that takes place of hiomap
(mboxd). Add this new feature to p10bmc.
Tested: Verified that tacoma (that doesn't support pldm) and p10bmc
(supports pldm) reached runtime.
Change-Id: I31e8beba5ff8a413b7b7fa7476f5f2403d3781dd
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Adriana Kobylak <anoo@us.ibm.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>
|
|
With the reshuffle that occurred in 38cfcc393d9e ("meta-aspeed:
u-boot-aspeed-sdk: Use provided signing key by default") we no-longer
need to specify these options in p10bmc.conf
Mistakenly, `SOCSEC_SIGN_ENABLE = "1"` was duplicated later in the file
by 699146128388 ("meta-ibm: p10bmc: Assert that we want the SPL signed
by socsec"). Removing the instance as done in this patch still leaves us
with the positive assertion that we want SPL signing enabled.
Change-Id: Iaa9cbe5b0ba4aaf69bb0fba1eb8f6bc62d085a33
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
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
|
|
Configure the SOCSEC_SIGN_* variables to sign the SPL and exploit the
AST2600 hardware root-of-trust.
Note that this doesn't require that secure-boot is enabled on the
system, the SoC will bootstrap just fine with the signature in place
while secure-boot is disabled. Signing the SPL allows us to switch the
systems over to secure-boot at our leisure.
Change-Id: I07b5c4afb7bacc040cbdce6c82a0fb3a57d0f7f8
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Update with the latest version from upstream.
Change-Id: I1a7da37b0457dab873afaf6445aca360d54b47ca
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
As for Rainier and Everest, use KCS2 as the debug-trigger interface.
Change-Id: I2614ffc3d97164658f2ad4fbb916cbf44be152e1
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
OpenBMC requires additional capabilities for the
OpenPOWER systems such as
- A common mechanism to access and control the host
hardware from the BMC.
- A storage mechanism to store the data that can be
used for initialize, control and access the CEC
hardware.
- An infrastructure to initialize the hardware using
the hardware procedures provided by the hardware team.
- Common mechanism to handle the hardware failures for
the host hardware.
These above features are essential for the BMC to provide
better RAS capability and to support lab debug for the
enterprise class systems.
The phal(POWER Hardware Abstraction Layer) aims to provide
a common layout such that the OpenPOWER application can
use this infrastructure to boot, enable RAS features like dump,
diagnostics, and lab debug tooling purpose.
The phal is a combination of open source packages that are
tailored/customised to use in OpenBMC. For instance POWER
hardware access and control is managed through pdbg and
host hardware data modelling is done via devicetree.
phal is group of libraries running in BMC. These libraries
are used by OpenPOWER specific application for host hardware
interactions, Hostboot and SBE initialization, diagnostics
and debugging.
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I187d9582598743871279a1e407451f4cf4f72668
|
|
Change-Id: Ic1cde1cd67fa6f8f68df80a1f327ace64a39d72b
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
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>
|
|
The rainier machine has been replaced with the generic p10bmc.
Change-Id: Ia7b6e8b6ad569d6f607d4a38318704fb402f2a1f
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Use the 'insecure/imprint' development key to sign the p10bmc SPL. The
key can be overriden for a production key if necessary.
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: I6e4abecb5859fb59c6185a097cf88bdcb958e207
|
|
Use the insecure key provided by commit '748d586bc1 meta-aspeed: Add
development key for Kernel sign' to sign both the Kernel as well as
U-Boot fitImages. This is used for U-Boot FIT Signature Verification
using a known key, fit for development purposes. For production
purposes, a secure private key must be used.
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: If0c39f4aa17e6eaa5f6952a90283457f252a64d3
|
|
This creates a new DISTRO_FEATURE "ibm-service-account-policy" which
- Adds an admin account which cannot SSH to the BMC's command shell.
- Adds a service account which can SSH and has passwordless sudo access.
This feature is applied to witherspoon-tacoma and p10bmc (rainier).
Tested:
The image behaves as before when the distro feature is not configured.
When the distro feature is configured:
The root user has the same access as before.
The admin user:
- Is not allowed to access the BMC's command shell.
- Console login gets: This account is currently not available.
- SSH login gets: Permission denied, please try again.
- Redfish and REST API access works with role=Administrator.
The service user:
- Console login to the BMC's command shell works. The home
directory is /. Passwordless sudo works.
- SSH login works and using sudo from a SSH session works.
- Redfish and REST API access works with role=Administrator.
Change-Id: Icac5ba7f4fa663047709ab55007bbcfec8158f5e
Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net>
|
|
The OBMC_ORG_YAML_SUBDIRS variable is intended to be set system-wide
and not via bbappends. There was an existing 'ibm-distrovars.inc'
that was unused. Rename it as appropriate, add it to the machines,
and remove the bbappend files.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Id5acd359f41c17ec9e68d1f0717e2f5c1bf96dcf
|
|
The meta-ibm layer supported two different DISTROs depending on the
machine being built. This caused complexity since the user needed to
remember to specify the DISTRO name, in addition to the CI build scripts
needed to check for the machine name being built to override the default
DISTRO.
For simplification, remove the openbmc-witherspoon DISTRO, which is the
openpower DISTRO plus additional features, and move these features to
the machine configuration files. Make the openpower DISTRO the default.
Tested: Built witherspoon and p10bmc using "source setup <machine> build"
followed by "bitbake obmc-phosphor-image" without specifying the
DISTRO. Verified witherspoon built a ubi image and p10bmc built
a emmc image.
Change-Id: If33441ab4ad2dc0fbedde09f0db91d691d2da4f7
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|