| commit | 8b3d81d7cd9dd0254c3b03dddad18b9e74d2975d | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Wed Apr 29 10:53:34 2020 -0500 |
| committer | Andrew Geissler <geissonator@yahoo.com> | Wed Apr 29 13:41:25 2020 -0500 |
| tree | b2291bec1f148d00817436b2d9f4b1b747591a0d | |
| parent | e63dd680abed78dc2b2126c6fcbf3497c35ae18b [diff] |
dunfell: move u-boot.inc into aspeed layer The latest upstream of oe-core has diverged to the point where the meta-aspeed layer can no longer utilize the shared u-boot.inc In particular it has introduced a new, buildable config file, u-boot-initial-env, which is referenced throughout the u-boot.inc file now. The best solution is that OpenBMC upstream the changes it requires for u-boot but resource constraints have prevented that. The current hybrid approach of using a 2016 version of u-boot, pointing to source code in openbmc/u-boot but continuing to use the upstream u-boot.inc really doesn't buy much and causes maintenance issues like we're seeing here. Best to just pull the working version into meta-aspeed and just cherry pick in the one change OpenBMC needs which is the move to python3. The python3 move will be in the next commit in this series. The u-boot.inc used here was from poky with this sha: 9052e5b32a0dbc810782be4963e775609b8dcc04 Resolves openbmc/u-boot#24 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I6bd62bf224555f792dadf2063345c9750a5af8a6
This layer provides support for Aspeed's platforms for use with OpenEmbedded and/or Yocto.
This layer depends on: URI: git://git.openembedded.org/openembedded-core layers: meta branch: master revision: HEAD
meta-aspeed patches are reviewed using the Gerrit instance at https://gerrit.openbmc-project.xyz.
Please submit patches to Gerrit. More information on using Gerrit can be found here. https://github.com/openbmc/meta-aspeed is a hosting mirror only and GitHub pull requests are not monitored and will not be accepted.
Patch checklist. Please ensure patches adhere to the following guidelines:
For questions or help please come join us on the mailing list or in IRC.