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
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
|
OpenEmbedded BSP layer for Rockchip boards
About:
-----
The purpose of this layer is to provide OpenEmbedded BSP support for
Rockchip-based devices using upstream sources as much as possible.
Dependencies:
------------
URI: git://git.openembedded.org/openembedded-core
layers: meta
branch: matched branches (e.g. master, sumo, ...)
URI: git://git.yoctoproject.org/meta-arm
layers: meta-arm, meta-arm-toolchain
branch: matched branches (e.g. master, sumo, ...)
Status of supported boards:
--------------------------
builds and boots wic image:
nanopi-m4
nanopi-m4-2gb
rock-pi-e
rock-pi-4a
rock-pi-4b
rock-pi-4c
rock64
tinker-board
tinker-board-s
vyasa-rk3288
firefly-rk3288
nanopi-r4s
rock-5b
nanopi-r2s
nanopi-m4b
rock-pi-s
rock-5a
roc-rk3328-cc
roc-rk3308-cc
orangepi-5-plus
rock-3a
rock-4c-plus
builds:
marsboard-rk3066
radxarock
rock2-square
Notes:
-----
The latest ddr initializer for the rk3308 platform does not output
diagnostic messages to uart0. This causes a bunch of gibberish to
be printed to the console window which only becomes legible once
the linux kernel starts. I.e. the console output of the ddr
initialization routine, as well as u-boot is lost. An older
version of this same binary blob does, however, support output to
uart0 (making its diagnostic messages as well as u-boot available
on the console). By default the build assumes the user would like
to see these message and be able to have the option to interact
with u-boot.
IOW: for rk3308-based devices, an older version of rkbin is used.
If, however, the user would prefer to use the latest binary ddr
initializer from rkbin, simply set:
RKBIN_RK3308_LATEST = "1"
in the configuration (e.g. conf/local.conf).
U-Boot Environment:
------------------
In order to configure U-Boot to be able to store its environment into the
device from which it was booted, for any device supported in this BSP,
simply add the following to MACHINE_FEATURES:
rk-u-boot-env
If enabled, to additionally have the U-Boot environment generated and
stored in the image, also enable the following variable (default: off):
RK_IMAGE_INCLUDES_UBOOT_ENV
The script:
scripts/dump-uboot-env-from-yocto-image.sh
can be used on a rockchip wic image to see the contents of the U-Boot
environment partition at build time.
Maintenance:
-----------
Please send pull requests, patches, comments, or questions to the
yocto-patches mailing list (yocto-patches@lists.yoctoproject.org)
CCing the maintainer
When sending patches, please make sure the email subject line includes
"[meta-rockchip][PATCH]" and follow the community's patch submission
guidelines, as described in:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
This can be configured within the repository with the following commands:
git config sendemail.to yocto-patches@lists.yoctoproject.org
git config sendemail.cc <your full email address>
git config format.subjectprefix "meta-rockchip] [PATCH"
Then, to send your most recent commit (i.e. just one patch),
please use something like:
git format-patch -M -1
git send-email <your patch file>
Maintainer:
----------
Trevor Woerner <twoerner@gmail.com>
Brief History:
-------------
2014 April
- originally started by Julien Chauveau
- Romain Perier joins
2014 Sep
- Julien leaves
2015 Aug
- Trevor Woerner joins
2017 Mar
- developers from Rockchip fork this layer see:
https://github.com/rockchip-linux/meta-rockchip.git
http://rockchip.wikidot.com/yocto-user-guide
2017 May
- Romain leaves
2018 Feb
- Rockchip developers abandon their fork for buildroot
http://opensource.rock-chips.com/wiki_Buildroot
|