Go to file
Vanessa Maegima 87223f2cc9 imx7d-pico: Add machine configuration
Add machine definition for imx7d-pico board.

For more information about this reference design, please visit:

https://www.wandboard.org/products/android-things/PICO-PI-IMX7/

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: Vanessa Maegima <vanessa.maegima@nxp.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2017-09-22 17:13:35 -03:00
conf imx7d-pico: Add machine configuration 2017-09-22 17:13:35 -03:00
recipes-bsp u-boot-congatec: Bump revision to 2a24305837 2017-08-30 10:13:49 -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-advantech: Add linux kernel patch for external WDOG_B support 2017-09-22 17:10:30 -03:00
.gitignore Initial skeleton 2012-04-27 15:20:53 -03:00
README README: Update to use new repository names 2016-10-21 16:19:26 -02: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-freescale 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-freescale-3rdparty

When creating a patch of the last commit, use

git format-patch -s --subject-prefix='3rdparty][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 'morty':

git format-patch -s \
--subject-prefix='3rdparty][morty][PATCH' -1