Update Documentation

Author: Mr-Dave

doc/CHANGELOG

@@ -1,3 +1,22 @@
+Summary of changes for version 4.6.0 are below
+    * Documentation updates
+    * Fix segfault on vaapi decoding
+    * Add support for DRM HW decode
+    * Remove default for allowed_media_types
+    * Fix libweb includes
+    * Fix autotools and translation files
+    * Update documentation on libcamerify
+    * Fix movie_extpipe
+    * Fix threshold_tune
+    * Add pragma for mmal code
+    * Update year in copyright notice
+    * Revise issue template
+    * Allow for bad packets when processing file
+    * Implement consistent time values
+    * Implement consistent calculation for pixel difference
+    * Fix compiler warnings
+    * Revise ioctl for devices to use long variable
+    * Print log message of signals
 Summary of changes for version 4.5.1 are below
     * Improve closing of v4l2 devices
     * Fix creation of pid_file

doc/motion_build.html

@@ -67,7 +67,7 @@ <h1>
       <button class="dropbtn">Distribution Specific Building</button>
       <div class="dropdown-content">
         <a href="#Preparation_For_Building"> Preparation For Building </a>
-        <a href="#BUILD_DEBIAN">Debian/Ubuntu/Raspbian</a>
+        <a href="#BUILD_DEBIAN">Debian/Ubuntu/Raspberry Pi OS</a>
         <a href="#BUILD_OPENSUSE">Open SUSE</a>
         <a href="#BUILD_FREEBSD">Free BSD</a>
         <a href="#BUILD_CENTOS">CentOS</a>
@@ -100,7 +100,7 @@ <h1>
     <h3><a name="Install_Apt"></a> Installing with apt </h3>
     <ul>
       <p></p>
-      Motion is part of the Debian, Ubuntu and Raspbian repositories and can be installed with the apt tool.  The
+      Motion is part of the Debian, Ubuntu and Raspberry Pi OS repositories and can be installed with the apt tool.  The
       version included with apt will be the version that was available when the distribution version
       was initially deployed and therefore may not represent the latest release.
       <p></p>
@@ -179,11 +179,11 @@ <h3><a name="Abbreviated_Building"></a> Abbreviated Building Guide  </a> </h3>
       script.  If errors occur during the process or you wish to customize the build, please
       review the extended building instructions further below.
       <p></p>
-      Debian / Ubuntu / Raspbian Packages
+      Debian / Ubuntu / Raspberry Pi OS Packages
       <ul>
           <code><strong>sudo apt-get install autoconf automake autopoint build-essential pkgconf libtool libzip-dev
           libjpeg-dev git libavformat-dev libavcodec-dev libavutil-dev libswscale-dev libavdevice-dev
-          libwebp-dev gettext libmicrohttpd-dev</strong></code>
+          libwebp-dev gettext libmicrohttpd-dev libcamera-tools libcamera-dev</strong></code>
           <p></p>
           <code><strong>cd ~</strong></code>
           <br /><code><strong>git clone https://github.com/Motion-Project/motion.git</strong></code>
@@ -247,13 +247,13 @@ <h3><a name="Preparation_For_Building"></a> Preparation For Building</a> </h3>
       <p></p>
       <p></p>
 
-      <h4><a name="BUILD_DEBIAN"></a>Debian/Ubuntu/Raspbian</a> </h4>
+      <h4><a name="BUILD_DEBIAN"></a>Debian/Ubuntu/Raspberry Pi OS</a> </h4>
       <ul>
         <li>Required</li>
         <ul>
           <p></p>
-          <code><strong>sudo apt-get install autoconf automake autopoint build-essential pkgconf
-          libtool git libzip-dev libjpeg62-turbo-dev gettext libmicrohttpd-dev</strong></code>
+          <code><strong>sudo apt-get install autoconf automake autopoint build-essential pkgconf libtool libzip-dev
+          libjpeg-dev git gettext libmicrohttpd-dev </strong></code>
           <p></p>
         </ul>
         <p></p>
