forked from Freescale/fsl-community-bsp-platform
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
67 lines (41 loc) · 1.88 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
Freescale's Community Yocto 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 dora
$: repo sync
Once this has complete, you will have all you need. To start a build, do:
$: source ./setup-environment build
$: bitbake core-image-minimal
You can use any directory to host your build.
The source code will be checked out at fsl-community-bsp/sources.
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/fsl-community-bsp-platform
When creating patches, please use something like:
git format-patch -s --subject-prefix='fsl-community-bsp-platform][PATCH' origin
When sending patches, please use something like:
git send-email --to [email protected] <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 will break something that was working before. Use with caution.
$: repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b master-next