summaryrefslogtreecommitdiff
path: root/meta-asrock
AgeCommit message (Collapse)AuthorFilesLines
2022-10-14treewide: remove obmc-control-bmc package referencesPatrick Williams2-2/+0
This package is an old interface from 'skeleton' for which there are no users outside of an IBM IPMI OEM handler, but the package isn't even installed on any IBM machines. Remove all references to this package from the tree so that it can be further removed. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Icda5c156940450ab033365d7f93d5542d6646696
2022-09-30add langdale to compatible layerAndrew Geissler3-3/+3
Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I65febeeec11e6e5b40ee728f42cfbe77023dae1e
2022-09-09treewide: handle upstream TEMPLATECONF movePatrick Williams4-0/+0
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
2022-08-05treewide: Don't duplicate default extrausers configZev Weiss1-4/+0
phosphor-defaults.inc now automatically inherits extrausers and configures the default root/0penBmc account, so individual platforms no longer need to specify either explicitly. Signed-off-by: Zev Weiss <zev@bewilderbeest.net> Change-Id: Ic2b725f0eaadfafef67069449497e57438fa0fba
2022-07-29romed8hm3: Add phosphor-regulators configZev Weiss2-0/+43
The default configuration of the VRM that supplies the VDDCR_CPU supply rail (ISL96147) provides a voltage that's significantly too high; we need to twiddle some magic bits in a specific register to bring it into spec (no public documentation of this particular VRM is available as far as I've been able to find, unfortunately). Signed-off-by: Zev Weiss <zev@bewilderbeest.net> Change-Id: I44d607b827e0fc7c18b9c336e63d0188e0955fd1
2022-07-28meta-asrock: Add meta-romed8hm3Zev Weiss5-0/+95
This is a single-socket Epyc server board from ASRock Rack with an AST2500 BMC and a 64MB SPI flash for the BMC firmware. Signed-off-by: Zev Weiss <zev@bewilderbeest.net> Change-Id: I162036f9e27a949d0cf8a85f92206ee659d884eb
2022-04-12treewide: Update BB_DISKMON_DIRS useGeorge Liu1-4/+4
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
2022-02-26treewide: remove image-prelink bbclass usagePatrick Williams1-1/+1
Upstream has removed the image-prelink bbclass[1], so remove it from any local.conf.sample that still has it enabled. 1. https://git.openembedded.org/openembedded-core/commit/?id=857baaf9e3d181ca18264e85d90b899fd94acff9 Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I70f42f8816f5dea207fcf5c34837d6796b3f6bb6
2022-02-26treewide: support yocto kirkstone releasePatrick Williams2-2/+2
* Deprecate N-1 release (hardknott). * Enable N+1 release (kirkstone). Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
2022-02-22treewide: remove MAINTAINERSPatrick Williams1-45/+0
The MAINTAINERS files are no longer used and are out of date (references to IRC still exist in most of them). Remove them and rely on the OWNERS exclusively. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I0f5d2719ad97e218ce03c4503efe1b1c92ac455e
2022-02-15e3c246d4i: use VIRTUAL-RUNTIME variables for E-M & dbus-sensorsZev Weiss2-2/+3
This obviates the need to specify the packages explicitly in packagegroup-asrock-apps, and drops some chunky binaries from the image that weren't serving much purpose, saving 389K on the compressed rofs (about 2%). Signed-off-by: Zev Weiss <zev@bewilderbeest.net> Change-Id: Ieb4ef39fe8a9e6a0e3783e2710d7702fcd1654a5
2022-01-18u-boot: Specify u-boot package for AST2500 machinesJoel Stanley1-0/+3
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>
2022-01-05meta-asrock: Add Zev Weiss as maintainerZev Weiss2-0/+47
Signed-off-by: Zev Weiss <zev@bewilderbeest.net> Change-Id: I9c224ea0de69ea378732f40f3b4d9fe8964360b0
2021-12-02Remove BBLAYERS_NON_REMOVABLE variableAlexander Filippov1-11/+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-11-15e3c246d4i: enable phosphor-isolationZev Weiss1-0/+5
Without the patches enabled by this feature, the default e3c246d4i strapping leaves the AST2500's SuperIO enabled, which causes the host boot process to hang (POST code 0x9a). Fixes: #3820 Signed-off-by: Zev Weiss <zweiss@equinix.com> Change-Id: I45de4945ff7f3322ed87494ad2c7aa41ce345438
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-10-22e3c246d4i: enable x86-power-controlZev Weiss3-0/+106
The config has a slight hack regarding the SioPowerGood/PowerOk signals (as explained in a comment in the file). The O_PWROK GPIO line perhaps "should" be the SioPowerGood signal, but we also don't have SioOnControl, so power-control disables its SIO support anyway, and using O_PWROK as PowerOk seems to work alright. Signed-off-by: Zev Weiss <zev@bewilderbeest.net> Change-Id: Ie3ef974e7edc172c82f63cb0129d90d098b15906
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-16meta-e3c246d4i: Add obmc-console configurationArthur Heymans2-0/+4
Allow to read the host console output via SOL. Change-Id: I249dcf485bcc34bb7c461feece8999240a33faa1 Signed-off-by: Arthur Heymans <arthur.heymans@9elements.com> Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
2021-09-16meta-asrock: catch up with yocto updatesZev Weiss4-10/+10
Override variable syntax change, honister compat, and a CONF_VERSION bump. Fixes openbmc/openbmc#3816. Signed-off-by: Zev Weiss <zev@bewilderbeest.net> Change-Id: Ia41d159d8118e5dba4b213bb0f7c2d61753c8ad3
2021-08-24treewide: remove gategarth from layer-supportPatrick Williams2-2/+2
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-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-05-24e3c246d4i: add initial board supportZev Weiss9-0/+320
The e3c246d4i is an ASRock Rack Xeon E-2100/E-2200 series board with an ASpeed AST2500 BMC. It's a relatively low-cost system with a SPI flash header available for easy programming. Signed-off-by: Zev Weiss <zweiss@equinix.com> Change-Id: I67ee57183215f3dd46b38f81994faeac8a1935c0