From ae63db8eb82e83dcd6728ed60f6d502e3e509ff3 Mon Sep 17 00:00:00 2001 From: Mr-Dave Date: Sun, 12 Jun 2022 16:42:26 -0600 Subject: [PATCH] Update PI camera instructions --- doc/motion_config.html | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/doc/motion_config.html b/doc/motion_config.html index 0e25bd2b..530ba9f1 100644 --- a/doc/motion_config.html +++ b/doc/motion_config.html @@ -234,7 +234,17 @@

- Raspberry Pi cameras can be set up two different ways. If Motion is installed by using the + The raspberry Pi camera is set up multiple ways depending upon the distro being used. +

+ In the Raspbian version based upon Debian release of 'bullseye' (and presumably later releases), Raspbian + allows access to the PI camera via an application called + libcamera. libcamera provides + access to the camera as a v4l2 device but this interface is only available when using a special + application. Users must run Motion using the + command libcamerify motion and + then specify /dev/video0 in the Motion configuration file. +

+ For Raspbian releases prior to 'bullseye', the PI camera can be set up two different ways. If Motion is installed by using the apt packages (e.g. apt-get install motion), then the camera must be set up using the bcm2835-v4l2 module which creates a v4l2 device for the camera. Users will need to install this module using the command sudo modprobe bcm2835-v4l2. This @@ -242,6 +252,8 @@ built from source or installed via the deb packages on the project release page, then an additional option is to set up the camera using the mmalcam_name parameter or using the bcm2835-v4l2 module. When Motion is installed via apt, the mmalcam option is not available. + It has been noted that this historical method of accessing the PI camera may be available in newer + releases via the enabling the legacy camera stack but it is unclear how long this method will be permitted.