treewide: remove meta-poky usage

Upstream poky made a commit that adds an `/etc/motd` with a strong
warning that meta-poky is not intended to be used for production
purposes. There isn't anything w

treewide: remove meta-poky usage

Upstream poky made a commit that adds an `/etc/motd` with a strong
warning that meta-poky is not intended to be used for production
purposes. There isn't anything we use directly from meta-poky anymore,
so clean up all references to it.

See poky commit a226865c8683398b5f58628ba2ec5aee1ee6c19d for additional
context.

We could potentially switch from using the `poky` subtree to picking
up OECore directly, but right now it also provides us a qualified set of
OECore + bitbake.

Tested: Built yosemite4 and confirmed `motd` output is absent when
SSHing in.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I9c08650d2278b3ba26794c009adad3e593767f58

show more ...

treewide: handle upstream TEMPLATECONF move

The latest poky commit is requiring us to have all of
our template configs in a subdirectory instead of directly in
the `conf` directory. Without this we

treewide: handle upstream TEMPLATECONF move

The latest poky commit is requiring us to have all of
our template configs in a subdirectory instead of directly in
the `conf` directory. Without this we end up with errors during
setup like:

```
Error: TEMPLATECONF value (which is .../openbmc/meta-facebook/meta-bletchley/conf) must point to meta-some-layer/conf/templates/template-name
```

Fix this by moving all of our template files into the 'default'
template subdirectory (following the pattern of poky) and modifying
`setup` as necessary to follow.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iecefde73d55acbb6bc63ae3d68c4311adaf327ae

show more ...