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
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Zaius doesn't use poky, so drop meta-poky from the layer configuration.
Zaius also doesn't need meta-webserver with the recent move to bmcweb.
(From meta-ingrasys rev: 0b3e60508154017b923320c18b133756ec34fc8a)
Change-Id: I75ead8eb6cbb1b10383cc5f81637e030521bc075
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add zaius-ipmi-sensor-inventory instead of appending to
phosphor-ipmi-sensor-inventory to not drop the zaius file with another
machine that hasn't set an override. The other machine will use the
default file supplied by the default provider.
(From meta-ingrasys rev: 9cedd21e4a0e71f3f13d6ffe0e9317b3e308a943)
Change-Id: I3f15f15553ad8449e19cc2400c2bcb29d0dbb613
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add zaius-ipmi-fru-properties package instead of appending to
phosphor-ipmi-fru-properties to not drop the zaius file with another
machine that hasn't set an override. The other machine will use the
default file supplied by the default provider.
(From meta-ingrasys rev: 4dd8f1dfde10a79c67d2be020ea2dce27bdde7c8)
Change-Id: Iac04818b3f879d26b0084f49e5c131a9e115a3e8
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Reset the following subtrees on thud HEAD:
poky: 87e3a9739d
meta-openembedded: 6094ae18c8
meta-security: 31dc4e7532
meta-raspberrypi: a48743dc36
meta-xilinx: c42016e2e6
Also re-apply backports that didn't make it into thud:
poky:
17726d0 systemd-systemctl-native: handle Install wildcards
meta-openembedded:
4321a5d libtinyxml2: update to 7.0.1
042f0a3 libcereal: Add native and nativesdk classes
e23284f libcereal: Allow empty package
030e8d4 rsyslog: curl-less build with fmhttp PACKAGECONFIG
179a1b9 gtest: update to 1.8.1
Squashed OpenBMC subtree compatibility updates:
meta-aspeed:
Brad Bishop (1):
aspeed: add yocto 2.6 compatibility
meta-ibm:
Brad Bishop (1):
ibm: prepare for yocto 2.6
meta-ingrasys:
Brad Bishop (1):
ingrasys: set layer compatibility to yocto 2.6
meta-openpower:
Brad Bishop (1):
openpower: set layer compatibility to yocto 2.6
meta-phosphor:
Brad Bishop (3):
phosphor: set layer compatibility to thud
phosphor: libgpg-error: drop patches
phosphor: react to fitimage artifact rename
Ed Tanous (4):
Dropbear: upgrade options for latest upgrade
yocto2.6: update openssl options
busybox: remove upstream watchdog patch
systemd: Rebase CONFIG_CGROUP_BPF patch
Change-Id: I7b1fe71cca880d0372a82d94b5fd785323e3a9e7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
With meta-phosphor commit fd1f696f99 this is done by the distro
configuration; so, no need to do it in local.conf.
(From meta-ingrasys rev: 302ca19cdaa86cc9c48a859459ca05e13b962534)
Change-Id: If7add5d0ce4eb52143521d5981449052797ede8e
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>
|