Browse Source

manual: board support: add instructions to test defconfig in the official docker

Sometimes new boards have not been tested with official docker so let's add
instructions to do it with utils/docker-run.

Cc: Luca Ceresoli <luca@lucaceresoli.net>
Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Reviewed-by: Luca Ceresoli <luca@lucaceresoli.net>
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Giulio Benetti 3 years ago
parent
commit
1e1976a25d
1 changed files with 8 additions and 0 deletions
  1. 8 0
      docs/manual/adding-board-support.txt

+ 8 - 0
docs/manual/adding-board-support.txt

@@ -46,3 +46,11 @@ create a directory +board/<manufacturer>+ and a subdirectory
 +board/<manufacturer>/<boardname>+. You can then store your patches
 +board/<manufacturer>/<boardname>+. You can then store your patches
 and configurations in these directories, and reference them from the main
 and configurations in these directories, and reference them from the main
 Buildroot configuration. Refer to xref:customize[] for more details.
 Buildroot configuration. Refer to xref:customize[] for more details.
+
+Before submitting patches for new boards it is recommended to test it by
+building it using latest gitlab-CI docker container. To do this use
+utils/docker-run script and inside it issue these commands:
+--------------------
+ $ make +<boardname>_defconfig+
+ $ make
+--------------------