@@ -293,10 +293,10 @@ <h4><a name="BUILD_DEBIAN"></a>Debian/Ubuntu/Raspbian</a> </h4>
             <code><strong>sudo apt-get install libsqlite3-dev</strong></code>
             <p></p>
           </ul>
-          <li>JPEG Turbo</li>
+          <li>libcamera</li>
           <ul>
             <p></p>
-            <code><strong>sudo apt-get install libjpeg-turbo8 libjpeg-turbo8-dev</strong></code>
+            <code><strong>sudo apt-get install libcamera-tools libcamera-dev</strong></code>
             <p></p>
           </ul>
           <li>Webp Image Support</li>

doc/motion_config.html

@@ -234,67 +234,18 @@ <h2><a name="Basic_Setup"></a>  Basic Setup </h2>
       <p></p>
 
       <a name="basic_setup_picam"></a>
-      <strong>The raspberry Pi camera</strong> is set up multiple ways depending upon the distro being used.
-      <p></p>
-      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
+      <strong>The raspberry Pi camera</strong> is set up via an application called
       <i><small><code>libcamera</code></small></i>.  <i><small><code>libcamera</code></small></i> 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 <i><small><code>libcamerify motion</code></small></i> and
       then specify the /dev/videoX device in the Motion configuration file.
       <p></p>
-      The PI camera's drivers expose the camera's full functionality as a set of low-level /dev/videoX
-      devices, while Motion (and other applications) expect a single high-level /dev/videoX device. The
-      libcamerify wrapper transparently manages these low-level devices and presents a high-level
-      interface on one of the /dev/videoX device nodes to Motion
-      (<a href="https://libcamera.org/docs.html#v4l2-compatibility-layer">libcamera docs</a>).
-      <p></p>
       With just one camera connected to the Pi, the device name should normally be
       <i><small><code>/dev/video0</code></small></i>.  With multiple cameras connected, e.g. a regular
-      USB web and the Pi camera, you should use the device names provided by V4L
-      (<i><small><code>v4l2-ctl --list-devices</code></small></i>). The wrapper doesn't seem to affect
-      the device names seen by Motion. In the below example, the PI camera is at
-      <i><small><code>/dev/video2</code></small></i> while an external USB camera is at
-      <i><small><code>/dev/video0</code></small></i> ("CSI" stands for the
-      <a href="https://en.wikipedia.org/wiki/Camera_Serial_Interface">interface	used by the Pi camera</a>).
-      <p></p>
-      Also, /dev/videoN names are dynamically assigned and may not always point to the same camera (e.g.
-      when a USB camera is hot-plugged). Take a look at the stable symlinks under
-      <i><small><code>/dev/v4l/by-path/</code></small></i> and consider using them in your Motion config
-      instead of /dev/videoX.
-      <pre>
-root@raspberrypi:~# v4l2-ctl --list-devices
-unicam (platform:3f801000.csi):
-/dev/video2                        # <== PI Camera
-/dev/media2
-
-bcm2835-codec-decode (platform:bcm2835-codec):
-/dev/video10                       # <=== Low level devices
-/dev/video11                       # for the Pi cam, ignore
-....
-
-bcm2835-isp (platform:bcm2835-isp):
-/dev/video13                      # <=== Low level devices
-/dev/video14                      # for the Pi cam, ignore
-....
-
-Venus USB2.0 Camera: Venus USB2 (usb-3f980000.usb-1.2):
-/dev/video0                         # <== USB webcam
-/dev/video1
-/dev/media4
-      </pre>
-      <p></p>
-      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 <code>sudo modprobe bcm2835-v4l2</code>.  This
-      will set up the camera as a normal v4l2 device and it can be accessed via a standard /dev/videoX device.  If Motion is
-      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 <a href="#mmalcam_name" >mmalcam_name</a> parameter or using
-      the bcm2835-v4l2 module.  <strong>When Motion is installed via apt, the mmalcam option is not available.</strong>
-      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.
+      USB web and the Pi camera, you will need to determine the device associated with the
+      Pi camera and the USB camera.  The list of devices can be seen using the command
+      (<i><small><code>v4l2-ctl --list-devices</code></small></i>).
       <p></p>
 
       <a name="basic_setup_composite"></a>