summaryrefslogtreecommitdiff
path: root/meta-ibm/meta-witherspoon/conf
AgeCommit message (Collapse)AuthorFilesLines
2020-04-27meta-ibm: move all meta-witherspoon metadataBrad Bishop7-169/+0
The metadata common to all IBM systems is confusingly split between meta-ibm and meta-witherspoon. Move everything to meta-ibm. The meta-ibm README is re-written to more accurately reflect the scope of the layer. Allow the configuration samples (bblayers.conf.sample, local.conf.sample) to be sourced from either meta-ibm or meta-witherspoon until such a time that any workflows and tooling have had the opportunity to move to meta-ibm. (From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442) Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-04-22Revert "tacoma: Build a wic image"Adriana Kobylak1-3/+1
This reverts commit 09415220c11012635c5de3e9e70ef17d1956ecc4. The layout of the wks file is still being worked out. (From meta-ibm rev: fea65fe4cf652ea9d207d114bc5be9cac4c5533a) Change-Id: I91e8b1b6397f090578b8cd548c0035616666477a Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-04-21tacoma: Build a wic imageAdriana Kobylak1-1/+3
Build a wic image with the zImage and device tree in the /boot partition. Rename the device tree to aspeed-bmc.dtb so that it's generic instead of having the machine name in the file. (From meta-ibm rev: 09415220c11012635c5de3e9e70ef17d1956ecc4) Change-Id: I0beb845d2de8a2b92d8f7300081054ab04265b52 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-04-21Revert "rainier and tacoma: Build u-boot spl"Adriana Kobylak2-4/+2
This reverts commit f2f334e6221b659934a8e72f5ca1aa8c9b8ae173. The u-boot openbmc spl defconfig is still in review: https://patchwork.ozlabs.org/project/openbmc/patch/1586370073-71433-1-git-send-email-anoo@linux.ibm.com/ (From meta-ibm rev: 5bea35bdaa05c736796bd1d0f22f0c7eaee9b484) Change-Id: I134d9044595c1e129d8b545ac4e4429a8a4d9f2b Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-04-14rainier and tacoma: Build u-boot splAdriana Kobylak2-2/+4
(From meta-ibm rev: f2f334e6221b659934a8e72f5ca1aa8c9b8ae173) Change-Id: I27c9d505b0699a2d1b1f58a8ce1349b17f15821a Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-04-14dunfell: add support for new layerAndrew Geissler1-1/+1
(From meta-ibm rev: 9508c70494a7d0ae3bd8f2a2fe662407ae642ad5) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ib03ada135194b8dffdd3982a98ff08bbbc131995 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-04-07tacoma: Build a mmc-ext4-tar imageAdriana Kobylak1-1/+1
The mmc-ext4-tar image is used for MMC code updates. (From meta-ibm rev: 4471bfb1798201d4b7f03912600474825034db0c) Change-Id: I9c26f9eebfccccce80eb405d8ddf9f7b59c34fd8 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-03-26witherspoon: Tacoma target should be full imageJoel Stanley1-1/+1
The commonly used target for Tacoma is to build obmc-phosphor-image. (From meta-ibm rev: 2789e4e691624911c9f570a9451518f7947a4e9e) Change-Id: Ie9e53df2127713cc467d85aafe2cd9f9aef2f7c5 Signed-off-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-03-19Add the rainier target to the targets in local.conf.sampleSunitha Harish1-0/+1
(From meta-ibm rev: c01884719907cf567e748bb00d6ebf3c13dbb1db) Signed-off-by: Sunitha Harish <sunithaharish04@gmail.com> Change-Id: I0c42518e03f06d06baec4a03095180e71508c065 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-03-17meta-ibm: Configure tacoma machine for new u-bootJoel Stanley1-1/+2
This selects the ast2600 openbmc u-boot configuration and the tacoma device tree. (From meta-ibm rev: b36b9ebc7f25a7d86d5c0e1cec81f156633921bd) Change-Id: I079fc3d82ae1a453719923c743f58dd2c529968d Signed-off-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-03-17meta-ibm: Configure rainier machine for new u-bootJoel Stanley1-1/+2
This selects the ast2600 openbmc u-boot configuration and the rainier device tree. (From meta-ibm rev: d3ed8678c77cd88a1953721b053f4fc6c1918fd1) Change-Id: Id97193d6f19e5e6b7e796880d13976417e79f92c Signed-off-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-03-12witherspoon-tacoma.conf: Build an ext4 imageAdriana Kobylak1-0/+2
Build an ext4 rootfs image for tacoma to be used in its eMMC chip. (From meta-ibm rev: 211b39b9b2de6bf558c03b9cf92824d3408a52b9) Change-Id: I45d6435b7caf7e3f28fc6a8a47a40bc62e96fb20 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-01-17Tacoma: add OBMC_POWER_SUPPLY_INSTANCESLei YU1-0/+2
Tacoma was missing the OBMC_POWER_SUPPLY_INSTANCES config, and thus the power supply monitor service will not start correctly. And with the change in https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/27463 the build will fail on constructing the rootfs. Fix it by adding OBMC_POWER_SUPPLY_INSTANCES in tacoma config. (From meta-ibm rev: 1f2b96d73f0117b9c07ce7e4beca0e1dfddfb8e2) Change-Id: I20f1ca81642bb1d594aa783ca3872b6bd08720da Signed-off-by: Lei YU <mine260309@gmail.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-11-07Rainier power supply presence detectsBrandon Wyman1-0/+2
Update rainier.conf to indicate the four power supply instances. Update bbappend for Rainier SYSTEMD_LINK and SYSTEMD_ENVIRONMENT_FILE. Add in subdirectory and power supply configuration files for GPIO presence detect of the Rainier power supplies. Use aspeed-gpio.sh from https://github.com/bradbishop/gpio-keys to determine gpio-key values. Use 7-bit I2C addresses on BMC. +-----+--------+----------+----+ | PSU | GPIO | gpio-key | AA | +-----+--------+----------+----+ | ps0 | GPIOS0 | 144 | 68 | +-----+--------+----------+----+ | ps1 | GPIOS1 | 145 | 69 | +-----+--------+----------+----+ | ps2 | GPIOS2 | 146 | 6a | +-----+--------+----------+----+ | ps3 | GPIOS3 | 147 | 6b | +-----+--------+----------+----+ (From meta-ibm rev: 3e8f174546cf440fda56ce47523030d4d403edbd) Change-Id: Ia55f80e4d857e7a477385d73c12f9719e3065f95 Signed-off-by: Brandon Wyman <bjwyman@gmail.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-10-24swift: Generate a mmc ext4 tar image fileAdriana Kobylak1-1/+1
Swift has an emmc chip, add the directive to generate a tarball for it. (From meta-ibm rev: 42c34123c54d5ebe407fbd7b87cc5ae6c75624a5) Change-Id: I263399cba325131be2d72d9ae2d3015050317d8f Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-10-17Extra argument to IPMI parsersSantosh Puranik1-0/+1
This commit adds an option to the invocation of IPMI MRW parsers within the IBM layer to allow them to parse an incomplete MRW. The extra option is only enabled for the Rainier machine. Tested: I updated rainier.conf to point to the in progress Rainier MRW and made sure that with the new option in the recipe, the IPMI parsers no longer complained about a broken MRW. (From meta-ibm rev: 7c056f4b459fa67dc911b40e14055b86dbf1ef46) Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com> Change-Id: I4482a09c93ab727b7330946f61e52a8ec92753fc Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-10-15ibm: rainier: remove witherpsoon, ac-server overridesBrad Bishop1-1/+0
Rainier mistakenly has witherspoon and ibm-ac-server machine overrides applied. Rainier is neither a witherspoon nor an ac-server (accelerated compute); remove so overrides approrpriate to those system types are not applied during a Rainier build. (From meta-ibm rev: c8e0f7ce18f89b09265ed4d2019f8a15999624a7) Change-Id: I3e931d032832bff0191eca2f4431e4bff1de2406 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-09-27ibm: tacoma: enable standard phosphor nor imagesBrad Bishop1-3/+3
Set the flash size so we get 128MiB images. Remove INITRAMFS and IMAGE_FSTYPES overrides so we get the standard phosphor images. (From meta-ibm rev: 1c12470b1ea14d6b043e0b214e800b974d10a36d) Change-Id: Ic941879b882aae809693a7901f3af95d23db5d05 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-27meta-ibm: Add rainier systemBrad Bishop1-0/+24
Rainier is a POWER system with an ast2600. Build instructions: TEMPLATECONF=meta-ibm/meta-witherspoon/conf . oe-init-build env MACHINE=rainier DISTRO=openbmc-openpower bitbake obmc-phosphor-image (From meta-ibm rev: 4c39d65a0b5678042a96324197c37478d81d6d4a) Change-Id: I4bf5424d99ea643f7262ae17c962d2b7dd280076 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-25mihawk-xml: srcrev bump b9929ba9fd..f6ec5aa0f9Ben_Pai1-1/+1
Change tpm connector instance name to prevent wrong name in bmc yaml file. (From meta-ibm rev: dad5e4f56d827cab311d9399a48bd09c26296f15) Change-Id: I919a8faadd3036b98215b76195602c1f8fb12435 Signed-off-by: Ben Pai <Ben_Pai@wistron.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-20Build full phosphor rootfs into witherspoon-tacomaAndrew Geissler1-0/+1
(From meta-ibm rev: fd1276f3a466058f0f0adbbbc6de889c0ceff9ac) Change-Id: I6d9db69525486e394a3e4757d3173284d0b07109 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-20meta-ibm: Add sample build invocationsBrad Bishop1-2/+12
Display sample build invocations when sourcing oe-init-build-env. These are only the most commonly used combinations of distro/machine/image and not an exhaustive list of all supported configurations. Rather the purpose of displaying these is to help bitbake newcomers quickly initiate a build without having to set DISTRO and MACHINE in local.conf or wonder which image recipe to bake. (From meta-ibm rev: 85057176dc1cee6ab5c78ca949f89e5cdb555bca) Change-Id: Ie16860278d9d779fa1d53025a29609ad45dcb94f Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-17Add Mihawk mac address syncAlvin Wang1-1/+4
(From meta-ibm rev: effd83bdc65d9ae8f9d000205f8d55e0c29557e4) Change-Id: I5d8fb1cd15e0b0bf2c2360631be8f259f42be98f Signed-off-by: Alvin Wang <alvinwang@msn.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-14meta-ibm: add tacoma systemBrad Bishop1-0/+24
The tacoma card is a boxelder replacement (witherspoon bmc card) with an ast2600 on it. By default use core-image-minimal as the initramfs. To add the full OpenBMC userspace set INITRAMFS_IMAGE="obmc-phosphor-image" in local.conf. Build instructions: TEMPLATECONF=meta-ibm/meta-witherspoon/conf . oe-init-build-env MACHINE=witherspoon-tacoma DISTRO=openbmc-openpower bitbake aspeed-image-norootfs (From meta-ibm rev: 77e917a89fd591bdc614aab362138f563460a316) Change-Id: I75374dbb3a01a66b2c70d96e56587a818262ebf8 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-10meta-ibm: Enable mac2 on mihawk platformBen_Pai1-0/+1
Since mihawk has share and dedicated two ports, so use two mac addresses. Tested:Use ip a command to see two mac addresses (From meta-ibm rev: ed92ee6fa8847511fbf2049e02ef3f8f0d7a7c70) Signed-off-by: Ben Pai <Ben_Pai@wistron.com> Change-Id: I43b3b78f7efd7e339e91bdc356283f6b9ffe1a5c Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-08-16witherspoon: Bump MRW versionAndrew Geissler1-1/+1
Pick up new IPMI clear sensor (From meta-ibm rev: 033ecca0a4321aba8000fd289c43aa38721255b2) Change-Id: I5c42bad754157bcae47463a1e8d6c0d1993e45d8 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-08-14Add mihawk platform to meta-ibmBen_Pai2-0/+39
The contents of this up-stream include the following items 1.Basic function 2.Led settings 3.GPIO monitor (id button and power supply) 4.Linux dts patch. (From meta-ibm rev: c53430a2234917b71f29d7e61d6aea749c45a2fc) Change-Id: Id0e47fd9197c8b2a70cbc94888bd572255664cdd Signed-off-by: Ben Pai <Ben_Pai@wistron.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-26Update swift mrw to latest versionAndrew Geissler1-1/+1
A lot of cleanup of IPMI sensors in this update (From meta-ibm rev: e80fecfd67ea850b6dba5af303e97ad7f8896ea6) Change-Id: Icd26b566002bf34b09b936300e89cd1a8fa4b9a5 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-24meta-ibm: add ibm-ac-server MACHINEOVERRIDEBrad Bishop1-0/+3
As of today the IBM(witherspoon) layer supports three of IBMs "Acclerated Compute" class of systems: witherspoon, witherspoon-128 and swift. Most of the bbappends are required for all three. Prior to this patch this was handled by bbappending without any override. This is counter to best practices and pollutes the metadata for layer users using recipes from meta-witherspoon. Add a new ibm-ac-server MACHINEOVERRIDE so that bbappends that work on all of IBM's AC systems can be overridden appropriately without having to explicitly list every system. (From meta-ibm rev: b770d19fc3e9774a1ad80be55b2f986d02847c26) Change-Id: I69ae41fa80612d1c019f031a02e32c01580b7939 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-24meta-ibm: witherspoon-128: MACHINEOVERRIDES fixupBrad Bishop1-1/+1
The ordering of the values in MACHINEOVERRIDES is wrong: MACHINEOVERRIDES="witherspoon-128:witherspoon" This means that: FOO_witherspoon = "bar" will override: FOO_witherspoon-128 = "baz" which is the opposite of expectation. The ordering is a function of config file include order and choice of the predot vs postdot operator. Use the same include ordering and dot operators as meta-fsl-arm to get the overrides to appear in MACHINEOVERRIDES in the correct order such that the expected semantics are provided and: FOO_witherspoon-128 = "bar" will override: FOO_witherspoon = "baz" (From meta-ibm rev: a12ff8392546591d8b52927da983dd76d2c0f1bd) Change-Id: I823e236bd0147cc058052d85778b522e74fabb28 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-23meta-ibm: local.conf.sample: add other machinesBrad Bishop1-0/+2
Do what poky does and add a (commented out) MACHINE entry for each supported machine. MACHINE=witherspoon remains the default. This makes is clear to anyone looking at local.conf.sample what machines are supported by the layer. (From meta-ibm rev: 275e64f3c4b4b6c6b84985f8000c3def18d1da0d) Change-Id: I83bd116e137aa9380a95abe5069f1a9c21df6983 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-11swift.conf: Build an ext4 imageAdriana Kobylak1-0/+2
Build an ext4 image for swift to be used in its eMMC chip. Tested: An ext4 image was built in addition to the current ubi ones. (From meta-ibm rev: 59bef037b63a73626434bfbfa22e1a53ca7133cd) Change-Id: I102b821754e2dd4998797f29bb935bd69324e8a3 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-04Swift: Bump MRW versionMatt Spinler1-1/+1
Pick up a change that assigns types to the panel and VRM cards so gen_openpower_fru.pl can find them when looking for VPD. (From meta-ibm rev: 318efca67822aa625b6868bcb08508e7695c5bf3) Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I26537326fb1fe0e653d3c7c470710c8a93cafb5e Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-29witherspoon-128: Use ${MACHINE} for device tree file nameAdriana Kobylak1-1/+1
Replace "witherspoon-128" with ${MACHINE} for the device tree file name as it's better practice to use bitbake variables instead of hard-coding values. Tested: Output of "bitbake obmc-phosphor-image -e": # pre-expansion value: # "${KMACHINE}-bmc-opp-${MACHINE}.dtb" KERNEL_DEVICETREE="aspeed-bmc-opp-witherspoon-128.dtb" (From meta-ibm rev: 8bbd213225ea5d6e3d1eb8537308f398dc85b6a2) Change-Id: I46e72947ddf47d3cbc20ab04f2b949ee717423cf Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-29swift: Point to swift's kernel device treeAdriana Kobylak1-3/+1
The kernel device tree for swift has been merged upstream. Tested: Output of "bitbake obmc-phosphor-image -e": # pre-expansion value: # "${KMACHINE}-bmc-opp-${MACHINE}.dtb" KERNEL_DEVICETREE="aspeed-bmc-opp-swift.dtb" (From meta-ibm rev: b652e467727899419334e6bf8b5b63e3a4150b56) Change-Id: Ib7f4063234d1412bdbeb01044947d92c75df704e Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-23swift: Increase read-write volume to 32MBAdriana Kobylak1-0/+5
Swift will be using UBI for its filesystem. Since it has 128MB flash chips, increase the size of the read-write volume to 32MB, same as witherspoon-128. (From meta-ibm rev: af07bab16662383dbf01ed4b7fae5083e66ae357) Change-Id: I631c69791e67f29903ae1e2377fc4414f33a0317 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-22meta-ibm: witherspoon: fans: drop unused variableBrad Bishop1-1/+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: bed9adaf6d89aa2ac42b91c06e4ee4be4e17c40e) Change-Id: I3cd896636924a59ecebd0eb25cad261f1bc070ab Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-21meta-ibm: witherspoon: fans: switch to non-nativeBrad Bishop1-2/+3
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: 6587e6ca03ca50411bc11cf87b5e11971dfe343f) Change-Id: Ib2c3f0052c1e01a84416da2eb868a54d8810e750 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-10witherspoon-128: Add witherspoon MACHINEOVERRIDESAdriana Kobylak1-0/+1
The witherspoon and witherspoon-128 machines are mostly the same. Add "witherspoon" as a MACHINEOVERRIDES to witherspoon-128 so that machine-specific features that apply only to witherspoon, including file paths, can be added to both flavors of witherspoon automatically. Tested: Built witherspoon and witherspoon-128, flashed images on HW and verified witherspoon powered on. (From meta-ibm rev: 6f44bb26247289aa46c6d21f04617838e596294a) Change-Id: I18ce6dd799cb0ab52b37f1f1f3d64c6189af4cd8 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-05-09meta-witherspoon: 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: ef6380a81fbd701b1052c12c8163498ba4e2de89) Change-Id: I1f4ab259befb094983df056c0f0f81cf8dc6f2e3 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-26Point to the real Swift MRWMatt Spinler1-3/+2
Tested: The image builds. The generated files look like a good start at least. (From meta-ibm rev: affeacabade12b73a4e009c7dd15d1f261db8528) Change-Id: Id80835c09cde4e6b61d40634406c3fa0e3752097 Signed-off-by: Matt Spinler <spinler@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-25meta-swift: Initial commitAdriana Kobylak1-0/+14
Create a new machine for Swift, a POWER9 system. It is initially based on Witherspoon but with 128MB NOR flash chips. - To build this machine: export MACHINE="swift"; \ export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE MACHINE"; \ bitbake obmc-phosphor-image (From meta-ibm rev: 12b1187ecfcf7d6438cb026d09f2c1b7c6e06cbc) Change-Id: I304ae026e1b2e027776981865b3f483d0898000f Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-25witherspoon-128: Initial commitAdriana Kobylak1-0/+13
Create a machine/witherspoon-128.conf file to model a witherspoon system with 128MB flash chips. * New kernel device tree (witherspoon-128.dts). * Bigger read-write filesystem. Remove the default from the witherspoon layer (not needed as 6MB is the default) so that the size value can be overwritten by the witherspoon-128.conf. - To build this machine: export MACHINE="witherspoon-128"; \ export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE MACHINE"; \ bitbake obmc-phosphor-image Witherspoon-128 is a system based on Witherspoon but with 128MB flash chips. Create a device tree for this configuration. Since this system is just a bringup vehicle, the device tree will be carried as a patch instead of merging it in upstream linux. (From meta-ibm rev: 903fd3532aaa967ddc7124095304f50cd4c9557c) Change-Id: If02e8ad32fc2bff336d16c18513f2c238b28c28a Signed-off-by: Adriana Kobylak <anoo@us.ibm.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-10meta-witherspoon: Disable unnecessary hardware featuresAndrew Jeffery1-0/+1
(From meta-ibm rev: 3beaf3a6fad2bcd231eccc7c4a602c3627fac1de) Change-Id: Ifb877562ada116ce4012a7e314600e975c5e36c2 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>
generated by cgit v1.2.3 (git 2.39.0) at 2024-09-02 23:45:19 +0300