summaryrefslogtreecommitdiff
path: root/meta-evb/meta-evb-nuvoton
AgeCommit message (Collapse)AuthorFilesLines
2024-03-22treewide: remove meta-poky usagePatrick Williams1-1/+0
Upstream poky made a commit that adds an `/etc/motd` with a strong warning that meta-poky is not intended to be used for production purposes. There isn't anything we use directly from meta-poky anymore, so clean up all references to it. See poky commit a226865c8683398b5f58628ba2ec5aee1ee6c19d for additional context. We could potentially switch from using the `poky` subtree to picking up OECore directly, but right now it also provides us a qualified set of OECore + bitbake. Tested: Built yosemite4 and confirmed `motd` output is absent when SSHing in. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I9c08650d2278b3ba26794c009adad3e593767f58
2024-02-07meta-nuvoton: trusted-firmware-a: fix the version at v2.9.0Tim Lee1-0/+1
Currently, openbmc upstream already update tfa to version v2.10.0 For compatibling with latest openbmc, we need to fix the version at v2.9.0. Otherwise, we will meet this kind of build error from upstream. ERROR: No recipes in default available for: openbmc/meta-nuvoton/dynamic-layers/arm-layer/recipes-bsp/ trusted-firmware-a/trusted-firmware-a_2.9.%.bbappend Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: If652ee5478cc9c42e833dd4d2a203d7d5ebddca1
2024-02-06meta-evb: meta-evb-npcm845: fix build warning for this layerTim Lee1-0/+2
There is build warning as below: WARNING: No bb files in default matched BBFILE_PATTERN_evb-npcm845 Due to there is no any bb files in meta-evb-npcm845 layer now. Add this BBFILE_PATTERN_IGNORE_EMPTY to allow those layers has no bb files then clear this kind of WARNING messages. Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: Ic266ce77e9dff1e068f0c3813f0a0717b2a99c1e
2024-01-22meta-nuvoton: move all the other recipes from meta-evbTim Lee3-127/+0
Make clean meta-evb layer back to description of OpenBMC EVB layer. Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: Ia56fc7abfb46615c2150dd4e5acdff801e64a590
2023-12-12meta-nuvoton: adopt meta-evb-npcm845 from meta-evbTim Lee5-40/+1
Adopt meta-evb-npcm845 from meta-evb layer that make more clearer about the scope of evb layer's description. Tested: /openbmc$ . setup evb-npcm845 Common targets are: obmc-phosphor-image Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: Ib922057b5bce54b864f1c0ced1b132ea1e71fd91
2023-11-25treewide: add scarthgap to LAYERSERIES_COMPAT2.16.0-devPatrick Williams3-3/+3
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I28ee50fa55ae47dd7fd8c99f8f6db8f5f6dfa53d
2023-11-24treewide: add nanbield to LAYERSERIES_COMPATPatrick Williams3-3/+3
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I85272779478b66452acd11be93f5fea99e4c3a34
2023-10-11treewide: clean up webui selectionPatrick Williams1-1/+0
The webui-vue package is now enabled by default. Clean up all the meta layers to clean up the explicit enablement. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I4895be56c70d2c8666dd96cec18d2c097f0c05a3
2023-07-05meta-evb-npcm845: enable sensors in dbus sensorsBrian Ma1-0/+5
There are temperature, adc, and fan sensors on EVB board, enable them. Change-Id: I533d4128e44ba8225356e80dcb74faa2fdaf07fb Signed-off-by: Brian Ma <chma0@nuvoton.com>
2023-06-28meta-evb-npcm845: host-postd: add postd daemon configurationTim Lee1-0/+1
Enable BIOS POST CODE functionality for Nuvoton BMC in postd. Need to add this configuration and fix daemon load failed. Due to default SNOOP_DEVICE is using Aspeed BMC. Failed log: lpcsnoop.service: Main process exited, code=exited ExecStart=/usr/bin/snoopd -b 1 -d /dev/aspeed-lpc-snoop0 (code=exited) Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: I3ec1c98787260e7a98f4a5135db0b9c5e23fc4af
2023-06-09meta-evb-npcm845: Add led manager configBrian Ma2-0/+34
Add len manager config for evb npcm845. Change-Id: I35429f01724fba4882ac2f60c11ba0cc732c743b Signed-off-by: Brian Ma <chma0@nuvoton.com>
2023-05-17evb-npcm845: packagegroup: remove nuvoton-ipmi-oemBrian Ma1-1/+0
Remote nuvoton-ipmi-oem from packagegroup due to the package is not exist in Openbmc. Change-Id: I90cd286f87cd485d1b406108736910e1766ef9a6 Signed-off-by: Brian Ma <chma0@nuvoton.com>
2023-03-03meta-evb: fix build warning for this layerTim Lee1-0/+1
There are some build warning message as below: WARNING: No bb files in default matched BBFILE_PATTERN_evb '' WARNING: No bb files in default matched BBFILE_PATTERN_evb-nuvoton '' Due to there is no any bb files in meta-evb and meta-evb-nuvoton layer. Add this BBFILE_PATTERN_IGNORE_EMPTY to allow those layers has no bb files then clear this kind of WARNING messages. Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: Ie845a2001b4e903975ab646ebe72aabd4f73e700
2023-01-13yocto:mickledore: add support for new yocto layerAndrew Geissler3-3/+3
Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
2022-12-21meta-evb-nuvoton: meta-evb-npcm845: add symbolic link of machine-confTim Lee1-1/+1
Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: I1a0355aa09cecca7dbcbcbeed8ad5b17d6a40b9f
2022-11-16meta-evb-nuvoton: add meta-evb-npcm845 layer for Arbel EVBTim Lee8-0/+179
Create meta-evb-npcm845 layer under meta-evb-nuvoton then make "setup" script looks for machine config files being present to know that the meta-layer contains a valid machine for OpenBMC. Also 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. Tested: /openbmc$ . setup evb-npcm845 Machine evb-npcm845 found in meta-evb/meta-evb-nuvoton/meta-evb-npcm845 Common targets are: obmc-phosphor-image Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: I21de23ded94244bed52c571a8e68b38cf498fc54
2022-09-30add langdale to compatible layerAndrew Geissler2-2/+2
Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I65febeeec11e6e5b40ee728f42cfbe77023dae1e
2022-09-12treewide: handle more upstream TEMPLATECONF movePatrick Williams1-0/+0
We also need to move the conf-notes.txt files. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ic44e015c0216b526de4fec277ad42f162bca1f33
2022-09-09treewide: handle upstream TEMPLATECONF movePatrick Williams2-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-04-30treewide: remove meta-perlPatrick Williams1-1/+0
The only recipes which use content from meta-perl are openpower machines: ``` meta-openpower/recipes-bsp/pdata/pdata_git.bb: libxml-libxml-perl-native \ meta-yadro/meta-nicole/recipes-phosphor/logging/openpower-esel-parser_git.bb: libxml-libxml-perl-native \ ``` Remove meta-perl from the bblayers of every layer except openpower machines. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I51f1a8fbfbe879295c64d2339fc115dbd8823681
2022-04-22treewide: drop unused meta-security layerBrad Bishop1-1/+0
This was added with cde0f094f for libseccomp, but shortly after that upstream moved libseccomp from meta-security to core (241c7d2e6). As such, meta-security is no longer used or required. Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Change-Id: I371e54b11f6336720dfc6edf0ef733d22b7fb4f2
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: 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
2021-12-02Remove BBLAYERS_NON_REMOVABLE variableAlexander Filippov1-14/+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-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-08-11meta-evb: increment CONF_VERSIONPatrick Williams1-1/+1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I2ca490f59630039696f7d1c8086520aa805a7e36
2021-08-11meta-evb: prep for new override syntaxPatrick Williams3-6/+6
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I7a755976c2144356314faef7cf1f226ae18dc884
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-12meta-evb-nuvoton: add symlinks for machine-conf for setupPatrick Williams1-0/+1
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
2021-04-06hardknott: yocto releaseAndrew Geissler2-2/+2
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-21meta-evb: update Yocto compat for gatesgarthPatrick Williams2-2/+2
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>
2019-06-13meta-evb-nuvoton: evb-npcm750: add warrior compatibilitykwliu2-2/+2
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>
2019-01-23meta-evb: evb-nuvoton: prepare for yocto 2.6Samuel Jiang2-2/+2
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>
2018-08-23[Subtree] Bring openbmc machines to top levelDave Cobbley6-0/+74
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>
generated by cgit v1.2.3 (git 2.39.0) at 2024-06-03 17:32:33 +0300