commit 8c820dd294e8d210002659c0db33c1e0beac1e96
parent f7b7a4341a7c9719eec08d5afc5b018422762285
Author: parazyd <parazyd@dyne.org>
Date: Sat, 21 Nov 2020 01:47:03 +0100
Add Raspberry Pi firmware blobs and .txt files.
Diffstat:
12 files changed, 58 insertions(+), 0 deletions(-)
diff --git a/rpi-boot/LICENCE.broadcom b/rpi-boot/LICENCE.broadcom
@@ -0,0 +1,31 @@
+Copyright (c) 2006, Broadcom Corporation.
+Copyright (c) 2015, Raspberry Pi (Trading) Ltd
+All rights reserved.
+
+Redistribution. Redistribution and use in binary form, without
+modification, are permitted provided that the following conditions are
+met:
+
+* This software may only be used for the purposes of developing for,
+ running or using a Raspberry Pi device, or authorised derivative
+ device manufactured via the element14 Raspberry Pi Customization Service
+* Redistributions must reproduce the above copyright notice and the
+ following disclaimer in the documentation and/or other materials
+ provided with the distribution.
+* Neither the name of Broadcom Corporation nor the names of its suppliers
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+DISCLAIMER. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
+CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
+BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
+OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
+TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
+USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGE.
+
diff --git a/rpi-boot/bootcode.bin b/rpi-boot/bootcode.bin
Binary files differ.
diff --git a/rpi-boot/cmdline.txt b/rpi-boot/cmdline.txt
@@ -0,0 +1 @@
+console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 fsck.repair=yes rootwait
diff --git a/rpi-boot/config.txt b/rpi-boot/config.txt
@@ -0,0 +1,26 @@
+kernel=zImage
+device_tree=bcm-2835-rpi-zero.dtb
+#avoid_warnings=2
+gpu_mem=16
+#initramfs initramfs.gz followkernel
+disable_splash=1
+
+# There are two framebuffers when an SPI display is attached:
+#
+# - /dev/fb0 - represents the HDMI output. This output is hardware-accelerated
+# and therefore should be the target of GUIs
+# - /dev/fb1 - represents the SPI/LCD output
+#
+# The following settings enable a custom mode (mode 87) that sets the HDMI
+# output to the same resolution as the LCD. This is useful so an application
+# can target the hardware-accelerated output, and the raspi2fb tool can be
+# used to mirror the output to the LCD.
+#
+# The HDMI group forces DMT output even on the HDMI output. DMT is the
+# standard for monitors, in contrast to CEA, the standard for TVs.
+
+framebuffer_width=250
+framebuffer_height=122
+hdmi_cvt 250 122 60 1 0 0 0
+hdmi_mode=87
+hdmi_group=2
diff --git a/rpi-boot/fixup.dat b/rpi-boot/fixup.dat
Binary files differ.
diff --git a/rpi-boot/fixup_cd.dat b/rpi-boot/fixup_cd.dat
Binary files differ.
diff --git a/rpi-boot/fixup_db.dat b/rpi-boot/fixup_db.dat
Binary files differ.
diff --git a/rpi-boot/fixup_x.dat b/rpi-boot/fixup_x.dat
Binary files differ.
diff --git a/rpi-boot/start.elf b/rpi-boot/start.elf
Binary files differ.
diff --git a/rpi-boot/start_cd.elf b/rpi-boot/start_cd.elf
Binary files differ.
diff --git a/rpi-boot/start_db.elf b/rpi-boot/start_db.elf
Binary files differ.
diff --git a/rpi-boot/start_x.elf b/rpi-boot/start_x.elf
Binary files differ.
