1. 18 Apr, 2018 2 commits
  2. 17 Apr, 2018 5 commits
  3. 16 Apr, 2018 6 commits
  4. 13 Apr, 2018 7 commits
  5. 12 Apr, 2018 6 commits
    • Matt Spinler's avatar
      Tell the mapper about IBM D-Bus paths · 602891b4
      Matt Spinler authored
      
      Add /com/ibm and com.ibm to the lists that the mapper
      uses to know what paths and interfaces to handle.
      
      As this is in the meta-ibm layer, it is only applied to
      IBM systems.
      
      Change-Id: I8c3624f4bff86af178b4d951632019d81dcaaf51
      Signed-off-by: default avatarMatt Spinler <spinler@us.ibm.com>
      602891b4
    • Matt Spinler's avatar
      Add ibm-dbus-interfaces recipe · b45c182e
      Matt Spinler authored
      
      These D-Bus interfaces are only for IBM systems.
      
      Change-Id: I62255887d9cb7059472ad33ccf6fddc84d476cf0
      Signed-off-by: default avatarMatt Spinler <spinler@us.ibm.com>
      b45c182e
    • Matt Spinler's avatar
      Enable recipes in meta-ibm/recipes-*/ · 1a626669
      Matt Spinler authored
      
      This is in preparation for adding recipes that
      are only for IBM systems.
      
      Change-Id: Id5be84d78c9a01fd2cf9dc2abb68cabfa6cedd51
      Signed-off-by: default avatarMatt Spinler <spinler@us.ibm.com>
      1a626669
    • Andrew Jeffery's avatar
      u-boot: Ensure we rebuild on change of VERSION_ID · 1cadf4c0
      Andrew Jeffery authored
      
      Systems utilising the obmc-ubi-fs DISTRO_FEATURE may fail to boot a
      freshly built image under some circumstances. Typically the error will
      be a mismatch in the u-boot environment between the value set in
      `kernelname` and the on-flash volume name for the kernel. They differ in
      the "Image ID" portion.
      
      The image ID is derived from the VERSION_ID field of `/etc/os-release`,
      and is currently added to the u-boot environment by sed-patching both a
      patch file adding the necessary information to the appropriate u-boot
      header, and the u-boot header itself.
      
      Why the current approach is wrong requires a bit of background on
      bitbake:
      
      1. bitbake tasks must be idempotent
      2. Building on 1, bitbake caches build state using stamp files
      3. bitbake tasks will not be re-run if a stamp exists and the task
         input state matches
      4. bitbake requires actions execute in the appropriate build phase
      
      To the issues:
      
      A. The sed-patching was performed by hooking the do_configure() task.
         This is wrong: There's a do_patch() phase whose purpose is to handle
         modifying the source tree, and will handle cache invalidation
         appropriately. The patch modifies the recipe to append the
         sed-patching to the do_patch() phase when the obmc-ubi-fs
         DISTRO_FEATURE is enabled.
      
      B. Sed-patching a patch is unnecessary. We can just sed the target file.
         By appending to the do_patch() phase we know the patches listed in
         SRC_URI have be applied, so drop any mangling of the patch. Note that
         as the existing approach hooked do_configure(), the source (including
         the patch) will not be redeployed, therefore the patch may remain in
         its mangled state.
      
      C. The search regex of the sed line only accounted for the case where
         the source was freshly unpacked and patched, and `kernelname` was
         assigned `kernel-0`. This will not be the case under a rebuild of a
         new commit to the OpenBMC repository that doesn't touch u-boot, as
         the source will not be redeployed due to the caching behaviour.
      
      D: We need an explicit dependency for the do_patch() phase on
         os-release:do_populate_sysroot to ensure that if os-release changes
         that we redo the patch phase to pick up the new image ID in the
         u-boot environment.
      
      The change addresses all of the issues outlined above.
      
      Change-Id: I01c95693053cb58aa0c0a90da04a03bca8eeec9e
      Signed-off-by: Andrew Jeffery's avatarAndrew Jeffery <andrew@aj.id.au>
      1cadf4c0
    • Jayanth Othayoth's avatar
      zaius: added "mutability" · 9c254ce3
      Jayanth Othayoth authored
      
      Added "mutability" flag to indicate if a sensor is READ/WRITE/RW.
      
      Change-Id: Ibe8913a0c72d8c97bdb9288a642901cea34f3a23
      Signed-off-by: default avatarJayanth Othayoth <ojayanth@in.ibm.com>
      9c254ce3
    • Andrew Geissler's avatar
      phosphor-ipmi-net.bb: bump version · e8073bab
      Andrew Geissler authored
      
      Change-Id: Ie1db920366e3104fe16ca1af6ca6b5e9fefea068
      Signed-off-by: default avatarAndrew Geissler <geissonator@yahoo.com>
      e8073bab
  6. 11 Apr, 2018 8 commits
  7. 10 Apr, 2018 6 commits