Go to file
Fabio Estevam 11f10aa88c broadcom-nvram-config: Add entry for cubox-i
Add an entry for cubox-i in order to fix the following build error:

ERROR: Nothing RPROVIDES 'bcm4329-nvram-config' (but /work/yocto/master/sources/poky/meta/recipes-core/packagegroups/packagegroup-base.bb RDEPENDS on or otherwise requires it)
ERROR: bcm4329-nvram-config was skipped: incompatible with machine cubox-i (not in COMPATIBLE_MACHINE)

Also add the brcmfmac4329-sdio.txt file for cubox-i.

Change-Id: I91797c9122c97b2e17b780c5b5f523f9aa4edae3
Reported-by: Peter Bergin <peter.bergin@tritech.se>
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2015-07-03 14:40:18 -03:00
conf linux-wandboard: Bump kernel version to 3.14.28 2015-06-17 11:07:20 -03:00
recipes-bsp broadcom-nvram-config: Add entry for cubox-i 2015-07-03 14:40:18 -03:00
recipes-core net-persistent-mac: Use the license text from common-licenses 2014-01-29 10:56:49 -02:00
recipes-kernel linux-wandboard: Bump kernel version to 3.14.28 2015-06-17 11:07:20 -03:00
.gitignore Initial skeleton 2012-04-27 15:20:53 -03:00
README Update README to document proper handling of patches for other branches 2015-03-19 09:35:32 -03:00

OpenEmbedded/Yocto BSP layer for Freescale's ARM based platforms

This layer provides support for Freescale's ARM based platforms for use with OpenEmbedded and/or Yocto Freescale's BSP layer.

This layer depends on:

URI: git://git.openembedded.org/openembedded-core branch: master revision: HEAD

URI: git://git.yoctoproject.org/meta-fsl-arm branch: master revision: HEAD

Contributing

To contribute to this layer you should the patches for review to the mailing list.

Mailing list:

https://lists.yoctoproject.org/listinfo/meta-freescale

Source code:

https://github.com/Freescale/meta-fsl-arm-extra

When creating a patch of the last commit, use

git format-patch -s --subject-prefix='meta-fsl-arm-extra][PATCH' -1

To send it to the community, use

git send-email --to meta-freescale@yoctoproject.org <generated patch>

Patches are normally intended for the master branch.

Patches for other branches should be sent separately so they can be tracked individually in Patchwork and should have the branch name in brackets.

For example, use this to generate a patch for branch 'dizzy':

git format-patch -s \
--subject-prefix='meta-freescale][meta-fsl-arm-extra][dizzy][PATCH' -1