summaryrefslogtreecommitdiffstats
path: root/meta-phosphor/conf/machine
Commit message (Collapse)AuthorAgeFilesLines
* obmc-bsp-common.inc: Remove a number of varsBrad Bishop2018-06-151-8/+0
| | | | | | | | | | | | | | | | | | | | | | Begin to remove content from this non-sensical file. Any BSP configuration should be in a BSP layer, not the phosphor layer. KERNEL_EXTRA_ARGS: should be set by BSP, and this isn't required at all at the moment by the currently supported BSPs. UBOOT_SUFFIX: should be set by a BSP or distro configuration. MACHINEOVERRIDES: this was nonsensical in the bitbake sense - there is no such thing as an openbmc machine. If there is a need for an openbmc override in the future it can be added as a distro override (there is no such need at the moment). MACHINE_FEATURES_BACKFILL_CONSIDERED: BSPs should be considering backfilled machine features. Tested: Built witherspoon and palmetto images Change-Id: Idf252c92cb718d076ea556f2b389f15c13716fd2 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* Remove u-boot-fw-utils from IMAGE_INSTALLBrad Bishop2018-04-101-1/+0
| | | | | | | | | Install u-boot-fw-utils via dependency, rather than explicitly attempting to include it in all images. Tested: Built witherspoon, qemux86 images Change-Id: I371cb4b848d67d75816a6d0d3b35bc7615f2ec39 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* obmc-phosphor-image: Don't build .cpio.lzma.u-bootXo Wang2018-04-061-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For most incremental builds, the critical path is generating a new installed obmc-phosphor-image fs, then compressing it to put into a .lzma.u-boot container. However, the latter step doesn't seem necessary except for the out-of-kernel initrd (obmc-phosphor-initramfs) because obmc-phosphor-image is packaged as a squashfs-xz and not seen by U-Boot. qemu.inc has its own IMAGE_FSTYPE appends, so qemuarm builds should not be affected. This reduces incremental build time by about a third, when doing 'bitbake obmc-phosphor-image' with no changes. before: 150.74s user 66.01s system 148% cpu 2:25.96 total after: 94.78s user 64.87s system 159% cpu 1:39.97 total This reflects the removal of the single-threaded, CPU-bound 'lzma' invocation from the critical path. Netbootable images can still by generated by adding: IMAGE_FSTYPES += "cpio.${INITRAMFS_CTYPE}.u-boot" to local.conf. Signed-off-by: Xo Wang <xow@google.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Change-Id: I867500589ffe0a36cbe1193843907d7882239227
* Convert obmc-ubi-fs to a distro featureBrad Bishop2018-03-121-3/+3
| | | | | | | | | | | | | | | As with MRW the use of the UBI image scheme is distro policy. Convert the existing machine feature to a distro feature. Enable the new distro feature on the systems that use it(Witherspoon). Add a distro override and fix-up MF checks to use this override instead for improved readability. Tested: Built a Witherspoon image and validated image Change-Id: I8ab03115bbfc2ecc77cff5c9eb8628903ae88051 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* Enable ubi image fstype with obmc-ubi-fsBrad Bishop2017-08-181-1/+5
| | | | | | Change-Id: I06f511350e025144a8612c8077427a1d35cdfe10 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
* obmc-phosphor-image: remove initramfs if obmc-ubi-fs enabledPatrick Williams2017-08-181-1/+2
| | | | | Change-Id: Ie064ea9595742b78ccb7fe8a59c923b147ebfff6 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
* overlay: Prepare for multiple image typesBrad Bishop2017-08-181-1/+1
| | | | | | | | | | | | | | | | | | | More refactoring in preparation for ubi based mtd images. Promote tar file generation to a real image_fstype. This allows tar generation to be turned on or off as needed. Move image-overlay function to image_types_phosphor. Perhaps phosphor is not the best name but for now we only have a handful of image types and the generation logic is to interdependant to warrant seperate classes for each. Attempt to improve readability throughout. Drop ext4 override to discourage mtd block emulation. Change-Id: Idbdc03444549b955ef2180622d133904cb191b28 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* overlay: remove OBMC_PHOSPHOR_IMAGE_OVERLAYBrad Bishop2017-08-011-4/+1
| | | | | | | | | Solve the problem resulting in the addition of this variable differently, such that it can be removed and image type selection can be selected in the standard way using IMAGE_FSTYPES. Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Change-Id: Ice94e8f278f00b8b4d344244bfb87dddeb173a23
* overlay: Adopt upstream style conventionsBrad Bishop2017-08-011-3/+0
| | | | | | | | | | | | Removed a handful of unused variables. Use upstream style conventions, which seem to be: - pep8 for python - tabs for shellcode - 8 space indent everywhere else Change-Id: I4de549ecf02472096a54234379cd7cce8c219c48 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* image-overlay: Include initramfs in kernel FITRick Altherr2017-01-251-1/+1
| | | | | | | | Instead of packaging the initramfs separately in the flash image, use the FIT image that includes kernel+fdt+initramfs. Change-Id: I0a3315cfc635acbfaf7b603f5dca7da1ddeae1c1 Signed-off-by: Rick Altherr <raltherr@google.com>
* Build FIT images that include an initramfsRick Altherr2017-01-251-1/+2
| | | | | | | | | All the infrastructure is provided by upstream Yocto. The resulting FIT image includes (kernel+fdt+initramfs). This can replace image-overlay's manual inclusion of an initramfs in the flash image. Change-Id: I6f3580c5e564539960e287a9fae3161cb425a534 Signed-off-by: Rick Altherr <raltherr@google.com>
* Consolidate flash image generationRick Altherr2017-01-101-1/+1
| | | | | | | | | | | | | | | | | Before c7248eb11c and 794bd3d4ac, flash image generation was split between obmc-phosphor-image_types_uboot.bbclass and image-overlay.bbclass. This was because generate_flash() relied on calling oe_mkimage() which was also defined in obmc-phosphor-image_types_uboot.bbclass. With that dependency removed, all of the flash image generation can now be consolidated into image-overlay.bbclass. This location makes more sense as the .uboot image type is for generating U-Boot legacy ramdisks while the overlay image type is specifically for OpenBMC and its flash layout. obmc-phopshor-image_types_uboot.bbclass is now empty and has been removed. Change-Id: Idcf38d3ef6f419780a7c54c77f1195bf3b5f5667 Signed-off-by: Rick Altherr <raltherr@google.com>
* Only build FIT kernel imagesRick Altherr2017-01-091-2/+2
| | | | | | | | | | U-Boot has support for FIT images enabled. Yocto has been building both cuImage and fitImage for a while now. Dropping cuImage gets us closer to mainline Yocto. Using a FIT image clears the path for bundling the initramfs into the kernel image. Change-Id: I46f1e3d4196bab12b733c59efca40e9e50ca264d Signed-off-by: Rick Altherr <raltherr@google.com>
* No longer generate separate netboot image for obmc-phosphor-imageRick Altherr2017-01-041-1/+1
| | | | | | | | | | | | | | | | | The netboot image consists of the initrd and rootfs packaged together into a single U-Boot legacy ramdisk image. The initrd is already built as a U-Boot legacy image via INITRAMFS_IMAGE_TYPES. Similarly, the rootfs is already built as a U-Boot legacy image via IMAGE_TYPES. In getting rid of the redundancy, using built-in mechanisms is preferred over custom code thus netboot image is being removed. Note that removing the netboot image generation means the raw initramfs CPIO archive is not explicitly needed so it has been removed from INITRAMFS_IMAGE_TYPES. It will still be generated as the U-Boot ramdisk generation requires it as an implicit dependency. Change-Id: I0370ccc9575000de3238af07f7f14faa283edc15 Signed-off-by: Rick Altherr <raltherr@google.com>
* Use INITRAMFS_FSTYPES to build a u-boot ramdiskRick Altherr2016-12-221-1/+1
| | | | | | | | | | | | | do_generate_flash() was manually packaging the initramfs cpio archive as a u-boot ramdisk legacy image. Add the u-boot type to INITRAMFS_FSTYPES to use the existing infrastructure instead. NOTE: if you have an existing build directory, this change may cause the build to fail while creating symlinks. This is caused by the .u-boot file changing from an actual file to a symlink. Change-Id: I9fa69620f97452671f89675768b1d1f33dbe97f2 Signed-off-by: Rick Altherr <raltherr@google.com>
* Disable gobject-introspection to make openbmc build on ppc64leNan Li2016-12-121-0/+1
| | | | | | | | | | | | | | | | | As a known issue, the introspection data cannot be built on ppc64le. https://lists.yoctoproject.org/pipermail/yocto/2016-April/029582.html. To work around, I disable the use of qemu when we build openbmc by modifying the configuration files: Add MACHINE_FEATURES_BACKFILL_CONSIDERED = "qemu-usermode" to the end line. Resolve: openbmc/openbmc#640 Change-Id: Idb6584ca43a8d4f005aa365f62aa1d46d2a00fd5 Signed-off-by: Nan Li <william.bjlinan@hotmail.com>
* Build both cuImage and fitImage by defaultRick Altherr2016-11-081-2/+2
| | | | | Change-Id: I2333097ce2a17a2e2d932384373ccbae6724a861 Signed-off-by: Rick Altherr <raltherr@google.com>
* remove sample.inc include from local.conf.exampleBrad Bishop2016-09-141-7/+0
| | | | | | | | | | | | | | | | | sample.inc has been reduced to simply appending some server related machine features. For the sake of correctness, don't assume anything about the machine features desired to be simulated by the phosphor layer client. Accomplish this by removing sample.inc from local.conf(.sample). To simulate additional machine features on fake platforms like evaluation boards or the default qemu models, append additional features to OBMC_MACHINE_FEATURES in local.conf. Change-Id: I8bf3e0b428a3d0c20136340720aa500e1312607e Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* Move default providers to distro configBrad Bishop2016-09-141-9/+0
| | | | | | | | Move the fake, example implementations from sample.inc to phosphor-defaults. Other layers override as needed. Change-Id: Ic024b13c39bf1750f5c76bc0fac1d18092e8305d Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* Add host ipmi featureBrad Bishop2016-09-141-0/+1
| | | | | | | Add a distro/machine feature for Host IPMI. Change-Id: I873e5a37236ab408890e967109f16bc1926503be Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* host-ipmid: Convert providers to package groupBrad Bishop2016-09-141-5/+0
| | | | | | | | The desired providers were previously expressed in a virtual package. Move them to a packagegroup instead. Change-Id: I7343b64871b655dc7f567ecb8412b6b47b791d33 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* remove VIRTUAL-RUNTIME_xxx_ctlBrad Bishop2016-09-141-12/+0
| | | | | | | | These variables don't do anything functionally at the moment and the idea is better implemented with a packagegroup anyway. Change-Id: I026989df7a1169d44ff1a532731c97930c95d293 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* remove manager classesBrad Bishop2016-09-141-8/+8
| | | | | | | | | | | The value added by these classes is minimal and lowers the flexibility available to clients using them when it comes to packaging. Rename recipe virtuals - obmc-phosphor seems redundant. Align package virtual names with best practices (virtual-package). Change-Id: I34c3cb03f6b1d2aaa734ed02078b388667f70917 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* Remove policy distro featureBrad Bishop2016-09-121-1/+0
| | | | | | | | The policy feature doesn't have any meaning or definition at the moment so remove in an attempt to reduce clutter. Change-Id: I7edaeb3bc9ffb409e5f7dfeae424ffb94f6085fd Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* meta-phosphor: Make image-overlay an optional featurePatrick Williams2016-06-241-1/+1
| | | | | | | | | | | | | | | | Previously, obmc-bsp-common.inc added "overlay" to the IMAGE_FSTYPES but this only has meaning if the 'image-overlay' class is used. The obmc-phosphor-image class explicitly includes 'image-overlay' when appropriate but no other images (ie. ones that come with yocto) do. Changed obmc-bsp-common to instead enable an obmc-phosphor-image feature by setting OBMC_PHOSPHOR_IMAGE_OVERLAY=1. Then in obmc-phosphor-image we add "overlay" to the IMAGE_FSTYPES only when the feature is enabled. This will fix both non-phosphor images on hardware platforms and all images on simulation platforms. Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
* meta-phosphor: use obmc-phosphor-user for qemu systemsPatrick Williams2016-06-241-1/+1
| | | | | | | | Yocto 2.1 can't seem to find the original reference package obmc-phosphor-userd. obmc-phosphor-user is a full implementation that works on qemu, so we will use it. Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
* meta-phosphor: Use obmc-phosphor-event for qemu systemsPatrick Williams2016-06-241-1/+1
| | | | | | | | Yocto 2.1 can't seem to find the original reference package obmc-phosphor-eventd. obmc-phosphor-event is a full implementation that works on qemu, so we will use it instead. Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
* Add OBMC_IMAGE_EXTRA_INSTALL variableBrad Bishop2016-06-141-1/+1
| | | | | | | | | | | | | | | Prior to this patch packagegroup-core-boot was not being pulled in. core-boot is what brings in the init_manager (systemd) but somehow systemd was added as a dependency by OE for the skeleton package so the missing core-boot packagegroup went unnoticed. core-boot was not being pulled in because of an assignment to IMAGE_INSTALL in the global configuration. Yocto core provides a mechanism to do the same thing safely - CORE_IMAGE_EXTRA_INSTALL; use this and also adopt a similar approach for adding extra packages to image recipes using obmc-phosphor-image. Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* Build a tftpboot friendly image.Brad Bishop2016-04-211-0/+1
| | | | | Build a rootfs cpio uimage with everything along with the other images.
* Don't inherit image-overlay by defaultBrad Bishop2016-02-291-1/+0
| | | | | | | | | | | This attempts to address a race condition in the build where we attempt to build a complete flash image before all the sub-images are available (specifically the initramfs image). Any classes in IMAGE_CLASSES are inherited by all image recipes, including the initramfs image. OE-Core's live/hddimg recipes address this by pulling in the class configuration in recipe scope, rather than global scope. Copy that behavior here.
* Recipe update: User management, systemd patch, IPMI net functionsAdriana Kobylak2016-02-121-0/+1
| | | | | | Create virtual class to include user management in the image Add the systemd patch for network support to the systemd recipe Update the IPMI recipe to pickup the support for network configuration
* Add u-boot fw-utils to the imageMilton D. Miller II2016-01-281-2/+9
| | | | | | | | | | | This adds the u-boot-fw-utils package to the obmc phosphor bsp include file to include the fw_setenv and fw_printenv utilities in the image. This will allow us to read and update the u-boot boot environment including setting the mac address of the ethernet. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
* Add ipmitool for qemu image onlyChris Austen2015-11-051-0/+1
|
* Merge pull request #64 from causten/candidate3Patrick Williams2015-11-021-2/+1
|\ | | | | stop the build break for btbridge on qemu
| * stop the build break for btbridge on qemuChris Austen2015-11-011-2/+1
| | | | | | | | btbridge is not even part of the qemu image
* | Add ipmi fru write to dbusChris Austen2015-11-011-0/+1
|/ | | | x
* Added liboemhandler.so to the official buildChris Austen2015-10-281-0/+3
| | | | | Moved ipmi up to the latest level to allow the ipmid-api.h to be exported in the package fixed bb files to ensure RECCOMNDS do not get overwritten
* Remove example applications from build.Brad Bishop2015-10-211-0/+7
| | | | | | They can still be built. Not included in any images. Part 2 of 2 (meta-palmetto, meta-phosphor).
* Make host-ipmid pull in host IPMI to hw packageBrad Bishop2015-10-191-0/+2
| | | | Set preferred providers for palmetto and qemuarm targets.
* Use lzma compression for rootfsBrad Bishop2015-10-121-1/+1
| | | | This saves almost 30 percent.
* Use OpenBMC uboot imageBrad Bishop2015-10-081-1/+4
| | | | | This makes all machines use the OpenBMC flash image uboot image fstype specialization.
* Move Palmetto specific metadata to Palmetto layerBrad Bishop2015-10-061-0/+15
|
* Added sd-bus service exampleBrad Bishop2015-09-211-2/+2
| | | | | Added obmc-phosphor-example-sdbus. Added sdbus-service class for common logic.
* Refactor obmc-phosphor-qemuBrad Bishop2015-09-211-4/+4
| | | | | | Renamed to obmc-phosphor-example-pydbus. Prep for forthcoming sdbus example. Added signal example.
* Merge commit '0d2b029c7fbf4abaa0b34bfc4a8ea77bae71c624' into HEADPatrick Williams2015-09-162-5/+19
|
* Add 'meta-phosphor/' from commit '93fb535853a24d4c3c42ec425ac92c9d3de13294'Patrick Williams2015-09-151-0/+5
git-subtree-dir: meta-phosphor git-subtree-mainline: 21f9b84b4b729fbd7acbd465e7a3f726e4d20f91 git-subtree-split: 93fb535853a24d4c3c42ec425ac92c9d3de13294
OpenPOWER on IntegriCloud