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
571 Commits 26 Branches 11 Tags 4 MiB
BitBake 89.5%
Shell 4.2%
PHP 3.5%
C++ 1.6%
HTML 1.2%
23df7dcb75
Go to file
Otavio Salvador 23df7dcb75 wandboard: Add Wandboard revision D1 support 
Latest Wandboard hardware revision is D1, which brings the following
new features:

 - PFUZE100 PMIC
 - AR8035 Ethernet PHY
 - Upgrade Wifi/BT chip to BCM4339/BCM43430

The new revision also adds support for QuadPlus SoC so the new Device
Tree is also added.

Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2017-10-05 13:51:39 -03:00
conf wandboard: Add Wandboard revision D1 support 2017-10-05 13:51:39 -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 wandboard: Revert device tree name change 2017-10-05 13:51:37 -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