summaryrefslogtreecommitdiff
path: root/meta-inspur/meta-on5263m5
AgeCommit message (Collapse)AuthorFilesLines
2021-12-14meta-x86: remove layerPatrick Williams1-1/+0
This layer has nothing in it. The current direction is for anything architecture specific to end up in meta-phosphor. Remove this "layer" so that it doesn't keep getting copied into new machines. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ied03175589840490bcd1eda8c704c73e224ba9a9
2021-11-04Partially revert "treewide: remove obmc-system-mgmt feature"Patrick Williams2-0/+3
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>
2021-10-26treewide: remove obmc-system-mgmt featurePatrick Williams2-3/+0
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
2021-09-16treewide: fix comments for rpm/ipkPatrick Williams1-1/+1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ia05891430c6c97a89b7bc8ba4558ae496866bf7d
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-08meta-inspur: Yocto override syntax changeGeorge Liu1-5/+5
Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I2b967fb31d9930074df17c108d06cfed489d1cf7
2021-09-02meta-phosphor: change systemd.bbclass to match upstream override syntaxPatrick Williams1-1/+1
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-19meta-inspur: on5263m5: Switch webUI to webui-vueGeorge Liu1-1/+1
Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I3ecba17a12ac6da02ac86bca3141b1da6d54fbbc
2021-08-12meta-inspur: Update CONF_VERSIONGeorge Liu1-1/+1
Since the upstream CONF_VERSION has been changed to 2, Need to sync the CONF_VERSION of the inspur layer. Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I539f6a4033933b728131a684163a9ff6a58fdec7
2021-08-12meta-inspur: honister: Compatible yocto releaseGeorge Liu1-1/+1
Latest upstream yocto has moved on to the 3.4 honister release. Compatible with honister for all inspur machines. Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I991415cb0db971d553eb374b7df8f634b00f4816
2021-08-12meta-inspur: Cleanup for Yocto override syntax changeGeorge Liu5-25/+25
Refer to: https://lore.kernel.org/openbmc/YQ1FD5q8KbhbXVBK@heinlein/ ``` poky/scripts/contrib/convert-overrides.py meta-inspur git grep "_[a-z0-9_/-]*[ :]" -- meta-inspur | grep ".bb" git grep -l _fp5280g2 -- meta-inspur | xargs sed -i \ 's/_fp5280g2/:fp5280g2/' git grep -l _on5263m5 -- meta-inspur | xargs sed -i \ 's/_on5263m5/:on5263m5/' git grep -l _virtual -- meta-inspur | xargs sed -i \ 's/_virtual/:virtual/' ``` Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I5ef5039691caf5e33fb865da0fdd70d95d7e3bdf
2021-08-10Remove redundant code to set root passwordJoseph Reynolds1-4/+1
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
2021-06-07treewide: Remove obsolete image-mklibs classWilliam A. Kennington III1-2/+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/+1
This layer provides libseccomp. Signed-off-by: Anton D. Kachalov <gmouse@google.com> Change-Id: I84513d56f2ed75fab49043196b98ef8b858e394f
2020-11-30meta-inspur: update Yocto compat for gatesgarthGeorge Liu1-1/+1
Since the current release of Yocto is gatesgarth, Add and support for gatesgarth(current) and dunsfell(previous) in meta-inspur layer. Also, remove the two earlier releases(warrior and zeus). Tested: Built successfully on fp5280g2 and on5263m5. (From meta-inspur rev: 831b68cce11da461122ee20ad371d93b60a245b1) Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I587a032a20bb645c452d16fbdc8adff3d35c965a Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-05-06meta-inspur: layer.conf: add dunfell compatibilityGeorge Liu1-1/+1
Tested: Built successfully on fp5280g2 and on5263m5. (From meta-inspur rev: 9f97e52a7b7f5366732be3ffd73e08266f67dbb2) Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: I55333bd59c44c6280ad54b07c164e74b5eb39a76 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-09-23meta-inspur: layer.conf: add zeus compatibilityJohn Wang1-1/+1
(From meta-inspur rev: de520bd0ba379715784a0060ca941c3c272d6054) Signed-off-by: John Wang <wangzqbj@inspur.com> Change-Id: I4e64add8166b48b3528473a1ef86fcde5c3dc550 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-05meta-inspur: Move recipes under meta-commonJohn Wang8-139/+80
Since meta-common is an x86 platform related meta, it would cause ambiguity if other platform related machines are created. In order to avoid ambiguity, recipses under meta-common are moved to meta-on5263m5, the meta-common folder is deleted. Tested: export TEMPLATECONF=meta-inspur/meta-on5263m5/conf source openbmc-env bitbake obmc-phosphor-image Build successfully (From meta-inspur rev: 295f5c5f6fbec43e8d5727e9a50dcba58e951cbd) Signed-off-by: John Wang <wangzqbj@inspur.com> Change-Id: Iffacaf8131ec83362ec453a51818f6901f1f80e5 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-30on5263m5: set layer compatability to thud&warriorJohn Wang1-1/+1
(From meta-inspur rev: 92714432cefa85eec0d76da5ef6a40b884869d6e) Signed-off-by: John Wang <wangzqbj@inspur.com> Change-Id: I62d42717772b12aa0246cb59f7db480a6441ff8c Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-03-26meta-inspur: on5263m5: Update I2C hwmon paths for the 5.0 kernelPatrick Venture4-3/+3
In the 5.0 Linux kernel, an I2C device path segment changed: i2c@1e78a000 -> bus@1e78a000 (From meta-inspur rev: 92609a93bf06ff5f71983595cf7edc4523676043) Tested: Verified paths visually, but not tested on hardware. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I37efb06fe1b59a69939560c7aba71e17354b2b81 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-15meta-on5263m5: Add sensor configsJohn Wang6-0/+52
tmp421 tmp112 adm1278 adc fan-tach Tested: Build on5263m5 board and load on the target hardware (From meta-inspur rev: cfb537ae3d5d9f4e0ca922880752dbf472cb6801) Change-Id: Ide9f3ea2314f518c2381b2258dbe97af04d14a9e Signed-off-by: John Wang <wangzqbj@inspur.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-15Add obmc-bsp-common.incJohn Wang1-0/+1
Without obmc-bsp-common.inc in machine/on5263m5.conf, it seems that the image-bmc can not be generated, so it is added Tested: export meta-inspur/meta-on5263m5/conf and build obmc-phosphor-image, verify the images are built (From meta-inspur rev: af5f1ab12b97dca39722f9056ad57d8e723871e9) Change-Id: Ica691390859cdb88159f6a2232a5fb6327c32db7 Signed-off-by: John Wang <wangzqbj@inspur.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-12-13Add ON5263M5 platformJohn Wang9-0/+421
(From meta-inspur rev: 42e8cb80b7e8344ce9fb6ff0c40f81e0bdd03cbe) Change-Id: I8affa38b64d7db1f4826718983d049dea5ea2f26 Signed-off-by: John Wang <wangzqbj@inspur.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
generated by cgit v1.2.3 (git 2.39.0) at 2024-06-29 07:10:43 +0300