@@ -130,24 +130,59 @@ Then, connect the cables to the Pi as described in this chart:
### Display
1. Connect the display by placing it on the GPIO header
2. Add the following line to `/boot/firmware/config.txt`
2. Download the [`waveshare35a-overlay.dtb` Device Tree Overlay](https://github.com/waveshareteam/LCD-show/raw/refs/heads/master/waveshare35a-overlay.dtb) and save it as `/boot/firmware/overlays/waveshare35a.dtbo`
3. Add the following lines to `/boot/firmware/config.txt`
3. Add `fbcon=map:2` at the end of the line to `/boot/firmware/cmdline.txt`
4. Add `fbcon=map:2` at the end of the line to `/boot/firmware/cmdline.txt`
- This will tell the framebuffer console (fbcon) to map all its terminals to `/dev/fb2` (which doesn't exist), i.e. don't show a Linux TTY on the display
<details>
<summary>Links</summary>
-[🌟 Python pygame fails to output to /dev/fb1 on a Raspberry Pi + TFT screen](https://stackoverflow.com/a/54986161/)
-[🌟 Setting Up a TFT Touchscreen on a Raspberry Pi with a fbtft Linux Driver](https://chrizog.com/rpi-linux-fbtft-touchscreen-setup)
-[Raspberry Pi Forum post mentioning the line to include in the config (German)](https://forum-raspberrypi.de/forum/thread/55290-displays-mit-spi-anschluss-unter-raspberry-pi-os-bullseye-bookworm/)
-[Python pygame fails to output to /dev/fb1 on a Raspberry Pi + TFT screen](https://stackoverflow.com/a/54986161/)
-[Device tree overlays README](https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README)
However, support for this seems to be very flaky, often doesn't work at all, and might conflict with `fbtft` (i.e. you have either touch or display, not both).