Update OS to Bullseye

[andysheen]

Description

• Updated CustomPiOS to use Bullseye.
• Legacy Camera support for Pi Zero 2 W

Fixes #95

Type of change

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

Tested on the following devices:

• [ ] Development environment (Linux, Windows, or MacOS)
• [x] Pi Zero W
• [ ] Pi 3A+
• [ ] Pi 3B+
• [ ] Pi 4
• [x] Pi Zero 2 W

Checklist:

• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [x] My changes generate no new warnings
• [ ] New and existing unit tests pass locally with my changes

[Vincent-Stragier]

@mikevanis, I just realized I was not clear and partially wrong in the above comment. But basically you should remove:

raspi-config nonint do_camera 1
echo "start_x=1" >> /boot/config.txt

And replace it by:

raspi-config nonint do_legacy 0

I tested it on a Raspberry Pi 4. I did not realize at first that do_legacy was implemented, but it is (https://www.raspberrypi.com/news/new-old-functionality-with-raspberry-pi-os-legacy). Apparently the picamera module will be updated (and I suppose that after do_camera must be used), because they are trying to use open source drivers.

Edit: I built an image here with this change.

[mikevanis]

@Vincent-Stragier can confirm this works on Pi Zero 2 W. I'll fix it directly on the main branch. Thank you!