jeans/motioneyeos
jeans/motioneyeos
1
0
Fork 0
mirror of https://github.com/motioneye-project/motioneyeos.git synced 2025-08-03 08:27:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

boards/raspberrypi: update instructions

Browse Source 
Now that we have a sanitised set of defconfig files, and we no longer
support non-DT setups, update and simplify the board readme file.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Floris Bos <bos@je-eigen-domein.nl>
Cc: Pascal de Bruijn <pmjdebruijn@pcode.nl>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
Yann E. MORIN 2015-06-30 00:07:46 +02:00 committed by Thomas Petazzoni
parent 76b00bde62
commit 6f999784b8
1 changed files with 22 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
board/raspberrypi/readme.txt
View File

@ -22,17 +22,14 @@ How to build it
Configure Buildroot Configure Buildroot
------------------- -------------------
The raspberrypi_defconfig configuration is a minimal configuration with There are two RaspberryPi defconfig files in Buildroot, one for each
all that is required to bring the Raspberry Pi up. You should base your major variant, which you should base your work on:
work on this defconfig:
For models A, B, A+ or B+:
$ make raspberrypi_defconfig $ make raspberrypi_defconfig
Alternatively, if you want to test support for the Device Tree: And for model 2 B:
$ make raspberrypi_dt_defconfig
For Raspberry Pi 2 use a different defconfig:
$ make raspberrypi2_defconfig $ make raspberrypi2_defconfig
@ -64,20 +61,23 @@ Result of the build
After building, you should obtain this tree: After building, you should obtain this tree:
output/images/ output/images/
+-- rootfs.tar [0] +-- rootfs.tar [0]
+-- rpi-firmware/ +-- rpi-firmware/
| +-- bcm2708-rpi-b.dtb
| +-- bcm2708-rpi-b-plus.dtb
| +-- bcm2709-rpi-2-b.dtb
| +-- bootcode.bin | +-- bootcode.bin
| +-- config.txt | +-- config.txt
| +-- fixup.dat | +-- fixup.dat
| `-- start.elf | `-- start.elf
+-- bcm2708-rpi-b.dtb [1]
+-- bcm2708-rpi-b-plus.dtb [1]
+-- bcm2709-rpi-2-b.dtb [1]
`-- zImage `-- zImage
[0] Note for Volatile: rootfs.tar will only be there if you kept [0] Note for Volatile: rootfs.tar will only be there if you kept
"tar the root filesystem" option selected in "Filesystem images". "tar the root filesystem" option selected in "Filesystem images".
[1] Not all of them will be present, depending on the RaspberryPi
model you are using.
Prepare you SDCard Prepare you SDCard
================== ==================
@ -105,30 +105,26 @@ Install the binaries to the SDCard
At the root of the boot partition, the Raspberry Pi must find the following At the root of the boot partition, the Raspberry Pi must find the following
files: files:
* bcm2708-rpi-b.dtb [1] * bcm2708-rpi-b.dtb [2]
* bcm2708-rpi-b-plus.dtb [2] * bcm2708-rpi-b-plus.dtb [3]
* bcm2709-rpi-2-b.dtb [3] * bcm2709-rpi-2-b.dtb [4]
* bootcode.bin * bootcode.bin
* config.txt * config.txt
* fixup.dat * fixup.dat
* start.elf * start.elf
* zImage * zImage
[1] For models A and B [2] For models A and B
[2] For models A+ and B+ [3] For models A+ and B+
[3] For model 2 [4] For model 2
For example: For example:
$ cp output/images/rpi-firmware/* /mnt/mountpointboot $ cp output/images/rpi-firmware/* /mnt/mountpointboot
$ cp output/images/*.dtb /mnt/mountpointboot
If your kernel does *not* have support for the Device Tree, then install The kernel image must be marked with a special header so that the
it with: bootloader of the RaspberryPi knows it supports Device Tree:
$ cp output/images/zImage /mnt/mountpointboot
If your kernel *does* have support for the Device Tree, then install it
with:
$ ./output/host/usr/bin/mkknlimg output/images/zImage /mnt/mountpointboot/zImage $ ./output/host/usr/bin/mkknlimg output/images/zImage /mnt/mountpointboot/zImage