summaryrefslogtreecommitdiff
path: root/meta-ibm/meta-romulus/conf
AgeCommit message (Collapse)AuthorFilesLines
2023-11-25treewide: add scarthgap to LAYERSERIES_COMPAT2.16.0-devPatrick Williams1-1/+1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I28ee50fa55ae47dd7fd8c99f8f6db8f5f6dfa53d
2023-11-24treewide: add nanbield to LAYERSERIES_COMPATPatrick Williams1-1/+1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I85272779478b66452acd11be93f5fea99e4c3a34
2023-09-26linux-aspeed: Move to Linux v6.5Joel Stanley1-1/+1
This moves the OpenBMC kernel to a v6.5 base for ASPEED. The 6.5 kernel moved all 32-bit ARM device trees, so our BMC device tress are now under an 'aspeed' subdirectory. This change means systems must describe the KERNEL_DEVICETREE with the aspeed directory prefix. There are 78 patches in the tree, with 40 of those patches not yet queued for merging in v6.6. The remaining out of tree patches include: Andrew Jeffery (6): dt-bindings: hwmon: pmbus: Add Maxim MAX31785 documentation pmbus (max31785): Add support for devicetree configuration pmbus (core): One-shot retries for failure to set page pmbus (max31785): Wrap all I2C accessors in one-shot failure handlers ARM: dts: aspeed: witherspoon: Update max31785 node ipmi: kcs_bmc: Add a "raw" character device interface Cédric Le Goater (1): /dev/mem: add a devmem kernel parameter to activate the device Eddie James (16): ARM: dts: aspeed: bonnell: Add reserved memory for TPM event log dt-bindings: soc: Add Aspeed XDMA Engine soc: aspeed: Add XDMA Engine Driver soc: aspeed: xdma: Add user interface soc: aspeed: xdma: Add reset ioctl soc: aspeed: xdma: Add trace events i2c: core: Add mux root adapter operations iio: si7020: Lock root adapter to wait for reset eeprom: ee1004: Enable devices on multiple busses dt-bindings: trivial-devices: Add Atmel AT30TSE004A serial eeprom eeprom: ee1004: Add OF matching support leds: pca955x: Refactor with helper functions and renaming leds: pca955x: Use pointers to driver data rather than I2C client leds: pca955x: Optimize probe led selection leds: pca955x: Add HW blink support leds: Ensure hardware blinking turns off when requested Jae Hyun Yoo (1): clk: ast2600: enable BCLK for PCI/PCIe bus always Joel Stanley (14): net: ftgmac100: Ensure tx descriptor updates are visible ARM: aspeed: Add debugfs directory ARM: soc: aspeed: Add secure boot controller support dt-bindings: trivial-devices: Remove Infineon SLB9673 TPM ARM: dts: nuvoton: npmc750-evb: Add default console tpm: tis-i2c: Add more compatible strings leds: pca955x: Revert "Remove the unused function pca95xx_num_led_regs()" arm64: configs: Add Nuvoton NPCM defconfig ARM: configs: aspeed: Add new FSI drivers ARM: config: aspeed_g5: Enable SSIF BMC driver ARM: config: aspeed: Remove FIRMWARE_MEMMAP ARM: config: aspeed: Add Ampere SMPro drivers ARM: config: Add openbmc defconfig ARM: config: openbmc: Add HPE GPX and Nuvoton 7xx Johannes Holland (1): dt-bindings: tpm: Add schema for TIS I2C devices Potin Lai (1): mtd: spi-nor: winbond: Add support for w25q01jvq Change-Id: Ib97af192391af6e71c96fe14e12cfc88c23d7a7d Signed-off-by: Joel Stanley <joel@jms.id.au>
2023-01-13yocto:mickledore: add support for new yocto layerAndrew Geissler1-1/+1
Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
2022-10-19ibm: romulus: Set QB_MACHINEJoel Stanley1-0/+3
Romulus has a Qemu model called romulus-bmc. Change-Id: Iea41fc4fcfdb3cea8e2fb9dc286dfca2f304184f Signed-off-by: Joel Stanley <joel@jms.id.au>
2022-09-30add langdale to compatible layerAndrew Geissler1-1/+1
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-12ibm: romulus: Use v2019.04-aspeed-openbmc u-boot treeJoel Stanley1-4/+2
The OpenBMC u-boot tree now has support for the AST2500 based Romulus and can use a single configuration for NCSI and non-NCSI boards. Change-Id: I6daa155fcafa0128b119d67bf47cf629ac4b7977 Signed-off-by: Joel Stanley <joel@jms.id.au>
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 Williams1-1/+1
* Deprecate N-1 release (hardknott). * Enable N+1 release (kirkstone). Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
2022-01-25treewide: fix up github SRC_URIsPatrick Williams1-1/+1
Per [1], Yocto is going to start requiring both branch names and `protocol=https` in GitHub SRC_URI variables. Ran the upstream tool to automatically fix our URIs. 1. https://git.yoctoproject.org/poky/tree/documentation/migration-guides/migration-3.5.rst#n10 Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I5f9619f7ff707050b469ae74c8aa16846568c5e4
2022-01-18u-boot: Specify u-boot package for AST2500 machinesJoel Stanley1-0/+4
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>
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-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-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-11meta-ibm: Update local.conf.sampleAdriana Kobylak1-25/+65
Update with the latest version from upstream. Change-Id: I1a7da37b0457dab873afaf6445aca360d54b47ca Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-08-11meta-ibm: prep for new override syntaxAdriana Kobylak2-4/+4
Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
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-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/+2
This layer provides libseccomp. Signed-off-by: Anton D. Kachalov <gmouse@google.com> Change-Id: I84513d56f2ed75fab49043196b98ef8b858e394f
2021-02-20romulus: remove empty distro indirectionPatrick Williams2-3/+2
Most openpower machines use DISTRO="openbmc-openpower" but Romulus has a "openbmc-romulus" 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: I371ce4137369e4964eed1529f8a8190e31721ecc
2020-11-22meta-ibm: 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-ibm rev: 284e2ad06544f567582b2732a22e052190b5b95a) Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ic1cb74ebd387715b08feccd8b94bfd0be7d35205 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-11-03gatesgarth: add support for new seriesAndrew Geissler1-1/+1
As we add support for a new series, remove support for the oldest. Little to no testing is done with older ones. (From meta-ibm rev: 6255d23fd68023fdc838d0a2262b43883b86be58) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Id63754bdc8ec82628cad23427bfdadafca380c15 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-04-28meta-ibm: Remove references to vcs-workaroundJoel Stanley1-2/+0
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. All of the p9 systems in the tree exclude the package so this change should be a noop. (From meta-ibm rev: 38c5c9539fb3f01fc2b96d483701938bffdf48a0) Change-Id: I1c7786526dee4d9bb0d5db916890c1cbe3d51577 Signed-off-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-04-16dunfell: palmetto and romulus supportAndrew Geissler1-1/+1
(From meta-ibm rev: b2f780f527e156adff88c3c8e05fe87762266db6) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I523e93b55dd1333640ef7e84aa596b5efb06c4ca Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-11-04romulus: drop meta-ibm from build defaultBrad Bishop1-2/+0
Base hardware enablement support for meta-romulus is provided by meta-romulus and meta-openpower. meta-ibm adds advanced serviceability functions for IBM branded products backed by the IBM service structure. Romulus is a reference platform for ODMs and/or OEMS building POWER9 based systems. End users cannot purchase support contracts for Romulus systems. As such remove meta-ibm from the build configuration in the spirit of keeping the reference implementation mini and simplified. At a functional level this removes the ibm-logging application from images. Note that meta-ibm can always be re-integrated by simply adding it to bblayers.conf (From meta-ibm rev: c8cb279e0a8e9d941d8a73f04496a81e0efd5501) Change-Id: Ie657468f2566042c5faad9ae5a7923a2f9222564 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-10-05meta-ibm: layer.conf: add zeus compatibilityBrad Bishop1-1/+1
OE-core master will be dropping warrior soon; zeus is the next release. (From meta-ibm rev: 9c8d1b961e1185ab2e7eabf6f6b42754fcb57db0) Change-Id: I791f06ddb596584d1a566657a38ad6eb13692521 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-21meta-ibm: romulus: new YAML dependency schemeBrad Bishop1-6/+0
A prior patch added a new recipe romulus-yaml-config to provide all the YAML configuration for Romulus systems. This patch switches the layer to that recipe by setting EXTRA_OECONF and DEPENDS as appropriate in the required bbappends. With this switch, a number of recipes and their provided YAML are now dead metadata, so remove those. (From meta-ibm rev: 66ca8269544784908b0abf78715620adf04d69cc) Change-Id: I02305ec4c431122ae6ab440c5dcb3def509b7ff9 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-28meta-romulus: Fix ipmi configsLei YU1-2/+5
The ipmi configs were using .bbappends to override the default ones. There was a change in OpenBMC about overriding variable assignments, that causes the .bbappends not working anymore due to they are native. This commit fixes the issue, by adding romulus specific configs to replace the default ones. Tested: Verify the ipmi sensor, fru are correct on Romulus. (From meta-ibm rev: e020d0d8973cb4fa36d382bc9af5c056e8d8e913) Change-Id: If804ced6d53c8c4433351b982ebcf079cd014f56 Signed-off-by: Lei YU <mine260309@gmail.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-22meta-ibm: romulus: fans: drop unused variableBrad Bishop1-2/+0
meta-phosphor dropped support for native class config recipes and uses target class config recipes by default. Drop the reference to PHOSPHOR_FAN_CONFIG_USE_NATIVE_SYSROOT as it is no longer used in meta-phosphor. (From meta-ibm rev: 0bc0301510b3371510a86fa684b72ea4d4100cf1) Change-Id: I6b59b1429ead70c1e4ac85a1c9d66b3e04197dd5 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-21meta-ibm: romulus: fans: switch to non-nativeBrad Bishop1-0/+1
meta-phosphor recently enabled target class config recipes. Those are preferable to native class config recipes because native recipes cannot be overridden based on MACHINE, so switch to target class config recipes. Switching to target class recipes consists of temporarily setting PHOSPHOR_FAN_CONFIG_USE_NATIVE_SYSROOT to 0, overriding the phosphor distro default of 1. After all OpenBMC BSP layers have moved to target class config recipes PHOSPHOR_FAN_CONFIG_USE_NATIVE_SYSROOT can be removed from meta-phosphor and any BSP layers. Any references to -native recipes are replaced with their target class counterparts. Any -native bbappends are re-worked to apply to their target class counterparts. Finally, use BPN instead of PN when setting FILESEXTRAPATHS, to avoid unfortunate directory hierarchies if these bbappends are copy/pasted and then used to bbappend a native recipe. Since this patch moves to target class recipes, this is a noop; however, this avoids unfortunate directory hierarchies with native bbappends such as: meta-base/recipes-foo/bar/baz-native.bb meta-base/recipes-foo/bar/baz/a-file meta-append/recipes-foo/bar/baz-native.bbappend meta-append/recipes-foo/bar/baz-native/b-file Using "${THISDIR}/${BPN}:" enables a more sensible hierarchy: meta-base/recipes-foo/bar/baz-native.bb meta-base/recipes-foo/bar/baz/a-file meta-append/recipes-foo/bar/baz-native.bbappend meta-append/recipes-foo/bar/baz/b-file This behavior occurs because By default FILESPATH is set in base.bbclass (in OE-Core) to look for files in ${BP}, ${BPN} and files (and a number of subdirectories of those based on ${FILESOVERRIDES}). (From meta-ibm rev: 589ee00a5ec7bc97c7d5c079cf66b3dbd3ac2b4f) Change-Id: I1a593373f1b4bc82c554a9330cdd75f04f21d1d8 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-09meta-romulus: layer.conf: set BBFILE_PATTERNBrad Bishop1-1/+1
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: WARNING: No bb files matched BBFILE_PATTERN_foo-layer (From meta-ibm rev: 8b843642e36fc9d1ac8921a98dd2710dccf1e514) Change-Id: I5c6102045f5aaa6146dc1902b106063896d073b8 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-29meta-romulus: add occ-control-config-nativeLei YU1-0/+1
openpower-occ-control requires a sensor header file generated from occ_sensor.yaml. By default it uses an example yaml, which does not fit for Romulus. Add romulus-occ-control-config-native.bb to use its own occ_sensor.yaml, so that the package uses the correct config. Tested: Verify the build uses the correct config generated from Romulus's occ_sensor.yaml. (From meta-ibm rev: 54abf3c0be5618333cb37faebc55af48aa2a872b) Change-Id: Iaa3adf0d20e5b6d080866dd1b19fa3ee7f4d7369 Signed-off-by: Lei YU <mine260309@gmail.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-07meta-ibm: remove phosphor-isolation from witherspoon and romulusLei YU1-1/+0
The distro feature phosphor-isolation is added into openbmc-openpower distro feature and becomes common for all openpower machines. So remove them from meta-witherspoon and meta-romulus. This shall be merged after the commit of adding phosphor-isolation in openbmc-openpower is merged. Tested: Verify the Romulus build picks phosphor-isolation distro feature (From meta-ibm rev: 90f4ccb72200c26d13d3bbd70b6eb7cd90c3dff7) Change-Id: I8e64bee92eaa7c69928399ceedec6f889a713156 Signed-off-by: Lei YU <mine260309@gmail.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-05meta-ibm: layer.conf: Add warrior compatibilityBrad Bishop1-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-ibm rev: 97893b2c0bf39cfaee58ccfc4f85249f9a1d8abf) Change-Id: I2e772add384637011a80acf52861b88ac71be98b Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-02-06ibm: remove useless ibm.inc configuration fileBrad Bishop1-1/+1
ibm.inc simply includes openpower.inc. That, and meta-ibm is a distro policy layer and doesn't enable any specific hardware. Update machine configurations to include openpower.inc directly. Add a conf/distro/include/ibm.inc to meta-ibm at a later time when meta-ibm has distro policy to apply. (From meta-ibm rev: 3d1be91f99c646b350c02bfe1004a019cd436c13) Change-Id: I4bf1e9badba105f4ed10c478f7d5473e3f169791 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-02-05ibm: remove meta-webserver from bblayers.confBrad Bishop1-2/+0
With the recent move to bmcweb we don't need meta-webserver anymore. (From meta-ibm rev: a5231caf14dd78aa451621644bb60069eea17009) Change-Id: I92f760321d38f99e651e3a6ae4d689f0bfb337ff Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-11meta-romulus: Disable unnecessary hardware featuresAndrew Jeffery2-1/+3
(From meta-ibm rev: e98ac73825bddbd95a4b931073c4481fe535cff8) Change-Id: Ifb4a4e48c9767e1fb388e8f07b076cf55e92733d Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-09reset upstream subtrees to yocto 2.6Brad Bishop1-1/+1
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>
2018-12-18ibm: remove setting root pw from local.confBrad Bishop1-7/+0
With meta-phosphor commit fd1f696f99 this is done by the distro configuration; so, no need to do it in local.conf. (From meta-ibm rev: 0525b1723095b6c47af7892ca90f328f92270815) Change-Id: I6fdbf055b24adf768efdd86132faa7f1fffc56f9 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-11-20ibm: Remove unused meta-poky layerBrad Bishop1-2/+0
The meta-poky layer is unused. Remove from the layer configuration. (From meta-ibm rev: 7bafd24c1b15a87e25c5386236527c863908121f) Change-Id: Ia589ac6a06af433e8af8cb858ec1a91af962768b Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-11-09meta-ibm: romulus: set mrw licensePatrick Venture1-0/+2
Set the license fields for the machine-readable-workbook. (From meta-ibm rev: 7fc06531434db3ff03b148f7a8bd1925a094ec94) Change-Id: I0d494889f62de9804f61b8a97b118482bbe2868b Signed-off-by: Patrick Venture <venture@google.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-09-24meta-ibm: Rename bb file collectionsBrad Bishop1-3/+3
Typical upstream layers have a -layer suffix. Rename collections from foo to foo-layer to match this de-facto standard. Some existing layers that use this convention include: openembedded-layer networking-layer perl-layer virtualization-layer (From meta-ibm rev: 32478afb0f68ba711b816d1dbaecf379c67cc928) Change-Id: I5c22956cf289263d5cef1e3c1babb2d1f5a10a3d Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-08-23[Subtree] Bring openbmc machines to top levelDave Cobbley5-0/+290
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-08-24 22:30:40 +0300