Skip to content
BSP platform manifest
Branch: thud
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
README.adoc
default.xml

README.adoc

FSL Community BSP

To get the BSP you need to have repo installed and use it as:

Install the repo utility:

$: mkdir ~/bin
$: curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$: chmod a+x ~/bin/repo

Download the BSP source:

$: PATH=${PATH}:~/bin
$: mkdir fsl-community-bsp
$: cd fsl-community-bsp
$: repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b thud
$: repo sync

At the end of the commands you have every metadata you need to start work with.

To start a simple image build:

$: source ./setup-environment build
$: bitbake core-image-minimal

You can use any directory to host your build.

The source code is checked out at fsl-community-bsp/sources.

Contributing

To contribute to this layer you should send the patches for review to the mailing list.

When creating patches, please use something like:

$: git format-patch -s --subject-prefix='fsl-community-bsp-platform][PATCH][thud' origin

When sending patches, please use something like:

$: git send-email --to meta-freescale@yoctoproject.org <generated patch>

Using Development and Testing Branches

Replace the repo init command above with one of the following:

master

For developers

$: repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b master
master-next

For intrepid developers and testers

Patches are typically merged into master-next and then are merged into master after a testing and comment period. It’s possible that master-next has something you want or need. But it’s also possible that using master-next breaks something that was working before. Use with caution.

$: repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b master-next
You can’t perform that action at this time.