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
419 Commits 26 Branches 11 Tags 4 MiB
BitBake 89.5%
Shell 4.2%
PHP 3.5%
C++ 1.6%
HTML 1.2%
e07d1d11b9
Go to file
Tony Felice e07d1d11b9 mcc: Update MCC packages to be dual license (GPLv2 or BSD) 
Change the MCC packages to be licensed under either GPLv2 or BSD. This is
less restrictive than the previous GPLv2-only license for these packages.

Signed-off-by: Anthony Felice <tony.felice@timesys.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2015-12-04 13:18:10 -02:00
conf mqxboot: Add mqxboot version 1 2015-10-29 09:14:13 -02:00
recipes-bsp mcc: Update MCC packages to be dual license (GPLv2 or BSD) 2015-12-04 13:18:10 -02:00
recipes-core net-persistent-mac: Use the license text from common-licenses 2014-01-29 10:56:49 -02:00
recipes-kernel mcc: Update MCC packages to be dual license (GPLv2 or BSD) 2015-12-04 13:18:10 -02: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

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-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