[PATCH openbmc 09/10] AST2500: Initial AST2500 BSP layer

[Andrew Jeffery]

On Sat, 2016-06-04 at 00:20 -0500, OpenBMC Patches wrote:
>  5 files changed, 132 insertions(+)
>  create mode 100644 meta-openbmc-bsp/meta-aspeed/meta-ast2500/conf/layer.conf
>  create mode 100644 meta-openbmc-bsp/meta-aspeed/meta-ast2500/conf/machine/include/ast2500.inc
>  create mode 100644 meta-openbmc-bsp/meta-aspeed/meta-ast2500/recipes-kernel/linux/linux-obmc/defconfig
>  create mode 100644 meta-openbmc-bsp/meta-aspeed/meta-ast2500/recipes-kernel/linux/linux-obmc_%.bbappend
>  create mode 100644 meta-openbmc-bsp/meta-aspeed/meta-ast2500/recipes.txt

This might show my ignorance of Yocto, but what drives us to structure
the repository this way? Specifically, why are we nesting meta-aspeed
under meta-openbmc-bsp? Whilst OpenBMC is heavily centred around the
Aspeed SoCs, in general Aspeed SoCs are used by more than OpenBMC. It
feels like the OOP inheritance vs composition problem. Is that a fair
analogy? If so, should we try to flatten out this hierarchy a bit?

Cheers,

Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20160606/8269acc0/attachment.sig>