Go to file
Daiane Angolini 089ce85e2e imx6ul-pico-hobbit: Add machine configuration
For more information about this reference design, please visit:

http://www.technexion.com/products/pico/pico-som/pico-imx6-emmc

The machine configuration file used to include Yocto Project support to the
board is a consolidation work only.

It only reflects the work done in Linux kernel, U-Boot and FSL Community BSP,
where the hard work is actually done.

Signed-off-by: Daiane Angolini <daiane.angolini@nxp.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2016-05-17 17:03:32 -03:00
conf imx6ul-pico-hobbit: Add machine configuration 2016-05-17 17:03:32 -03:00
recipes-bsp u-boot-ge: Add u-boot recipe for GE i.MX6 boards 2016-04-23 11:55:14 -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-ge: Add linux kernel recipe for GE i.MX6 boards 2016-04-23 11:55:36 -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