Line 45:
Line 45:
(TODO picture)
(TODO picture)
+
+
=== piOS Configuration ===
+
For details on how to install the Raspberry Pi system, please refer to the official documentation at [https://www.raspberrypi.org/documentation/installation/ Install raspberry pi guide].
+
+
Initially, the Raspberry Pi system I2C is not enabled. After booting, we need to turn them on manually by executing the following command:
+
+
<code>sudo raspi-config</code>[[File:Raspi-config bullseye.png|alt=|center|thumb|608x608px|raspi-config bullseye|link=http://wiki.veye.cc/index.php/File:Raspi-config_bullseye.png]]Enter Interface Options, enable I2C, and then restart the Raspberry Pi.
+
+
It is recommended to enable the ssh service and samba service of Raspberry Pi system, here we will not go into the details of how to enable ssh and samba service of Raspberry Pi system.
+
+
=== Legacy mode and V4L2 mode introduction ===
+
The difference between these two modes is described in detail on the [https://www.raspberrypi.com/documentation/accessories/camera.html#libcamera-and-the-legacy-raspicam-camera-stack Raspberry Pi website.] The libcamera-stack mode mentioned on the Raspberry Pi website is architecturally identical to the V4L2 mode we are talking about.
+
+
==== Legacy mode ====
+
Traditional mode, relying on Broadcom's GPU for image processing. The traditional raspicam software set uses this model.
+
+
The disadvantage of this model is closed. The GPU side is closed source, can not freely access sensor.
+
+
The Raspberry Pi organization has switched to the libcamera camera stack, but this model still has value:
+
+
# More use of GPU resources and lower CPU load. This is useful for earlier versions of the Raspberry Pi where CPU performance is poorer.
+
# It is possible to simply and directly fetch image data to the application layer without the support of the driver layer. This is especially useful for cameras that do not rely on the Raspberry Pi's isp.
+
# libcamera lacks some feature support now.
+
<br />
<br />