at91bootstrap 3.6.2: allow custom targets

This way a MACHINE.conf can set it to non-default values.

Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Merge pull request #23 from koenkooi/at91bootstrap

at91bootstrap 3.6.2: allow custom targets
Change layer name

Conforming to OE/Yocto naming convention, the layer should not use the
meta prefix for BBFILE_COLLECTIONS and other layer-specific variables.

Signed-off-by: David Vincent <freesilicon@gmail.com>
Remove superfluous EXTRA_IMAGE_DEPENDS

Since files/bootloaders.inc is now required by every machine
configuration file, the EXTRA_IMAGE_DEPENDS found in sama5d3xek.conf
is not needed anymore.

Signed-off-by: David Vincent <freesilicon@gmail.com>
Create SoC include files

OE/Yocto offers the possibility to group some SoC features into a
SOC_FAMILY. This gives the possibility to group common overrides and
definitions and in a file to be included by all machines based on the
same SoC.

Signed-off-by: David Vincent <freesilicon@gmail.com>
Use correct FPU

OE/Yocto default configuration is not compatible with Atmel SAMA5D3x
FPU. Indeed, OE/Yocto uses a VFPv3 FPU whereas SAMA5D3x is a VFPv4-D16.

Signed-off-by: David Vincent <freesilicon@gmail.com>
Include file for SAM9x5EK

Some options are shared by all SAM9x5 Evaluation Kits, so we define an
include file to be used by each machine file.

Signed-off-by: David Vincent <freesilicon@gmail.com>
Use SAM9x SoC include files

Now that we have SoC files for SAM9x MPU family, use it for every
Atmel board defined in this layer.

Signed-off-by: David Vincent <freesilicon@gmail.com>
Include file for SAMA5D3xEK

Some options are shared by all SAMA5D3x Evaluation Kits, so we define
an include file to be used by each machine file.

Signed-off-by: David Vincent <freesilicon@gmail.com>
Use SAMA5D3x SoC include files

Now that we have SoC files for SAMA5D3x MPU family, use it for every
Atmel board defined in this layer.

Signed-off-by: David Vincent <freesilicon@gmail.com>
Create common recipe file

Create an include file for at91bootstrap recipe to have a common
configuration for all versions. This way, releasing a new version should
only result in a new recipe with an updated SRC_URI.

Also, keep only one recipe as recommended by the Yocto project :
https://wiki.yoctoproject.org/wiki/Best_Known_Methods_(BKMs)_for_Package_Updating

Signed-off-by: David Vincent <freesilicon@gmail.com>
Modify at91bootstrap recipe

The existing recipe was only compatible with Atmel boards. This new one
has been modified in order to make it more compatible with custom
boards.

A new board can simply be created by adding a defconfig file in the
SRC_URI of a custom BSP recipe.

Signed-off-by: David Vincent <freesilicon@gmail.com>
Fix build failure

Standard includes cause a build failure when compiling with a hard-float
toolchain. Since they are not needed, we can safely remove them.

Signed-off-by: David Vincent <freesilicon@gmail.com>
Deploy at91bootstrap image

Simplify deployment of at91bootstrap images by creating symlinks to the
final image. The deployment directory is also populated with symlinks to
point to the last generated image.

Signed-off-by: David Vincent <freesilicon@gmail.com>
Modify U-Boot recipes

Signed-off-by: David Vincent <freesilicon@gmail.com>