Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I2ca490f59630039696f7d1c8086520aa805a7e36
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I7a755976c2144356314faef7cf1f226ae18dc884
|
|
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>
|
|
The 'setup' script looks for machine config files being present
to know that the meta-layer contains a valid machine for OpenBMC.
The nuvoton EVBs are split between meta-nuvoton for the base support
and meta-evb-nuvoton for "EVB on Phosphor" support.
Add symlinks for the machine config files from meta-nuvoton into
meta-evb-nuvoton so that setup recognizes them as valid machines, but
using the phosphor layers.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I871432047979f8a7c3d1b836633a5dc74864b6fa
|
|
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
|
|
The feature was implemented as an append to the kernel (BSP) layers in
meta-phsophor. This created a three way dance between machine layers,
BSP and meta-phosphor, when it should have been the kernel layer
providing this feature and machines could then opt in.
Fixing this means we could remove the KERNEL_DANGLING_FEATURES_WARN_ONLY
workaround.
As the feature is simply turning on a pair of kernel options without any
other impact, we can implement it by adding the options to our
defconfigs. In fact, aspeed and hpe kernel configurations enable the two
kernel options:
$ git grep CONFIG_KEYBOARD_GPIO=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_KEYBOARD_GPIO=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_KEYBOARD_GPIO=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_KEYBOARD_GPIO=y
meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_KEYBOARD_GPIO=y
$ git grep CONFIG_INPUT_EVDEV
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_INPUT_EVDEV=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_INPUT_EVDEV=y
meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_INPUT_EVDEV=y
meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_INPUT_EVDEV=y
Other machines that wish to enable this feature should ensure it is
added to their BSP's defconfig, or add it to their machine specific
defconfig.
Change-Id: I0726836319022f96c1d13d4a0cbd73708047302c
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
The 'setup' script looks for machine config files being present
to know that the meta-layer contains a valid machine for OpenBMC.
The aspeed EVBs are split between meta-aspeed for the base support
and meta-evb-aspeed for "EVB on Phosphor" support.
Add symlinks for the machine config files from meta-aspeed into
meta-evb-aspeed so that setup recognizes them as valid machines, but
using the phosphor layers.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I673756a3d837f61d7338b8fbb356c5234770ffca
|
|
Add obmc-phosphor-bsp-common.inc for building OpenBMC image.
Tested build with:
TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2600/conf . openbmc-env
bitbake obmc-phosphor-image
(From meta-evb rev: ddba410ebffe7bace588ff6d216c43608f4c5310)
Signed-off-by: Troy Lee <troy_lee@aspeedtech.com>
Change-Id: Ia005eb875f11fec8ffb3aadd5fff4b93a3028f3a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This commit has been verified with AST2600A1 EVB with the image created
by the following command:
TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2600/conf . openbmc-env
bitbake obmc-phosphor-image
(From meta-evb rev: 9ec0661731103f703660aa65b5806a126a4f69fb)
Signed-off-by: Troy Lee <troy_lee@aspeedtech.com>
Change-Id: Ie928880ed77ea77cecb33a900092f6ffc5454fb8
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 dunfell (previous).
(From meta-evb rev: 4d356d1b1afe5b7050220a649b894b1309973495)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ia4a5889b5cb26171b4578f7a29254c9ad0c527a0
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add obmc-bsp-common.inc so that evb-ast2500 build produces the OpenBMC
image.
Tested: Verify that the evb-ast2500 builds OK with below commands:
TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env
bitbake obmc-phosphor-image
(From meta-evb rev: 55bf3f1528d5c90c08c7cfa42e3f1783b4d29d35)
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I00b22e5fc9a99296028621abb29f40a44e99fc34
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The config evb-ast2500.conf is replaced by the one in meta-aspeed.
Remove it.
(From meta-evb rev: 122ac03206645f5bcece5e7aad5d5983c0f26031)
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I5372436effe5fa84532d9a17576f3204eadb18b5
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
EVBBASE 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-evb rev: 1da7522494e80d2355c240e0eb05ae7576ee32cf)
Change-Id: Ie2f441c1f53bf367bea7cb4fb4da51c7e5602d97
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Resolves: openbmc/openbmc#3603
(From meta-evb rev: 0d0349ec8bb0b05934bd026a49bda64c408a4cad)
Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: Icd3d7c3b1d1ca6de7c1bdb44e4c651fd98d2b3ef
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Set compatibility to thud and warrior.
(From meta-evb rev: 4d85a858915070372700be7905c397379030d595)
Signed-off-by: kwliu <kwliu@nuvoton.com>
Change-Id: I5de64963f205ffd5f9e56937f2fccab6cced1138
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
set layer compatability to thud
(From meta-evb rev: e16a390306e917b7a5f41fd73dd3ac67a7fbc476)
Change-Id: Iaff472e7779f4e59986aa6d5e6fc86c67162eb39
Signed-off-by: Samuel Jiang <Samuel.Jiang@quantatw.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Set LICENSE field explicitly.
(From meta-evb rev: e5e7ee9fbce4f3285d53e487c1b0f6967649b458)
Change-Id: I890edf620b75c150865111048e2f67386e0c1d80
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Define a variable that recipes can use for finding the root
of the evb layer. Typically this is used to refer to the
layer LICENSE for recipes that don't have any source repository.
(From meta-evb rev: bf038b9cfd62406da05f692a3cb0a952a1826091)
Change-Id: I4a8fbadb3f9bf81ce053385658a1e79c69f34437
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This adds preliminary support for the Enclustra Mars ZX3 using the upstream
meta-xilinx layer. In order to get it to compile this removes the
phosphor-gpio-keys feature even though it could theoretically be supported.
(From meta-evb rev: 07837e0d7d62497302c114008d27e0a808106ca2)
Change-Id: Ie02c329864d2c981dbe245a16e0e9858b37d6aee
Signed-off-by: Alexander Hedges <ahedges@ethz.ch>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
When meta-evb was split out as a subtree from openbmc the license
information was not copied to the new repository.
License of the metadata and code remains unchanged - this is only a
documentation update.
Fixes: 194ff4f1f5d44b12e9cb06ddafa6adb20174a13c
(From meta-evb rev: 08aad8396ee6adcd9be614e7f83813b05f5aee6e)
Change-Id: I26757042a5a2cbcff8281bfd02493b7772619048
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The new subtree model brings the subtrees up from the openbmc-machines
layer.
Change-Id: I58a03ae1be374bc79ae1438e65e888375d12d0c0
Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|