summaryrefslogtreecommitdiff
path: root/meta-quanta/meta-f0b
AgeCommit message (Collapse)AuthorFilesLines
2021-12-02Remove BBLAYERS_NON_REMOVABLE variableAlexander Filippov1-12/+0
`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>
2021-09-16bitbake: Use IPK packaging for rootfs assemblyAndrew Jeffery1-1/+1
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>
2021-09-02meta-phosphor: change systemd.bbclass to match upstream override syntaxPatrick Williams2-3/+3
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
2021-08-24treewide: remove gategarth from layer-supportPatrick Williams1-1/+1
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
2021-08-17meta-quanta: Fix incorrect change in Yocto syntax updateDavid Wang2-3/+3
'SYSTEMD_ENVIRONMENT_FILE', 'SYSTEMD_LINK', 'SYSTEMD_OVERRIDE' should stay underscore Signed-off-by: David Wang <davidwang@quantatw.com> Change-Id: Ia30f306857d1552b19ff5ed06664c8bd5360cb4c
2021-08-13meta-quanta: Cleanup for Yocto override syntax changeDavid Wang5-15/+14
- Cleanup subtree meta-f0b, meta-olympus-nuvoton, meta-q71l with convert-overrides.py meta-quanta/meta-f0b convert-overrides.py meta-quanta/meta-olympus-nuvoton convert-overrides.py meta-quanta/meta-q71l git grep "_[a-z0-9_/-]*[ :]" -- meta-quanta/meta-f0b git grep "_[a-z0-9_/-]*[ :]" -- meta-quanta/meta-olympus-nuvoton git grep "_[a-z0-9_/-]*[ :]" -- meta-quanta/meta-q71l git grep -l _f0b -- meta-quanta/meta-f0b | xargs sed -i 's/_f0b/:f0b/' git grep -l _olympus-nuvoton -- meta-quanta/meta-olympus-nuvoton | xargs sed -i 's/_olympus-nuvoton/:olympus-nuvoton/' git grep -l _quanta-q71l -- meta-quanta/meta-q71l | xargs sed -i 's/_quanta-q71l/:quanta-q71l/' - Fix up a few by hand - Revert 'BBFILE_PATTERN' and 'LAYERSERIES_COMPAT' - Add honister to 'LAYERSERIES_COMPAT' - Update 'CONF_VERSION' - Fix up 'SYSTEMD_ENVIRONMENT_FILE', 'SYSTEMD_LINK' and 'SYSTEMD_OVERRIDE' in all subtree Signed-off-by: David Wang <davidwang@quantatw.com> Change-Id: Ic431624d09dc5899b1d84439559bea9efca08ad8
2021-06-07treewide: Remove obsolete image-mklibs classWilliam A. Kennington III1-1/+1
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>
2021-04-22build phosphor-hwmon with mesonMatt Spinler1-1/+1
The repository supports it, so switch it over in bitbake. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I8d96c79b395ee2614ddd869091569f245426c5c7
2021-04-06hardknott: yocto releaseAndrew Geissler1-1/+1
Latest upstream yocto has moved on to the 3.3 hardknott release Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ieae36798d66d21c2c642931f06407d3bb2acf163
2021-03-22openbmc: add meta-security layerAnton D. Kachalov1-0/+4
This layer provides libseccomp. Signed-off-by: Anton D. Kachalov <gmouse@google.com> Change-Id: I84513d56f2ed75fab49043196b98ef8b858e394f
2020-11-23meta-quanta: update Yocto compat for gatesgarthPatrick Williams1-1/+1
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-quanta rev: 34f30a0dca7ab63d93d56132f93e96244b02aeff) Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I388aa5bf43235718668da109ebdb800e27b856d0 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-09-23meta-quanta: layer.conf: add zeus compatibilityPatrick Venture1-1/+1
OE-core master will be dropping warrior soon; zeus is the next release. (From meta-quanta rev: bee6771b647c0da99af4d06a3f60b7445d8427aa) Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I7c5f88138fffd3ef7649270bc2e44354450018a8 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-14meta-quanta: Remove references to QUANTABASEBrad Bishop2-2/+2
QUANTABASE 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-quanta rev: 170929b6044497d12e65a6a2c5e7025262c9d783) Change-Id: I12defd008e095db3227e5cd39261f942abd1406c Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-06update upstream subtreesBrad Bishop1-1/+1
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>
2019-04-06meta-quanta: layer.conf: Add warrior compatibilityPatrick Venture1-1/+1
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-quanta rev: 4f126361a17e37cfc96d5f9ccd5e3b81fa8b5ae2) Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I0a6cc767e787cef3d31d75b987b9369e44a7afc9 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-03-26meta-quanta: f0b: Update I2C hwmon paths for the 5.0 kernelPatrick Venture13-10/+10
In the 5.0 Linux kernel, an I2C device path segment changed: i2c@1e78a000 -> bus@1e78a000 (From meta-quanta rev: b57b3464ff116f009cc6771d7d2d87ae938bfa37) Tested: Verified paths visually, but not tested on hardware. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I9b2bf3480cc85d0cf9083c09ca8cd47b8d601f3e Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-02-01meta-quanta: Add meta-f0b machinePKLee-Quanta25-0/+530
Initial introduction of Quanta F0B family equipped with Aspeed 2500 BMC SoC. Tested: Build Quanta F0B board and load on the target hardware. Ensure that BMC boots to console. (From meta-quanta rev: b0d87650a1f20510596881a37c6a4424c6c5781a) Change-Id: Ieb5aad2f897dc8fb1840e0db2929b9350e3fa063 Signed-off-by: PKLee-Quanta <p.k.lee@quantatw.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
generated by cgit v1.2.3 (git 2.39.0) at 2024-06-30 15:41:34 +0300