summaryrefslogtreecommitdiffstats
path: root/recipes-bsp/rpi-mkimage
Commit message (Collapse)AuthorAgeFilesLines
* rpi-mkimage: Bump revisionAndrei Gherzan2015-10-211-1/+1
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* rpi-mkimage: Bump SRCREVPetter Mabäcker2015-07-191-1/+1
| | | | | | | | | Update to latest version of rpi-mkimg [Support #60] Signed-off-by: Petter Mabäcker <petter@technux.se> Acked-by: Andrei Gherzan <andrei@gherzan.ro>
* devicetree: Add minimal support with RPi bootloaderFrancois Muller2015-02-051-1/+1
| | | | | | | | | | | | | | | | | | | | | [RPi DT info] https://github.com/raspberrypi/documentation/blob/master/configuration/device-tree.md#part-3-using-device-trees-on-raspberry-pi RPi bootloader detects a DT-ready kernel by checking for a specific trailer in kernel.img. Using latest raspberrypi/firmware (firmware.inc) enables this check ability. Using latest raspberrypi/tools (rpi-mkimage.bb) gives access to mkknlimg for adding the required trailer to kernel image. If KERNEL_DEVICETREE is filled in, the trailer is added to the kernel image before kernel install task. While creating the SDCard image, this modified kernel is put on boot partition (as kernel.img) as well as DeviceTree blobs (.dtb files). If KERNEL_DEVICETREE is empty, this new process isn't operated, legacy one does. KERNEL_DEVICETREE for RPi is really supported only starting from linux-rapsberry 3.18+ kernels, so as for now it defaults to empty (in machine config file). Change-Id: Ifea71bbda729b8f3c47be7ba0ba03be5ad2ceeaa Signed-off-by: Francois Muller <francois@concept-embarque.fr>
* rpi-mkimage: Integrate packageAndrei Gherzan2014-02-093-0/+64
Tool needed to convert bootable images in kernel.img files which can be loaded by rpi bootloader. Change-Id: I0088707be5d31d77def1087f51e3f8cc886d19db Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>