emmc-unavailable: move to common recipe

We see that platforms without TH enabled, failed eMMC Lock because of
missing this target.

It's better to have this target just moved to emmc-available.bb which is
there as long as a platforms enables eMMC.

This does not affect platforms with TH disabled. Just a new target is
there.

Tested: bitbake emmc-available and TH worked. Shouldn't affect any functionality
Google-Bug-Id: 464221969
Change-Id: If1ba3fe7c46a8976cf82743c57e2e3271f7dc1e9
Signed-off-by: Nan Zhou <nanzhou@google.com>
3 files changed
tree: 873e47e612ad5c36513c7455c57ba50ebc3d9f6f
  1. classes/
  2. conf/
  3. dynamic-layers/
  4. recipes-bsp/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-google/
  10. recipes-kernel/
  11. recipes-phosphor/
  12. recipes-support/
  13. recipes-tpm1/
  14. recipes-tpm2/
  15. LICENSE
  16. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.