Go to file
Pushpal Sidhu 68cabb954b ventana: Add self as board maintainer
Signed-off-by: Pushpal Sidhu <psidhu@gateworks.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2015-04-28 10:58:09 -03:00
conf ventana: Add self as board maintainer 2015-04-28 10:58:09 -03:00
recipes-bsp uboot-gateworks-imx: initial recipe for uboot 2015-04-22 16:51:46 -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-cubox-i: update SRCREV to ea83bda1b4 2015-04-24 15:20:17 -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