MIRRORS/meta-freescale-3rdparty
1
0
Fork 0
mirror of https://github.com/Freescale/meta-freescale-3rdparty.git synced 2025-07-19 12:09:01 +02:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
531 Commits 26 Branches 11 Tags 4 MiB
BitBake 89.5%
Shell 4.2%
PHP 3.5%
C++ 1.6%
HTML 1.2%
79b9c97f25
Go to file
Otavio Salvador 79b9c97f25 nitrogen6x: Add wic image tool support 
The wic image needs to install the bootscript and it loads the
respective kernel image and device-tree files from the image, thus
those need to be included.

Change-Id: If58ef5a51a5016761f04fbf5b20aaabf903a22ea
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2017-03-27 16:41:30 -03:00
conf nitrogen6x: Add wic image tool support 2017-03-27 16:41:30 -03:00
recipes-bsp u-boot-boundary, u-boot-script-boundary: Bump revision to cf2b52b5d9 2017-03-22 20:34:24 +00:00
recipes-core net-persistent-mac: Use the license text from common-licenses 2014-01-29 10:56:49 -02:00
recipes-kernel linux-toradex: update stable 4.1 kernel 2017-03-17 17:10:49 -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

README

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