image_types_phosphor: Make rwfs name dependent

If we try and generate a `core-image-minimal` and `obmc-phosphor-image`
target in the same workspace we will currently encounter an error in
bitbake complaining about
```
obmc-phosphor-image-1.0-r0 do_image_complete: The recipe obmc-phosphor-image is trying to install files into a shared area when those files already exist. Those files and their manifest location are: rwfs.jffs2
```

This patch fixes the complaint by using a distinctly generated rwfs per
image type.

Change-Id: Ieb28f8b1c609c28eeceb7e19dc94c308d837c0d8
Signed-off-by: William A. Kennington III <wak@google.com>
1 file changed
tree: 11cce6e1c23ac89da2f03c6025f14dd291481d33
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. raspberrypi/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-graphics/
  11. recipes-phosphor/
  12. recipes-protocols/
  13. recipes-support/
  14. recipes-textproc/
  15. COPYING.apache-2.0
  16. COPYING.MIT
  17. LICENSE
  18. MAINTAINERS
  19. README.md
  20. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.