[{"id":22831,"web_url":"https://patchwork.libcamera.org/comment/22831/","msgid":"<20220504071232.5k3ggf63umpw6nev@uno.localdomain>","date":"2022-05-04T07:12:32","subject":"Re: [libcamera-devel] [PATCH 3/3] Documentation: use https instead\n\tof http","submitter":{"id":3,"url":"https://patchwork.libcamera.org/api/people/3/","name":"Jacopo Mondi","email":"jacopo@jmondi.org"},"content":"Hi Quentin\n\nOn Tue, May 03, 2022 at 06:30:38PM +0200, Quentin Schulz via libcamera-devel wrote:\n> From: Quentin Schulz <quentin.schulz@theobroma-systems.com>\n>\n> Avoid a redirection from http by using https directly.\n\nAlso a generally better practice :)\n\nReviewed-by: Jacopo Mondi <jacopo@jmondi.org>\n\nThanks\n  j\n\n>\n> Cc: Quentin Schulz <foss+libcamera@0leil.net>\n> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>\n> ---\n>  Documentation/contributing.rst                |   4 +-\n>  Documentation/environment_variables.rst       |   2 +-\n>  .../guides/application-developer.rst          |   8 +-\n>  Documentation/guides/introduction.rst         |   6 +-\n>  Documentation/guides/pipeline-handler.rst     | 116 +++++++++---------\n>  5 files changed, 68 insertions(+), 68 deletions(-)\n>\n> diff --git a/Documentation/contributing.rst b/Documentation/contributing.rst\n> index 57bc9acc..6405c5fb 100644\n> --- a/Documentation/contributing.rst\n> +++ b/Documentation/contributing.rst\n> @@ -56,8 +56,8 @@ Documentation\n>  Project documentation is created using `Sphinx`_.  Source level documentation\n>  uses `Doxygen`_.  Please make sure to document all code during development.\n>\n> -.. _Sphinx: http://www.sphinx-doc.org\n> -.. _Doxygen: http://www.doxygen.nl\n> +.. _Sphinx: https://www.sphinx-doc.org\n> +.. _Doxygen: https://www.doxygen.nl\n>\n>  Submitting Patches\n>  ------------------\n> diff --git a/Documentation/environment_variables.rst b/Documentation/environment_variables.rst\n> index 1e85befd..fa703a72 100644\n> --- a/Documentation/environment_variables.rst\n> +++ b/Documentation/environment_variables.rst\n> @@ -54,7 +54,7 @@ The optional `category <Log categories_>`__ is a string matching the categories\n>  defined by each file in the source base using the logging infrastructure. It\n>  can include a wildcard ('*') character at the end to match multiple categories.\n>\n> -For more information refer to the `API documentation <http://libcamera.org/api-html/log_8h.html#details>`__.\n> +For more information refer to the `API documentation <https://libcamera.org/api-html/log_8h.html#details>`__.\n>\n>  Examples:\n>\n> diff --git a/Documentation/guides/application-developer.rst b/Documentation/guides/application-developer.rst\n> index 07cc7273..16bea9c4 100644\n> --- a/Documentation/guides/application-developer.rst\n> +++ b/Documentation/guides/application-developer.rst\n> @@ -49,7 +49,7 @@ abstracts and manages the complex pipelines that kernel drivers expose through\n>  the `Linux Media Controller`_ and `Video for Linux`_ (V4L2) APIs, meaning that\n>  an application doesn't need to handle device or driver specific details.\n>\n> -.. _CameraManager: http://libcamera.org/api-html/classlibcamera_1_1CameraManager.html\n> +.. _CameraManager: https://libcamera.org/api-html/classlibcamera_1_1CameraManager.html\n>  .. _Linux Media Controller: https://www.kernel.org/doc/html/latest/media/uapi/mediactl/media-controller-intro.html\n>  .. _Video for Linux: https://www.linuxtv.org/docs.php\n>\n> @@ -207,7 +207,7 @@ supported values.\n>  The ``validate`` function returns a `Status`_ which applications shall check to\n>  see if the Pipeline Handler adjusted the configuration.\n>\n> -.. _Status: http://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html#a64163f21db2fe1ce0a6af5a6f6847744\n> +.. _Status: https://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html#a64163f21db2fe1ce0a6af5a6f6847744\n>\n>  For example, the code above set the width and height to 640x480, but if the\n>  camera cannot produce an image that large, it might adjust the configuration to\n> @@ -345,7 +345,7 @@ Event handling and callbacks\n>  The libcamera library uses the concept of `signals and slots` (similar to `Qt\n>  Signals and Slots`_) to connect events with callbacks to handle them.\n>\n> -.. _signals and slots: http://libcamera.org/api-html/classlibcamera_1_1Signal.html#details\n> +.. _signals and slots: https://libcamera.org/api-html/classlibcamera_1_1Signal.html#details\n>  .. _Qt Signals and Slots: https://doc.qt.io/qt-5/signalsandslots.html\n>\n>  The ``Camera`` device emits two signals that applications can connect to in\n> @@ -418,7 +418,7 @@ in this request, and access the metadata associated to each frame.\n>  The metadata buffer contains information such the capture status, a timestamp,\n>  and the bytes used, as described in the `FrameMetadata`_ documentation.\n>\n> -.. _FrameMetaData: http://libcamera.org/api-html/structlibcamera_1_1FrameMetadata.html\n> +.. _FrameMetaData: https://libcamera.org/api-html/structlibcamera_1_1FrameMetadata.html\n>\n>  .. code:: cpp\n>\n> diff --git a/Documentation/guides/introduction.rst b/Documentation/guides/introduction.rst\n> index 07f66881..2d1760c1 100644\n> --- a/Documentation/guides/introduction.rst\n> +++ b/Documentation/guides/introduction.rst\n> @@ -214,7 +214,7 @@ Camera Manager\n>\n>    Read the `Camera Manager API`_ documentation for more details.\n>\n> -.. _Camera Manager API: http://libcamera.org/api-html/classlibcamera_1_1CameraManager.html\n> +.. _Camera Manager API: https://libcamera.org/api-html/classlibcamera_1_1CameraManager.html\n>\n>  Camera Device\n>    The Camera class represents a single item of camera hardware that is capable\n> @@ -231,7 +231,7 @@ Camera Device\n>\n>    Read the `Camera API`_ documentation for more details.\n>\n> -..  _Camera API: http://libcamera.org/api-html/classlibcamera_1_1Camera.html\n> +.. _Camera API: https://libcamera.org/api-html/classlibcamera_1_1Camera.html\n>\n>  Pipeline Handler\n>    The Pipeline Handler manages the complex pipelines exposed by the kernel\n> @@ -254,7 +254,7 @@ Pipeline Handler\n>    More details can be found in the `PipelineHandler API`_ documentation, and the\n>    `Pipeline Handler Writers Guide`_.\n>\n> -.. _PipelineHandler API: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html\n> +.. _PipelineHandler API: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html\n>\n>  Image Processing Algorithms\n>    An image processing algorithm (IPA) component is a loadable plugin that\n> diff --git a/Documentation/guides/pipeline-handler.rst b/Documentation/guides/pipeline-handler.rst\n> index 989b0163..8e3f991d 100644\n> --- a/Documentation/guides/pipeline-handler.rst\n> +++ b/Documentation/guides/pipeline-handler.rst\n> @@ -81,49 +81,49 @@ functionalities described above. Below is a brief overview of each of those:\n>  .. TODO: (MediaDevice) Reference to the Media Device API (possibly with versioning requirements)\n>  .. TODO: (IPAInterface) refer to the IPA guide\n>\n> --  `MediaDevice <http://libcamera.org/api-html/classlibcamera_1_1MediaDevice.html>`_:\n> +-  `MediaDevice <https://libcamera.org/api-html/classlibcamera_1_1MediaDevice.html>`_:\n>     Instances of this class are associated with a kernel media controller\n>     device and its connected objects.\n>\n> --  `DeviceEnumerator <http://libcamera.org/api-html/classlibcamera_1_1DeviceEnumerator.html>`_:\n> +-  `DeviceEnumerator <https://libcamera.org/api-html/classlibcamera_1_1DeviceEnumerator.html>`_:\n>     Enumerates all media devices attached to the system and the media entities\n>     registered with it, by creating instances of the ``MediaDevice`` class and\n>     storing them.\n>\n> --  `DeviceMatch <http://libcamera.org/api-html/classlibcamera_1_1DeviceMatch.html>`_:\n> +-  `DeviceMatch <https://libcamera.org/api-html/classlibcamera_1_1DeviceMatch.html>`_:\n>     Describes a media device search pattern using entity names, or other\n>     properties.\n>\n> --  `V4L2VideoDevice <http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html>`_:\n> +-  `V4L2VideoDevice <https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html>`_:\n>     Models an instance of a V4L2 video device constructed with the path to a V4L2\n>     video device node.\n>\n> --  `V4L2SubDevice <http://libcamera.org/api-html/classlibcamera_1_1V4L2Subdevice.html>`_:\n> +-  `V4L2SubDevice <https://libcamera.org/api-html/classlibcamera_1_1V4L2Subdevice.html>`_:\n>     Provides an API to the sub-devices that model the hardware components of a\n>     V4L2 device.\n>\n> --  `CameraSensor <http://libcamera.org/api-html/classlibcamera_1_1CameraSensor.html>`_:\n> +-  `CameraSensor <https://libcamera.org/api-html/classlibcamera_1_1CameraSensor.html>`_:\n>     Abstracts camera sensor handling by hiding the details of the V4L2 subdevice\n>     kernel API and caching sensor information.\n>\n> --  `Camera::Private <http://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html>`_:\n> +-  `Camera::Private <https://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html>`_:\n>     Represents device-specific data a pipeline handler associates to each Camera\n>     instance.\n>\n> --  `StreamConfiguration <http://libcamera.org/api-html/structlibcamera_1_1StreamConfiguration.html>`_:\n> +-  `StreamConfiguration <https://libcamera.org/api-html/structlibcamera_1_1StreamConfiguration.html>`_:\n>     Models the current configuration of an image stream produced by the camera by\n>     reporting its format and sizes.\n>\n> --  `CameraConfiguration <http://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html>`_:\n> +-  `CameraConfiguration <https://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html>`_:\n>     Represents the current configuration of a camera, which includes a list of\n>     stream configurations for each active stream in a capture session. When\n>     validated, it is applied to the camera.\n>\n> --  `IPAInterface <http://libcamera.org/api-html/classlibcamera_1_1IPAInterface.html>`_:\n> +-  `IPAInterface <https://libcamera.org/api-html/classlibcamera_1_1IPAInterface.html>`_:\n>     The interface to the Image Processing Algorithm (IPA) module which performs\n>     the computation of the image processing pipeline tuning parameters.\n>\n> --  `ControlList <http://libcamera.org/api-html/classlibcamera_1_1ControlList.html>`_:\n> +-  `ControlList <https://libcamera.org/api-html/classlibcamera_1_1ControlList.html>`_:\n>     A list of control items, indexed by Control<> instances or by numerical index\n>     which contains values used by application and IPA to change parameters of\n>     image streams, used to return to applications and share with IPA the metadata\n> @@ -191,7 +191,7 @@ In *vivid.cpp* add the pipeline handler to the ``libcamera`` namespace, defining\n>  a `PipelineHandler`_ derived class named PipelineHandlerVivid, and add stub\n>  implementations for the overridden class members.\n>\n> -.. _PipelineHandler: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html\n> +.. _PipelineHandler: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html\n>\n>  .. code-block:: cpp\n>\n> @@ -267,7 +267,7 @@ handler factory using the `REGISTER_PIPELINE_HANDLER`_ macro which\n>  registers it and creates a global symbol to reference the class and make it\n>  available to try and match devices.\n>\n> -.. _REGISTER_PIPELINE_HANDLER: http://libcamera.org/api-html/pipeline__handler_8h.html\n> +.. _REGISTER_PIPELINE_HANDLER: https://libcamera.org/api-html/pipeline__handler_8h.html\n>\n>  For debugging and testing a pipeline handler during development, you can define\n>  a log message category for the pipeline handler. The ``LOG_DEFINE_CATEGORY``\n> @@ -275,7 +275,7 @@ macro and ``LIBCAMERA_LOG_LEVELS`` environment variable help you use the inbuilt\n>  libcamera `logging infrastructure`_ that allow for the inspection of internal\n>  operations in a user-configurable way.\n>\n> -.. _logging infrastructure: http://libcamera.org/api-html/log_8h.html\n> +.. _logging infrastructure: https://libcamera.org/api-html/log_8h.html\n>\n>  Add the following before the ``PipelineHandlerVivid`` class declaration:\n>\n> @@ -334,8 +334,8 @@ You can specify the search further by adding specific media entities to the\n>  search using the ``.add()`` function on the DeviceMatch.\n>\n>  .. _match(): https://www.libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a7cd5b652a2414b543ec20ba9dabf61b6\n> -.. _start(): http://libcamera.org/api-html/classlibcamera_1_1CameraManager.html#a49e322880a2a26013bb0076788b298c5\n> -.. _DeviceMatch: http://libcamera.org/api-html/classlibcamera_1_1DeviceMatch.html\n> +.. _start(): https://libcamera.org/api-html/classlibcamera_1_1CameraManager.html#a49e322880a2a26013bb0076788b298c5\n> +.. _DeviceMatch: https://libcamera.org/api-html/classlibcamera_1_1DeviceMatch.html\n>\n>  This example uses search patterns that match vivid, but when developing a new\n>  pipeline handler, you should change this value to suit your device identifier.\n> @@ -354,7 +354,7 @@ to the matching media controller device with the `acquireMediaDevice`_ function.\n>  If the function attempts to acquire a device it has already matched, it returns\n>  ``false``.\n>\n> -.. _acquireMediaDevice: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a77e424fe704e7b26094164b9189e0f84\n> +.. _acquireMediaDevice: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a77e424fe704e7b26094164b9189e0f84\n>\n>  Add the following below ``dm.add(\"vivid-000-vid-cap\");``:\n>\n> @@ -419,7 +419,7 @@ with the Camera.\n>  Each Camera has instance-specific data represented using the `Camera::Private`_\n>  class, which can be extended for the specific needs of the pipeline handler.\n>\n> -.. _Camera::Private: http://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html\n> +.. _Camera::Private: https://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html\n>\n>\n>  To support the Camera we will later register, we need to create a Camera::Private\n> @@ -475,7 +475,7 @@ the `MediaDevice::getEntityByName`_ function from the MediaDevice. As our\n>  example is based upon the simplistic Vivid test device, we only need to open a\n>  single capture device named 'vivid-000-vid-cap' by the device.\n>\n> -.. _MediaDevice::getEntityByName: http://libcamera.org/api-html/classlibcamera_1_1MediaDevice.html#ad5d9279329ef4987ceece2694b33e230\n> +.. _MediaDevice::getEntityByName: https://libcamera.org/api-html/classlibcamera_1_1MediaDevice.html#ad5d9279329ef4987ceece2694b33e230\n>\n>  .. code-block:: cpp\n>\n> @@ -516,8 +516,8 @@ handler and camera manager using `registerCamera`_.\n>  Finally with a successful construction, we return 'true' indicating that the\n>  PipelineHandler successfully matched and constructed a device.\n>\n> -.. _Camera::create: http://libcamera.org/api-html/classlibcamera_1_1Camera.html#a453740e0d2a2f495048ae307a85a2574\n> -.. _registerCamera: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#adf02a7f1bbd87aca73c0e8d8e0e6c98b\n> +.. _Camera::create: https://libcamera.org/api-html/classlibcamera_1_1Camera.html#a453740e0d2a2f495048ae307a85a2574\n> +.. _registerCamera: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#adf02a7f1bbd87aca73c0e8d8e0e6c98b\n>\n>  .. code-block:: cpp\n>\n> @@ -590,9 +590,9 @@ processed to automatically generate documentation and interfaces. Controls are\n>  defined by the src/libcamera/`control_ids.yaml`_ file and camera properties\n>  are defined by src/libcamera/`properties_ids.yaml`_.\n>\n> -.. _controls framework: http://libcamera.org/api-html/controls_8h.html\n> -.. _control_ids.yaml: http://libcamera.org/api-html/control__ids_8h.html\n> -.. _properties_ids.yaml: http://libcamera.org/api-html/property__ids_8h.html\n> +.. _controls framework: https://libcamera.org/api-html/controls_8h.html\n> +.. _control_ids.yaml: https://libcamera.org/api-html/control__ids_8h.html\n> +.. _properties_ids.yaml: https://libcamera.org/api-html/property__ids_8h.html\n>\n>  Pipeline handlers can optionally register the list of controls an application\n>  can set as well as a list of immutable camera properties. Being both\n> @@ -600,14 +600,14 @@ Camera-specific values, they are represented in the ``Camera::Private`` base\n>  class, which provides two members for this purpose: the\n>  `Camera::Private::controlInfo_`_ and the `Camera::Private::properties_`_ fields.\n>\n> -.. _Camera::Private::controlInfo_: http://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html#ab4e183eb4dabe929d1b2bbbb519b969f\n> -.. _Camera::Private::properties_: http://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html#ad31f12f5ed9c1fbe25750902f4791064\n> +.. _Camera::Private::controlInfo_: https://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html#ab4e183eb4dabe929d1b2bbbb519b969f\n> +.. _Camera::Private::properties_: https://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html#ad31f12f5ed9c1fbe25750902f4791064\n>\n>  The ``controlInfo_`` field represents a map of ``ControlId`` instances\n>  associated with the limits of valid values supported for the control. More\n>  information can be found in the `ControlInfoMap`_ class documentation.\n>\n> -.. _ControlInfoMap: http://libcamera.org/api-html/classlibcamera_1_1ControlInfoMap.html\n> +.. _ControlInfoMap: https://libcamera.org/api-html/classlibcamera_1_1ControlInfoMap.html\n>\n>  Pipeline handlers register controls to expose the tunable device and IPA\n>  parameters to applications. Our example pipeline handler only exposes trivial\n> @@ -700,7 +700,7 @@ To support validation in our example pipeline handler, Create a new class called\n>  ``VividCameraConfiguration`` derived from the base `CameraConfiguration`_ class\n>  which we can implement and use within our ``PipelineHandlerVivid`` class.\n>\n> -.. _CameraConfiguration: http://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html\n> +.. _CameraConfiguration: https://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html\n>\n>  The derived ``CameraConfiguration`` class must override the base class\n>  ``validate()`` function, where the stream configuration inspection and\n> @@ -726,8 +726,8 @@ Applications generate a ``CameraConfiguration`` instance by calling the\n>  implementation of the overridden `PipelineHandler::generateConfiguration()`_\n>  function.\n>\n> -.. _Camera::generateConfiguration(): http://libcamera.org/api-html/classlibcamera_1_1Camera.html#a25c80eb7fc9b1cf32692ce0c7f09991d\n> -.. _PipelineHandler::generateConfiguration(): http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a7932e87735695500ce1f8c7ae449b65b\n> +.. _Camera::generateConfiguration(): https://libcamera.org/api-html/classlibcamera_1_1Camera.html#a25c80eb7fc9b1cf32692ce0c7f09991d\n> +.. _PipelineHandler::generateConfiguration(): https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a7932e87735695500ce1f8c7ae449b65b\n>\n>  Configurations are generated by receiving a list of ``StreamRoles`` instances,\n>  which libcamera uses as predefined ways an application intends to use a camera\n> @@ -735,7 +735,7 @@ which libcamera uses as predefined ways an application intends to use a camera\n>  optional hints on how an application intends to use a stream, and a pipeline\n>  handler should return an ideal configuration for each role that is requested.\n>\n> -.. _StreamRole API: http://libcamera.org/api-html/stream_8h.html#file_a295d1f5e7828d95c0b0aabc0a8baac03\n> +.. _StreamRole API: https://libcamera.org/api-html/stream_8h.html#file_a295d1f5e7828d95c0b0aabc0a8baac03\n>\n>  In the pipeline handler ``generateConfiguration`` implementation, remove the\n>  ``return nullptr;``, create a new instance of the ``CameraConfiguration``\n> @@ -796,7 +796,7 @@ The `StreamFormats`_ class holds information about the pixel formats and frame\n>  sizes that a stream can support. The class groups size information by the pixel\n>  format, which can produce it.\n>\n> -.. _StreamFormats: http://libcamera.org/api-html/classlibcamera_1_1StreamFormats.html\n> +.. _StreamFormats: https://libcamera.org/api-html/classlibcamera_1_1StreamFormats.html\n>\n>  The code below uses the ``StreamFormats`` class to represent all of the\n>  supported pixel formats, associated with a list of frame sizes. It then\n> @@ -849,7 +849,7 @@ If changes are made, it marks the configuration as ``Adjusted``, however if the\n>  requested configuration is not supported and cannot be adjusted it shall be\n>  refused and marked as ``Invalid``.\n>\n> -.. _CameraConfiguration::validate(): http://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html#a29f8f263384c6149775b6011c7397093\n> +.. _CameraConfiguration::validate(): https://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html#a29f8f263384c6149775b6011c7397093\n>\n>  The validation phase makes sure all the platform-specific constraints are\n>  respected by the requested configuration. The most trivial examples being making\n> @@ -949,8 +949,8 @@ The `PipelineHandler::configure()`_ function receives a valid\n>  parameters to prepare a device for a streaming session with the desired\n>  properties.\n>\n> -.. _PipelineHandler::configure(): http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a930f2a9cdfb51dfb4b9ca3824e84fc29\n> -.. _CameraConfiguration: http://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html\n> +.. _PipelineHandler::configure(): https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a930f2a9cdfb51dfb4b9ca3824e84fc29\n> +.. _CameraConfiguration: https://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html\n>\n>  Replace the contents of the stubbed ``PipelineHandlerVivid::configure`` function\n>  with the following to obtain the camera data and stream configuration. This\n> @@ -972,8 +972,8 @@ node. The fourcc attribute is a `V4L2PixelFormat`_ and differs from the\n>  plane configuration for multiplanar formats, so you must explicitly convert it\n>  using the helper ``V4L2PixelFormat::fromPixelFormat()``.\n>\n> -.. _V4L2DeviceFormat: http://libcamera.org/api-html/classlibcamera_1_1V4L2DeviceFormat.html\n> -.. _V4L2PixelFormat: http://libcamera.org/api-html/classlibcamera_1_1V4L2PixelFormat.html\n> +.. _V4L2DeviceFormat: https://libcamera.org/api-html/classlibcamera_1_1V4L2DeviceFormat.html\n> +.. _V4L2PixelFormat: https://libcamera.org/api-html/classlibcamera_1_1V4L2PixelFormat.html\n>\n>  Add the following code beneath the code from above:\n>\n> @@ -989,7 +989,7 @@ driver has adjusted the format, as this shows the pipeline handler has failed to\n>  handle the validation stages correctly, and the configure operation shall also\n>  fail.\n>\n> -.. _V4L2VideoDevice::setFormat(): http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#ad67b47dd9327ce5df43350b80c083cca\n> +.. _V4L2VideoDevice::setFormat(): https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#ad67b47dd9327ce5df43350b80c083cca\n>\n>  Continue the implementation with the following code:\n>\n> @@ -1008,7 +1008,7 @@ Associate the configuration with the stream by using the\n>  `StreamConfiguration::setStream`_ function, and set the values of individual\n>  stream configuration members as required.\n>\n> -.. _StreamConfiguration::setStream: http://libcamera.org/api-html/structlibcamera_1_1StreamConfiguration.html#a74a0eb44dad1b00112c7c0443ae54a12\n> +.. _StreamConfiguration::setStream: https://libcamera.org/api-html/structlibcamera_1_1StreamConfiguration.html#a74a0eb44dad1b00112c7c0443ae54a12\n>\n>  .. NOTE: the cfg.setStream() call here associates the stream to the\n>     StreamConfiguration however that should quite likely be done as part of\n> @@ -1033,7 +1033,7 @@ controls at system configuration time, to make sure they are defaulted to sane\n>  values. Handling of device controls is again performed using the libcamera\n>  `controls framework`_.\n>\n> -.. _Controls Framework: http://libcamera.org/api-html/controls_8h.html\n> +.. _Controls Framework: https://libcamera.org/api-html/controls_8h.html\n>\n>  This section is particularly specific to Vivid as it sets the initial values of\n>  controls to match `Vivid Controls`_ defined by the kernel driver. You won't need\n> @@ -1056,8 +1056,8 @@ come directly from the kernel sources:\n>  We can now use the V4L2 control IDs to prepare a list of controls with the\n>  `ControlList`_ class, and set them using the `ControlList::set()`_ function.\n>\n> -.. _ControlList: http://libcamera.org/api-html/classlibcamera_1_1ControlList.html\n> -.. _ControlList::set(): http://libcamera.org/api-html/classlibcamera_1_1ControlList.html#a74a1a29abff5243e6e37ace8e24eb4ba\n> +.. _ControlList: https://libcamera.org/api-html/classlibcamera_1_1ControlList.html\n> +.. _ControlList::set(): https://libcamera.org/api-html/classlibcamera_1_1ControlList.html#a74a1a29abff5243e6e37ace8e24eb4ba\n>\n>  In our pipeline ``configure`` function, add the following code after the format\n>  has been set and checked to initialise the ControlList and apply it to the\n> @@ -1111,16 +1111,16 @@ libcamera also provides an API to allocate and export memory to applications\n>  realized through the `exportFrameBuffers`_ function and the\n>  `FrameBufferAllocator`_ class which will be presented later.\n>\n> -.. _exportFrameBuffers: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a6312a69da7129c2ed41f9d9f790adf7c\n> -.. _FrameBufferAllocator: http://libcamera.org/api-html/classlibcamera_1_1FrameBufferAllocator.html\n> +.. _exportFrameBuffers: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a6312a69da7129c2ed41f9d9f790adf7c\n> +.. _FrameBufferAllocator: https://libcamera.org/api-html/classlibcamera_1_1FrameBufferAllocator.html\n>\n>  Please refer to the V4L2VideoDevice API documentation, specifically the\n>  `allocateBuffers`_, `importBuffers`_ and `exportBuffers`_ functions for a\n>  detailed description of the video device memory management.\n>\n> -.. _allocateBuffers: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a3a1a77e5e6c220ea7878e89485864a1c\n> -.. _importBuffers: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a154f5283d16ebd5e15d63e212745cb64\n> -.. _exportBuffers: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#ae9c0b0a68f350725b63b73a6da5a2ecd\n> +.. _allocateBuffers: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a3a1a77e5e6c220ea7878e89485864a1c\n> +.. _importBuffers: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a154f5283d16ebd5e15d63e212745cb64\n> +.. _exportBuffers: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#ae9c0b0a68f350725b63b73a6da5a2ecd\n>\n>  Video memory buffers are represented in libcamera by the `FrameBuffer`_ class.\n>  A ``FrameBuffer`` instance has to be associated to each ``Stream`` which is part\n> @@ -1129,7 +1129,7 @@ by importing the dma-buf file descriptors it needs to operate on. This operation\n>  is performed by using the ``V4L2VideoDevice`` API, which provides an\n>  ``importBuffers()`` function that prepares the video device accordingly.\n>\n> -.. _FrameBuffer: http://libcamera.org/api-html/classlibcamera_1_1FrameBuffer.html\n> +.. _FrameBuffer: https://libcamera.org/api-html/classlibcamera_1_1FrameBuffer.html\n>\n>  Implement the pipeline handler ``start()`` function by replacing the stub\n>  version with the following code:\n> @@ -1160,13 +1160,13 @@ and exports it as dma-buf file descriptors. From this point on, the allocated\n>  imported by the pipeline hander in exactly the same fashion as if they were\n>  allocated elsewhere.\n>\n> -.. _FrameBufferAllocator: http://libcamera.org/api-html/classlibcamera_1_1FrameBufferAllocator.html\n> +.. _FrameBufferAllocator: https://libcamera.org/api-html/classlibcamera_1_1FrameBufferAllocator.html\n>\n>  Pipeline handlers support the ``FrameBufferAllocator`` operations by\n>  implementing the `exportFrameBuffers`_ function, which will allocate memory in\n>  the video device associated with a stream and export it.\n>\n> -.. _exportFrameBuffers: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a6312a69da7129c2ed41f9d9f790adf7c\n> +.. _exportFrameBuffers: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a6312a69da7129c2ed41f9d9f790adf7c\n>\n>  Implement the ``exportFrameBuffers`` stub function with the following code to\n>  handle this:\n> @@ -1198,14 +1198,14 @@ caller and the `releaseBuffers`_ function releases any buffers to leave the\n>  device in a consistent state. If your pipeline handler uses any image processing\n>  algorithms, or other devices you should also stop them.\n>\n> -.. _streamOn: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a588a5dc9d6f4c54c61136ac43ff9a8cc\n> -.. _releaseBuffers: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a191619c152f764e03bc461611f3fcd35\n> +.. _streamOn: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a588a5dc9d6f4c54c61136ac43ff9a8cc\n> +.. _releaseBuffers: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a191619c152f764e03bc461611f3fcd35\n>\n>  Of course we also need to handle the corresponding actions to stop streaming on\n>  a device, Add the following to the ``stop`` function, to stop the stream with\n>  the `streamOff`_ function and release all buffers.\n>\n> -.. _streamOff: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a61998710615bdf7aa25a046c8565ed66\n> +.. _streamOff: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a61998710615bdf7aa25a046c8565ed66\n>\n>  .. code-block:: cpp\n>\n> @@ -1228,8 +1228,8 @@ This example pipeline handler identifies the buffer using the `findBuffer`_\n>  helper from the only supported stream and queues it to the capture device\n>  directly with the `queueBuffer`_ function provided by the V4L2VideoDevice.\n>\n> -.. _findBuffer: http://libcamera.org/api-html/classlibcamera_1_1Request.html#ac66050aeb9b92c64218945158559c4d4\n> -.. _queueBuffer: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a594cd594686a8c1cf9ae8dba0b2a8a75\n> +.. _findBuffer: https://libcamera.org/api-html/classlibcamera_1_1Request.html#ac66050aeb9b92c64218945158559c4d4\n> +.. _queueBuffer: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a594cd594686a8c1cf9ae8dba0b2a8a75\n>\n>  Replace the stubbed contents of ``queueRequestDevice`` with the following:\n>\n> @@ -1328,7 +1328,7 @@ This example pipeline handler applies controls during the `queueRequestDevice`_\n>  function for each request, and applies them to the capture device through the\n>  capture node.\n>\n> -.. _queueRequestDevice: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a106914cca210640c9da9ee1f0419e83c\n> +.. _queueRequestDevice: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a106914cca210640c9da9ee1f0419e83c\n>\n>  In the ``queueRequestDevice`` function, replace the following:\n>\n> @@ -1369,7 +1369,7 @@ of the libcamera implementation is available in the `libcamera Signal and Slot`_\n>  classes documentation.\n>\n>  .. _Qt Signals and Slots: https://doc.qt.io/qt-5/signalsandslots.html\n> -.. _libcamera Signal and Slot: http://libcamera.org/api-html/classlibcamera_1_1Signal.html#details\n> +.. _libcamera Signal and Slot: https://libcamera.org/api-html/classlibcamera_1_1Signal.html#details\n>\n>  In order to notify applications about the availability of new frames and data,\n>  the ``Camera`` device exposes two ``Signals`` to which applications can connect\n> @@ -1396,7 +1396,7 @@ the PipelineHandler base class ``completeRequest`` function. The PipelineHandler\n>  class implementation makes sure the request completion notifications are\n>  delivered to applications in the same order as they have been submitted.\n>\n> -.. _connecting: http://libcamera.org/api-html/classlibcamera_1_1Signal.html#aa04db72d5b3091ffbb4920565aeed382\n> +.. _connecting: https://libcamera.org/api-html/classlibcamera_1_1Signal.html#aa04db72d5b3091ffbb4920565aeed382\n>\n>  Returning to the ``int VividCameraData::init()`` function, add the following\n>  above the closing ``return 0;`` to connect the pipeline handler ``bufferReady``\n> --\n> 2.35.1\n>","headers":{"Return-Path":"<libcamera-devel-bounces@lists.libcamera.org>","X-Original-To":"parsemail@patchwork.libcamera.org","Delivered-To":"parsemail@patchwork.libcamera.org","Received":["from lancelot.ideasonboard.com (lancelot.ideasonboard.com\n\t[92.243.16.209])\n\tby patchwork.libcamera.org (Postfix) with ESMTPS id B2835C0F2A\n\tfor <parsemail@patchwork.libcamera.org>;\n\tWed,  4 May 2022 07:12:36 +0000 (UTC)","from lancelot.ideasonboard.com (localhost [IPv6:::1])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTP id 6E98965642;\n\tWed,  4 May 2022 09:12:36 +0200 (CEST)","from relay10.mail.gandi.net (relay10.mail.gandi.net\n\t[217.70.178.230])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTPS id 009D9604A3\n\tfor <libcamera-devel@lists.libcamera.org>;\n\tWed,  4 May 2022 09:12:34 +0200 (CEST)","(Authenticated sender: jacopo@jmondi.org)\n\tby mail.gandi.net (Postfix) with ESMTPSA id 672E6240006;\n\tWed,  4 May 2022 07:12:34 +0000 (UTC)"],"DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/simple; d=libcamera.org;\n\ts=mail; t=1651648356;\n\tbh=q21CFZkT+xhc/VEYrjd4DfGOac7+Z/Vb9m2poSHndFU=;\n\th=Date:To:References:In-Reply-To:Subject:List-Id:List-Unsubscribe:\n\tList-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:\n\tFrom;\n\tb=WuPD5JUdt60O9VuecQ/gvxMi4oIilW6pRQpuinblddlDhk1sPdF8escT+rxdNNORE\n\tX3MKAjcmXOLwjGWJrNZ12PT3RfS4rczhQI/nbYjnu5TDgTyE5SCoCW6QCu0vFiDxA6\n\tXnwvZT32cfl0xcDCK4cRyL0xV/gNO7hJK0kdTaTCp/yEZg5rxDMorN4rCxGk+lAKzm\n\troQ9r5OG3mX1RycHJv0YLl7yRaYOZ4BSFZTSBY7iSGS/QeD6F6nbEVO3dD2CLzX0Z8\n\tPvqaBNy7oZxnfIDogKMBuWFUoingXRDvWVGCFXOTmYAv21PxDPUnipQzSM/L2L3vX8\n\tk5ovgcz8U29vA==","Date":"Wed, 4 May 2022 09:12:32 +0200","To":"Quentin Schulz <foss+libcamera@0leil.net>","Message-ID":"<20220504071232.5k3ggf63umpw6nev@uno.localdomain>","References":"<20220503163038.1174462-1-foss+libcamera@0leil.net>\n\t<20220503163038.1174462-3-foss+libcamera@0leil.net>","MIME-Version":"1.0","Content-Type":"text/plain; charset=utf-8","Content-Disposition":"inline","In-Reply-To":"<20220503163038.1174462-3-foss+libcamera@0leil.net>","Subject":"Re: [libcamera-devel] [PATCH 3/3] Documentation: use https instead\n\tof http","X-BeenThere":"libcamera-devel@lists.libcamera.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"<libcamera-devel.lists.libcamera.org>","List-Unsubscribe":"<https://lists.libcamera.org/options/libcamera-devel>,\n\t<mailto:libcamera-devel-request@lists.libcamera.org?subject=unsubscribe>","List-Archive":"<https://lists.libcamera.org/pipermail/libcamera-devel/>","List-Post":"<mailto:libcamera-devel@lists.libcamera.org>","List-Help":"<mailto:libcamera-devel-request@lists.libcamera.org?subject=help>","List-Subscribe":"<https://lists.libcamera.org/listinfo/libcamera-devel>,\n\t<mailto:libcamera-devel-request@lists.libcamera.org?subject=subscribe>","From":"Jacopo Mondi via libcamera-devel <libcamera-devel@lists.libcamera.org>","Reply-To":"Jacopo Mondi <jacopo@jmondi.org>","Cc":"libcamera-devel@lists.libcamera.org","Errors-To":"libcamera-devel-bounces@lists.libcamera.org","Sender":"\"libcamera-devel\" <libcamera-devel-bounces@lists.libcamera.org>"}},{"id":22844,"web_url":"https://patchwork.libcamera.org/comment/22844/","msgid":"<165165755432.4076486.16783220744826624607@Monstersaurus>","date":"2022-05-04T09:45:54","subject":"Re: [libcamera-devel] [PATCH 3/3] Documentation: use https instead\n\tof http","submitter":{"id":4,"url":"https://patchwork.libcamera.org/api/people/4/","name":"Kieran Bingham","email":"kieran.bingham@ideasonboard.com"},"content":"Quoting Quentin Schulz via libcamera-devel (2022-05-03 17:30:38)\n> From: Quentin Schulz <quentin.schulz@theobroma-systems.com>\n> \n> Avoid a redirection from http by using https directly.\n> \n> Cc: Quentin Schulz <foss+libcamera@0leil.net>\n> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>\n\nReviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>\n\n> ---\n>  Documentation/contributing.rst                |   4 +-\n>  Documentation/environment_variables.rst       |   2 +-\n>  .../guides/application-developer.rst          |   8 +-\n>  Documentation/guides/introduction.rst         |   6 +-\n>  Documentation/guides/pipeline-handler.rst     | 116 +++++++++---------\n>  5 files changed, 68 insertions(+), 68 deletions(-)\n> \n> diff --git a/Documentation/contributing.rst b/Documentation/contributing.rst\n> index 57bc9acc..6405c5fb 100644\n> --- a/Documentation/contributing.rst\n> +++ b/Documentation/contributing.rst\n> @@ -56,8 +56,8 @@ Documentation\n>  Project documentation is created using `Sphinx`_.  Source level documentation\n>  uses `Doxygen`_.  Please make sure to document all code during development.\n>  \n> -.. _Sphinx: http://www.sphinx-doc.org\n> -.. _Doxygen: http://www.doxygen.nl\n> +.. _Sphinx: https://www.sphinx-doc.org\n> +.. _Doxygen: https://www.doxygen.nl\n>  \n>  Submitting Patches\n>  ------------------\n> diff --git a/Documentation/environment_variables.rst b/Documentation/environment_variables.rst\n> index 1e85befd..fa703a72 100644\n> --- a/Documentation/environment_variables.rst\n> +++ b/Documentation/environment_variables.rst\n> @@ -54,7 +54,7 @@ The optional `category <Log categories_>`__ is a string matching the categories\n>  defined by each file in the source base using the logging infrastructure. It\n>  can include a wildcard ('*') character at the end to match multiple categories.\n>  \n> -For more information refer to the `API documentation <http://libcamera.org/api-html/log_8h.html#details>`__.\n> +For more information refer to the `API documentation <https://libcamera.org/api-html/log_8h.html#details>`__.\n>  \n>  Examples:\n>  \n> diff --git a/Documentation/guides/application-developer.rst b/Documentation/guides/application-developer.rst\n> index 07cc7273..16bea9c4 100644\n> --- a/Documentation/guides/application-developer.rst\n> +++ b/Documentation/guides/application-developer.rst\n> @@ -49,7 +49,7 @@ abstracts and manages the complex pipelines that kernel drivers expose through\n>  the `Linux Media Controller`_ and `Video for Linux`_ (V4L2) APIs, meaning that\n>  an application doesn't need to handle device or driver specific details.\n>  \n> -.. _CameraManager: http://libcamera.org/api-html/classlibcamera_1_1CameraManager.html\n> +.. _CameraManager: https://libcamera.org/api-html/classlibcamera_1_1CameraManager.html\n>  .. _Linux Media Controller: https://www.kernel.org/doc/html/latest/media/uapi/mediactl/media-controller-intro.html\n>  .. _Video for Linux: https://www.linuxtv.org/docs.php\n>  \n> @@ -207,7 +207,7 @@ supported values.\n>  The ``validate`` function returns a `Status`_ which applications shall check to\n>  see if the Pipeline Handler adjusted the configuration.\n>  \n> -.. _Status: http://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html#a64163f21db2fe1ce0a6af5a6f6847744\n> +.. _Status: https://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html#a64163f21db2fe1ce0a6af5a6f6847744\n>  \n>  For example, the code above set the width and height to 640x480, but if the\n>  camera cannot produce an image that large, it might adjust the configuration to\n> @@ -345,7 +345,7 @@ Event handling and callbacks\n>  The libcamera library uses the concept of `signals and slots` (similar to `Qt\n>  Signals and Slots`_) to connect events with callbacks to handle them.\n>  \n> -.. _signals and slots: http://libcamera.org/api-html/classlibcamera_1_1Signal.html#details\n> +.. _signals and slots: https://libcamera.org/api-html/classlibcamera_1_1Signal.html#details\n>  .. _Qt Signals and Slots: https://doc.qt.io/qt-5/signalsandslots.html\n>  \n>  The ``Camera`` device emits two signals that applications can connect to in\n> @@ -418,7 +418,7 @@ in this request, and access the metadata associated to each frame.\n>  The metadata buffer contains information such the capture status, a timestamp,\n>  and the bytes used, as described in the `FrameMetadata`_ documentation.\n>  \n> -.. _FrameMetaData: http://libcamera.org/api-html/structlibcamera_1_1FrameMetadata.html\n> +.. _FrameMetaData: https://libcamera.org/api-html/structlibcamera_1_1FrameMetadata.html\n>  \n>  .. code:: cpp\n>  \n> diff --git a/Documentation/guides/introduction.rst b/Documentation/guides/introduction.rst\n> index 07f66881..2d1760c1 100644\n> --- a/Documentation/guides/introduction.rst\n> +++ b/Documentation/guides/introduction.rst\n> @@ -214,7 +214,7 @@ Camera Manager\n>  \n>    Read the `Camera Manager API`_ documentation for more details.\n>  \n> -.. _Camera Manager API: http://libcamera.org/api-html/classlibcamera_1_1CameraManager.html\n> +.. _Camera Manager API: https://libcamera.org/api-html/classlibcamera_1_1CameraManager.html\n>  \n>  Camera Device\n>    The Camera class represents a single item of camera hardware that is capable\n> @@ -231,7 +231,7 @@ Camera Device\n>  \n>    Read the `Camera API`_ documentation for more details.\n>  \n> -..  _Camera API: http://libcamera.org/api-html/classlibcamera_1_1Camera.html\n> +.. _Camera API: https://libcamera.org/api-html/classlibcamera_1_1Camera.html\n>  \n>  Pipeline Handler\n>    The Pipeline Handler manages the complex pipelines exposed by the kernel\n> @@ -254,7 +254,7 @@ Pipeline Handler\n>    More details can be found in the `PipelineHandler API`_ documentation, and the\n>    `Pipeline Handler Writers Guide`_.\n>  \n> -.. _PipelineHandler API: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html\n> +.. _PipelineHandler API: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html\n>  \n>  Image Processing Algorithms\n>    An image processing algorithm (IPA) component is a loadable plugin that\n> diff --git a/Documentation/guides/pipeline-handler.rst b/Documentation/guides/pipeline-handler.rst\n> index 989b0163..8e3f991d 100644\n> --- a/Documentation/guides/pipeline-handler.rst\n> +++ b/Documentation/guides/pipeline-handler.rst\n> @@ -81,49 +81,49 @@ functionalities described above. Below is a brief overview of each of those:\n>  .. TODO: (MediaDevice) Reference to the Media Device API (possibly with versioning requirements)\n>  .. TODO: (IPAInterface) refer to the IPA guide\n>  \n> --  `MediaDevice <http://libcamera.org/api-html/classlibcamera_1_1MediaDevice.html>`_:\n> +-  `MediaDevice <https://libcamera.org/api-html/classlibcamera_1_1MediaDevice.html>`_:\n>     Instances of this class are associated with a kernel media controller\n>     device and its connected objects.\n>  \n> --  `DeviceEnumerator <http://libcamera.org/api-html/classlibcamera_1_1DeviceEnumerator.html>`_:\n> +-  `DeviceEnumerator <https://libcamera.org/api-html/classlibcamera_1_1DeviceEnumerator.html>`_:\n>     Enumerates all media devices attached to the system and the media entities\n>     registered with it, by creating instances of the ``MediaDevice`` class and\n>     storing them.\n>  \n> --  `DeviceMatch <http://libcamera.org/api-html/classlibcamera_1_1DeviceMatch.html>`_:\n> +-  `DeviceMatch <https://libcamera.org/api-html/classlibcamera_1_1DeviceMatch.html>`_:\n>     Describes a media device search pattern using entity names, or other\n>     properties.\n>  \n> --  `V4L2VideoDevice <http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html>`_:\n> +-  `V4L2VideoDevice <https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html>`_:\n>     Models an instance of a V4L2 video device constructed with the path to a V4L2\n>     video device node.\n>  \n> --  `V4L2SubDevice <http://libcamera.org/api-html/classlibcamera_1_1V4L2Subdevice.html>`_:\n> +-  `V4L2SubDevice <https://libcamera.org/api-html/classlibcamera_1_1V4L2Subdevice.html>`_:\n>     Provides an API to the sub-devices that model the hardware components of a\n>     V4L2 device.\n>  \n> --  `CameraSensor <http://libcamera.org/api-html/classlibcamera_1_1CameraSensor.html>`_:\n> +-  `CameraSensor <https://libcamera.org/api-html/classlibcamera_1_1CameraSensor.html>`_:\n>     Abstracts camera sensor handling by hiding the details of the V4L2 subdevice\n>     kernel API and caching sensor information.\n>  \n> --  `Camera::Private <http://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html>`_:\n> +-  `Camera::Private <https://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html>`_:\n>     Represents device-specific data a pipeline handler associates to each Camera\n>     instance.\n>  \n> --  `StreamConfiguration <http://libcamera.org/api-html/structlibcamera_1_1StreamConfiguration.html>`_:\n> +-  `StreamConfiguration <https://libcamera.org/api-html/structlibcamera_1_1StreamConfiguration.html>`_:\n>     Models the current configuration of an image stream produced by the camera by\n>     reporting its format and sizes.\n>  \n> --  `CameraConfiguration <http://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html>`_:\n> +-  `CameraConfiguration <https://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html>`_:\n>     Represents the current configuration of a camera, which includes a list of\n>     stream configurations for each active stream in a capture session. When\n>     validated, it is applied to the camera.\n>  \n> --  `IPAInterface <http://libcamera.org/api-html/classlibcamera_1_1IPAInterface.html>`_:\n> +-  `IPAInterface <https://libcamera.org/api-html/classlibcamera_1_1IPAInterface.html>`_:\n>     The interface to the Image Processing Algorithm (IPA) module which performs\n>     the computation of the image processing pipeline tuning parameters.\n>  \n> --  `ControlList <http://libcamera.org/api-html/classlibcamera_1_1ControlList.html>`_:\n> +-  `ControlList <https://libcamera.org/api-html/classlibcamera_1_1ControlList.html>`_:\n>     A list of control items, indexed by Control<> instances or by numerical index\n>     which contains values used by application and IPA to change parameters of\n>     image streams, used to return to applications and share with IPA the metadata\n> @@ -191,7 +191,7 @@ In *vivid.cpp* add the pipeline handler to the ``libcamera`` namespace, defining\n>  a `PipelineHandler`_ derived class named PipelineHandlerVivid, and add stub\n>  implementations for the overridden class members.\n>  \n> -.. _PipelineHandler: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html\n> +.. _PipelineHandler: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html\n>  \n>  .. code-block:: cpp\n>  \n> @@ -267,7 +267,7 @@ handler factory using the `REGISTER_PIPELINE_HANDLER`_ macro which\n>  registers it and creates a global symbol to reference the class and make it\n>  available to try and match devices.\n>  \n> -.. _REGISTER_PIPELINE_HANDLER: http://libcamera.org/api-html/pipeline__handler_8h.html\n> +.. _REGISTER_PIPELINE_HANDLER: https://libcamera.org/api-html/pipeline__handler_8h.html\n>  \n>  For debugging and testing a pipeline handler during development, you can define\n>  a log message category for the pipeline handler. The ``LOG_DEFINE_CATEGORY``\n> @@ -275,7 +275,7 @@ macro and ``LIBCAMERA_LOG_LEVELS`` environment variable help you use the inbuilt\n>  libcamera `logging infrastructure`_ that allow for the inspection of internal\n>  operations in a user-configurable way.\n>  \n> -.. _logging infrastructure: http://libcamera.org/api-html/log_8h.html\n> +.. _logging infrastructure: https://libcamera.org/api-html/log_8h.html\n>  \n>  Add the following before the ``PipelineHandlerVivid`` class declaration:\n>  \n> @@ -334,8 +334,8 @@ You can specify the search further by adding specific media entities to the\n>  search using the ``.add()`` function on the DeviceMatch.\n>  \n>  .. _match(): https://www.libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a7cd5b652a2414b543ec20ba9dabf61b6\n> -.. _start(): http://libcamera.org/api-html/classlibcamera_1_1CameraManager.html#a49e322880a2a26013bb0076788b298c5\n> -.. _DeviceMatch: http://libcamera.org/api-html/classlibcamera_1_1DeviceMatch.html\n> +.. _start(): https://libcamera.org/api-html/classlibcamera_1_1CameraManager.html#a49e322880a2a26013bb0076788b298c5\n> +.. _DeviceMatch: https://libcamera.org/api-html/classlibcamera_1_1DeviceMatch.html\n>  \n>  This example uses search patterns that match vivid, but when developing a new\n>  pipeline handler, you should change this value to suit your device identifier.\n> @@ -354,7 +354,7 @@ to the matching media controller device with the `acquireMediaDevice`_ function.\n>  If the function attempts to acquire a device it has already matched, it returns\n>  ``false``.\n>  \n> -.. _acquireMediaDevice: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a77e424fe704e7b26094164b9189e0f84\n> +.. _acquireMediaDevice: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a77e424fe704e7b26094164b9189e0f84\n>  \n>  Add the following below ``dm.add(\"vivid-000-vid-cap\");``:\n>  \n> @@ -419,7 +419,7 @@ with the Camera.\n>  Each Camera has instance-specific data represented using the `Camera::Private`_\n>  class, which can be extended for the specific needs of the pipeline handler.\n>  \n> -.. _Camera::Private: http://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html\n> +.. _Camera::Private: https://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html\n>  \n>  \n>  To support the Camera we will later register, we need to create a Camera::Private\n> @@ -475,7 +475,7 @@ the `MediaDevice::getEntityByName`_ function from the MediaDevice. As our\n>  example is based upon the simplistic Vivid test device, we only need to open a\n>  single capture device named 'vivid-000-vid-cap' by the device.\n>  \n> -.. _MediaDevice::getEntityByName: http://libcamera.org/api-html/classlibcamera_1_1MediaDevice.html#ad5d9279329ef4987ceece2694b33e230\n> +.. _MediaDevice::getEntityByName: https://libcamera.org/api-html/classlibcamera_1_1MediaDevice.html#ad5d9279329ef4987ceece2694b33e230\n>  \n>  .. code-block:: cpp\n>  \n> @@ -516,8 +516,8 @@ handler and camera manager using `registerCamera`_.\n>  Finally with a successful construction, we return 'true' indicating that the\n>  PipelineHandler successfully matched and constructed a device.\n>  \n> -.. _Camera::create: http://libcamera.org/api-html/classlibcamera_1_1Camera.html#a453740e0d2a2f495048ae307a85a2574\n> -.. _registerCamera: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#adf02a7f1bbd87aca73c0e8d8e0e6c98b\n> +.. _Camera::create: https://libcamera.org/api-html/classlibcamera_1_1Camera.html#a453740e0d2a2f495048ae307a85a2574\n> +.. _registerCamera: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#adf02a7f1bbd87aca73c0e8d8e0e6c98b\n>  \n>  .. code-block:: cpp\n>  \n> @@ -590,9 +590,9 @@ processed to automatically generate documentation and interfaces. Controls are\n>  defined by the src/libcamera/`control_ids.yaml`_ file and camera properties\n>  are defined by src/libcamera/`properties_ids.yaml`_.\n>  \n> -.. _controls framework: http://libcamera.org/api-html/controls_8h.html\n> -.. _control_ids.yaml: http://libcamera.org/api-html/control__ids_8h.html\n> -.. _properties_ids.yaml: http://libcamera.org/api-html/property__ids_8h.html\n> +.. _controls framework: https://libcamera.org/api-html/controls_8h.html\n> +.. _control_ids.yaml: https://libcamera.org/api-html/control__ids_8h.html\n> +.. _properties_ids.yaml: https://libcamera.org/api-html/property__ids_8h.html\n>  \n>  Pipeline handlers can optionally register the list of controls an application\n>  can set as well as a list of immutable camera properties. Being both\n> @@ -600,14 +600,14 @@ Camera-specific values, they are represented in the ``Camera::Private`` base\n>  class, which provides two members for this purpose: the\n>  `Camera::Private::controlInfo_`_ and the `Camera::Private::properties_`_ fields.\n>  \n> -.. _Camera::Private::controlInfo_: http://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html#ab4e183eb4dabe929d1b2bbbb519b969f\n> -.. _Camera::Private::properties_: http://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html#ad31f12f5ed9c1fbe25750902f4791064\n> +.. _Camera::Private::controlInfo_: https://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html#ab4e183eb4dabe929d1b2bbbb519b969f\n> +.. _Camera::Private::properties_: https://libcamera.org/api-html/classlibcamera_1_1Camera_1_1Private.html#ad31f12f5ed9c1fbe25750902f4791064\n>  \n>  The ``controlInfo_`` field represents a map of ``ControlId`` instances\n>  associated with the limits of valid values supported for the control. More\n>  information can be found in the `ControlInfoMap`_ class documentation.\n>  \n> -.. _ControlInfoMap: http://libcamera.org/api-html/classlibcamera_1_1ControlInfoMap.html\n> +.. _ControlInfoMap: https://libcamera.org/api-html/classlibcamera_1_1ControlInfoMap.html\n>  \n>  Pipeline handlers register controls to expose the tunable device and IPA\n>  parameters to applications. Our example pipeline handler only exposes trivial\n> @@ -700,7 +700,7 @@ To support validation in our example pipeline handler, Create a new class called\n>  ``VividCameraConfiguration`` derived from the base `CameraConfiguration`_ class\n>  which we can implement and use within our ``PipelineHandlerVivid`` class.\n>  \n> -.. _CameraConfiguration: http://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html\n> +.. _CameraConfiguration: https://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html\n>  \n>  The derived ``CameraConfiguration`` class must override the base class\n>  ``validate()`` function, where the stream configuration inspection and\n> @@ -726,8 +726,8 @@ Applications generate a ``CameraConfiguration`` instance by calling the\n>  implementation of the overridden `PipelineHandler::generateConfiguration()`_\n>  function.\n>  \n> -.. _Camera::generateConfiguration(): http://libcamera.org/api-html/classlibcamera_1_1Camera.html#a25c80eb7fc9b1cf32692ce0c7f09991d\n> -.. _PipelineHandler::generateConfiguration(): http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a7932e87735695500ce1f8c7ae449b65b\n> +.. _Camera::generateConfiguration(): https://libcamera.org/api-html/classlibcamera_1_1Camera.html#a25c80eb7fc9b1cf32692ce0c7f09991d\n> +.. _PipelineHandler::generateConfiguration(): https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a7932e87735695500ce1f8c7ae449b65b\n>  \n>  Configurations are generated by receiving a list of ``StreamRoles`` instances,\n>  which libcamera uses as predefined ways an application intends to use a camera\n> @@ -735,7 +735,7 @@ which libcamera uses as predefined ways an application intends to use a camera\n>  optional hints on how an application intends to use a stream, and a pipeline\n>  handler should return an ideal configuration for each role that is requested.\n>  \n> -.. _StreamRole API: http://libcamera.org/api-html/stream_8h.html#file_a295d1f5e7828d95c0b0aabc0a8baac03\n> +.. _StreamRole API: https://libcamera.org/api-html/stream_8h.html#file_a295d1f5e7828d95c0b0aabc0a8baac03\n>  \n>  In the pipeline handler ``generateConfiguration`` implementation, remove the\n>  ``return nullptr;``, create a new instance of the ``CameraConfiguration``\n> @@ -796,7 +796,7 @@ The `StreamFormats`_ class holds information about the pixel formats and frame\n>  sizes that a stream can support. The class groups size information by the pixel\n>  format, which can produce it.\n>  \n> -.. _StreamFormats: http://libcamera.org/api-html/classlibcamera_1_1StreamFormats.html\n> +.. _StreamFormats: https://libcamera.org/api-html/classlibcamera_1_1StreamFormats.html\n>  \n>  The code below uses the ``StreamFormats`` class to represent all of the\n>  supported pixel formats, associated with a list of frame sizes. It then\n> @@ -849,7 +849,7 @@ If changes are made, it marks the configuration as ``Adjusted``, however if the\n>  requested configuration is not supported and cannot be adjusted it shall be\n>  refused and marked as ``Invalid``.\n>  \n> -.. _CameraConfiguration::validate(): http://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html#a29f8f263384c6149775b6011c7397093\n> +.. _CameraConfiguration::validate(): https://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html#a29f8f263384c6149775b6011c7397093\n>  \n>  The validation phase makes sure all the platform-specific constraints are\n>  respected by the requested configuration. The most trivial examples being making\n> @@ -949,8 +949,8 @@ The `PipelineHandler::configure()`_ function receives a valid\n>  parameters to prepare a device for a streaming session with the desired\n>  properties.\n>  \n> -.. _PipelineHandler::configure(): http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a930f2a9cdfb51dfb4b9ca3824e84fc29\n> -.. _CameraConfiguration: http://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html\n> +.. _PipelineHandler::configure(): https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a930f2a9cdfb51dfb4b9ca3824e84fc29\n> +.. _CameraConfiguration: https://libcamera.org/api-html/classlibcamera_1_1CameraConfiguration.html\n>  \n>  Replace the contents of the stubbed ``PipelineHandlerVivid::configure`` function\n>  with the following to obtain the camera data and stream configuration. This\n> @@ -972,8 +972,8 @@ node. The fourcc attribute is a `V4L2PixelFormat`_ and differs from the\n>  plane configuration for multiplanar formats, so you must explicitly convert it\n>  using the helper ``V4L2PixelFormat::fromPixelFormat()``.\n>  \n> -.. _V4L2DeviceFormat: http://libcamera.org/api-html/classlibcamera_1_1V4L2DeviceFormat.html\n> -.. _V4L2PixelFormat: http://libcamera.org/api-html/classlibcamera_1_1V4L2PixelFormat.html\n> +.. _V4L2DeviceFormat: https://libcamera.org/api-html/classlibcamera_1_1V4L2DeviceFormat.html\n> +.. _V4L2PixelFormat: https://libcamera.org/api-html/classlibcamera_1_1V4L2PixelFormat.html\n>  \n>  Add the following code beneath the code from above:\n>  \n> @@ -989,7 +989,7 @@ driver has adjusted the format, as this shows the pipeline handler has failed to\n>  handle the validation stages correctly, and the configure operation shall also\n>  fail.\n>  \n> -.. _V4L2VideoDevice::setFormat(): http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#ad67b47dd9327ce5df43350b80c083cca\n> +.. _V4L2VideoDevice::setFormat(): https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#ad67b47dd9327ce5df43350b80c083cca\n>  \n>  Continue the implementation with the following code:\n>  \n> @@ -1008,7 +1008,7 @@ Associate the configuration with the stream by using the\n>  `StreamConfiguration::setStream`_ function, and set the values of individual\n>  stream configuration members as required.\n>  \n> -.. _StreamConfiguration::setStream: http://libcamera.org/api-html/structlibcamera_1_1StreamConfiguration.html#a74a0eb44dad1b00112c7c0443ae54a12\n> +.. _StreamConfiguration::setStream: https://libcamera.org/api-html/structlibcamera_1_1StreamConfiguration.html#a74a0eb44dad1b00112c7c0443ae54a12\n>  \n>  .. NOTE: the cfg.setStream() call here associates the stream to the\n>     StreamConfiguration however that should quite likely be done as part of\n> @@ -1033,7 +1033,7 @@ controls at system configuration time, to make sure they are defaulted to sane\n>  values. Handling of device controls is again performed using the libcamera\n>  `controls framework`_.\n>  \n> -.. _Controls Framework: http://libcamera.org/api-html/controls_8h.html\n> +.. _Controls Framework: https://libcamera.org/api-html/controls_8h.html\n>  \n>  This section is particularly specific to Vivid as it sets the initial values of\n>  controls to match `Vivid Controls`_ defined by the kernel driver. You won't need\n> @@ -1056,8 +1056,8 @@ come directly from the kernel sources:\n>  We can now use the V4L2 control IDs to prepare a list of controls with the\n>  `ControlList`_ class, and set them using the `ControlList::set()`_ function.\n>  \n> -.. _ControlList: http://libcamera.org/api-html/classlibcamera_1_1ControlList.html\n> -.. _ControlList::set(): http://libcamera.org/api-html/classlibcamera_1_1ControlList.html#a74a1a29abff5243e6e37ace8e24eb4ba\n> +.. _ControlList: https://libcamera.org/api-html/classlibcamera_1_1ControlList.html\n> +.. _ControlList::set(): https://libcamera.org/api-html/classlibcamera_1_1ControlList.html#a74a1a29abff5243e6e37ace8e24eb4ba\n>  \n>  In our pipeline ``configure`` function, add the following code after the format\n>  has been set and checked to initialise the ControlList and apply it to the\n> @@ -1111,16 +1111,16 @@ libcamera also provides an API to allocate and export memory to applications\n>  realized through the `exportFrameBuffers`_ function and the\n>  `FrameBufferAllocator`_ class which will be presented later.\n>  \n> -.. _exportFrameBuffers: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a6312a69da7129c2ed41f9d9f790adf7c\n> -.. _FrameBufferAllocator: http://libcamera.org/api-html/classlibcamera_1_1FrameBufferAllocator.html\n> +.. _exportFrameBuffers: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a6312a69da7129c2ed41f9d9f790adf7c\n> +.. _FrameBufferAllocator: https://libcamera.org/api-html/classlibcamera_1_1FrameBufferAllocator.html\n>  \n>  Please refer to the V4L2VideoDevice API documentation, specifically the\n>  `allocateBuffers`_, `importBuffers`_ and `exportBuffers`_ functions for a\n>  detailed description of the video device memory management.\n>  \n> -.. _allocateBuffers: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a3a1a77e5e6c220ea7878e89485864a1c\n> -.. _importBuffers: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a154f5283d16ebd5e15d63e212745cb64\n> -.. _exportBuffers: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#ae9c0b0a68f350725b63b73a6da5a2ecd\n> +.. _allocateBuffers: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a3a1a77e5e6c220ea7878e89485864a1c\n> +.. _importBuffers: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a154f5283d16ebd5e15d63e212745cb64\n> +.. _exportBuffers: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#ae9c0b0a68f350725b63b73a6da5a2ecd\n>  \n>  Video memory buffers are represented in libcamera by the `FrameBuffer`_ class.\n>  A ``FrameBuffer`` instance has to be associated to each ``Stream`` which is part\n> @@ -1129,7 +1129,7 @@ by importing the dma-buf file descriptors it needs to operate on. This operation\n>  is performed by using the ``V4L2VideoDevice`` API, which provides an\n>  ``importBuffers()`` function that prepares the video device accordingly.\n>  \n> -.. _FrameBuffer: http://libcamera.org/api-html/classlibcamera_1_1FrameBuffer.html\n> +.. _FrameBuffer: https://libcamera.org/api-html/classlibcamera_1_1FrameBuffer.html\n>  \n>  Implement the pipeline handler ``start()`` function by replacing the stub\n>  version with the following code:\n> @@ -1160,13 +1160,13 @@ and exports it as dma-buf file descriptors. From this point on, the allocated\n>  imported by the pipeline hander in exactly the same fashion as if they were\n>  allocated elsewhere.\n>  \n> -.. _FrameBufferAllocator: http://libcamera.org/api-html/classlibcamera_1_1FrameBufferAllocator.html\n> +.. _FrameBufferAllocator: https://libcamera.org/api-html/classlibcamera_1_1FrameBufferAllocator.html\n>  \n>  Pipeline handlers support the ``FrameBufferAllocator`` operations by\n>  implementing the `exportFrameBuffers`_ function, which will allocate memory in\n>  the video device associated with a stream and export it.\n>  \n> -.. _exportFrameBuffers: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a6312a69da7129c2ed41f9d9f790adf7c\n> +.. _exportFrameBuffers: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a6312a69da7129c2ed41f9d9f790adf7c\n>  \n>  Implement the ``exportFrameBuffers`` stub function with the following code to\n>  handle this:\n> @@ -1198,14 +1198,14 @@ caller and the `releaseBuffers`_ function releases any buffers to leave the\n>  device in a consistent state. If your pipeline handler uses any image processing\n>  algorithms, or other devices you should also stop them.\n>  \n> -.. _streamOn: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a588a5dc9d6f4c54c61136ac43ff9a8cc\n> -.. _releaseBuffers: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a191619c152f764e03bc461611f3fcd35\n> +.. _streamOn: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a588a5dc9d6f4c54c61136ac43ff9a8cc\n> +.. _releaseBuffers: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a191619c152f764e03bc461611f3fcd35\n>  \n>  Of course we also need to handle the corresponding actions to stop streaming on\n>  a device, Add the following to the ``stop`` function, to stop the stream with\n>  the `streamOff`_ function and release all buffers.\n>  \n> -.. _streamOff: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a61998710615bdf7aa25a046c8565ed66\n> +.. _streamOff: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a61998710615bdf7aa25a046c8565ed66\n>  \n>  .. code-block:: cpp\n>  \n> @@ -1228,8 +1228,8 @@ This example pipeline handler identifies the buffer using the `findBuffer`_\n>  helper from the only supported stream and queues it to the capture device\n>  directly with the `queueBuffer`_ function provided by the V4L2VideoDevice.\n>  \n> -.. _findBuffer: http://libcamera.org/api-html/classlibcamera_1_1Request.html#ac66050aeb9b92c64218945158559c4d4\n> -.. _queueBuffer: http://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a594cd594686a8c1cf9ae8dba0b2a8a75\n> +.. _findBuffer: https://libcamera.org/api-html/classlibcamera_1_1Request.html#ac66050aeb9b92c64218945158559c4d4\n> +.. _queueBuffer: https://libcamera.org/api-html/classlibcamera_1_1V4L2VideoDevice.html#a594cd594686a8c1cf9ae8dba0b2a8a75\n>  \n>  Replace the stubbed contents of ``queueRequestDevice`` with the following:\n>  \n> @@ -1328,7 +1328,7 @@ This example pipeline handler applies controls during the `queueRequestDevice`_\n>  function for each request, and applies them to the capture device through the\n>  capture node.\n>  \n> -.. _queueRequestDevice: http://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a106914cca210640c9da9ee1f0419e83c\n> +.. _queueRequestDevice: https://libcamera.org/api-html/classlibcamera_1_1PipelineHandler.html#a106914cca210640c9da9ee1f0419e83c\n>  \n>  In the ``queueRequestDevice`` function, replace the following:\n>  \n> @@ -1369,7 +1369,7 @@ of the libcamera implementation is available in the `libcamera Signal and Slot`_\n>  classes documentation.\n>  \n>  .. _Qt Signals and Slots: https://doc.qt.io/qt-5/signalsandslots.html\n> -.. _libcamera Signal and Slot: http://libcamera.org/api-html/classlibcamera_1_1Signal.html#details\n> +.. _libcamera Signal and Slot: https://libcamera.org/api-html/classlibcamera_1_1Signal.html#details\n>  \n>  In order to notify applications about the availability of new frames and data,\n>  the ``Camera`` device exposes two ``Signals`` to which applications can connect\n> @@ -1396,7 +1396,7 @@ the PipelineHandler base class ``completeRequest`` function. The PipelineHandler\n>  class implementation makes sure the request completion notifications are\n>  delivered to applications in the same order as they have been submitted.\n>  \n> -.. _connecting: http://libcamera.org/api-html/classlibcamera_1_1Signal.html#aa04db72d5b3091ffbb4920565aeed382\n> +.. _connecting: https://libcamera.org/api-html/classlibcamera_1_1Signal.html#aa04db72d5b3091ffbb4920565aeed382\n>  \n>  Returning to the ``int VividCameraData::init()`` function, add the following\n>  above the closing ``return 0;`` to connect the pipeline handler ``bufferReady``\n> -- \n> 2.35.1\n>","headers":{"Return-Path":"<libcamera-devel-bounces@lists.libcamera.org>","X-Original-To":"parsemail@patchwork.libcamera.org","Delivered-To":"parsemail@patchwork.libcamera.org","Received":["from lancelot.ideasonboard.com (lancelot.ideasonboard.com\n\t[92.243.16.209])\n\tby patchwork.libcamera.org (Postfix) with ESMTPS id 32F86C0F2A\n\tfor <parsemail@patchwork.libcamera.org>;\n\tWed,  4 May 2022 09:45:59 +0000 (UTC)","from lancelot.ideasonboard.com (localhost [IPv6:::1])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTP id 9A1FA65644;\n\tWed,  4 May 2022 11:45:58 +0200 (CEST)","from perceval.ideasonboard.com (perceval.ideasonboard.com\n\t[213.167.242.64])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTPS id 3A10A604A3\n\tfor <libcamera-devel@lists.libcamera.org>;\n\tWed,  4 May 2022 11:45:57 +0200 (CEST)","from pendragon.ideasonboard.com\n\t(cpc89244-aztw30-2-0-cust3082.18-1.cable.virginm.net [86.31.172.11])\n\tby perceval.ideasonboard.com (Postfix) with ESMTPSA id C79DF488;\n\tWed,  4 May 2022 11:45:56 +0200 (CEST)"],"DKIM-Signature":["v=1; a=rsa-sha256; c=relaxed/simple; d=libcamera.org;\n\ts=mail; t=1651657558;\n\tbh=09dhKrdXkEm89/PlaO0xy7FAl/YmXBuFnMj4+3K6FFE=;\n\th=In-Reply-To:References:To:Date:Subject:List-Id:List-Unsubscribe:\n\tList-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:\n\tFrom;\n\tb=fIl3GWoXQ4zePr5yQ7HwOIpdswGc2mXbq5VCCka72R1cV3NMPTX3d+1lXdRHXN9Pr\n\tdMaEgkBkYp2q033vM+rd+IAeN+P9RvpHOF/ixvd3Kw7nFjpiZLHO+QVUtqYMw2EVnr\n\tJACyruieoRZCuLBvyTjiz/llvl35QWNxtOCY3XneSRoJfg7vK2DwK2TCQVt8YpCYz5\n\t4WjM959dpeQ5A/FCPuvJK3a1O0V6lwIn09G7KFTptnNvAPcblOO55cIs6LYNwiGxEX\n\tj0BwSZZedcu9HG1SsXh/Xc4fNY7B2eJDLmf/Wv8fp+q8qbjDBZA+VwHBRZSnuC/Eav\n\tI61IE1Vojl/UA==","v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com;\n\ts=mail; t=1651657556;\n\tbh=09dhKrdXkEm89/PlaO0xy7FAl/YmXBuFnMj4+3K6FFE=;\n\th=In-Reply-To:References:Subject:From:Cc:To:Date:From;\n\tb=LzL6tfyJzoS2aYp7u0m639WhzIJPB+L+SgojdHjOUstP2TbFg+Uz5ssuB7DTIjCpS\n\tg9EbKmxrFz6Gl6vrHHlD1hgYYiidG0TVxiBxVYn+yg83O9Cjl5AXiTb4cRSvG4W1pt\n\tWmuw65OhEqif4hwkHQV2uMujkHdIU2QpUxcZY8Z4="],"Authentication-Results":"lancelot.ideasonboard.com; dkim=pass (1024-bit key; \n\tunprotected) header.d=ideasonboard.com\n\theader.i=@ideasonboard.com\n\theader.b=\"LzL6tfyJ\"; dkim-atps=neutral","Content-Type":"text/plain; charset=\"utf-8\"","MIME-Version":"1.0","Content-Transfer-Encoding":"quoted-printable","In-Reply-To":"<20220503163038.1174462-3-foss+libcamera@0leil.net>","References":"<20220503163038.1174462-1-foss+libcamera@0leil.net>\n\t<20220503163038.1174462-3-foss+libcamera@0leil.net>","To":"Quentin Schulz <foss+libcamera@0leil.net>,\n\tQuentin Schulz via libcamera-devel <libcamera-devel@lists.libcamera.org>","Date":"Wed, 04 May 2022 10:45:54 +0100","Message-ID":"<165165755432.4076486.16783220744826624607@Monstersaurus>","User-Agent":"alot/0.10","Subject":"Re: [libcamera-devel] [PATCH 3/3] Documentation: use https instead\n\tof http","X-BeenThere":"libcamera-devel@lists.libcamera.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"<libcamera-devel.lists.libcamera.org>","List-Unsubscribe":"<https://lists.libcamera.org/options/libcamera-devel>,\n\t<mailto:libcamera-devel-request@lists.libcamera.org?subject=unsubscribe>","List-Archive":"<https://lists.libcamera.org/pipermail/libcamera-devel/>","List-Post":"<mailto:libcamera-devel@lists.libcamera.org>","List-Help":"<mailto:libcamera-devel-request@lists.libcamera.org?subject=help>","List-Subscribe":"<https://lists.libcamera.org/listinfo/libcamera-devel>,\n\t<mailto:libcamera-devel-request@lists.libcamera.org?subject=subscribe>","From":"Kieran Bingham via libcamera-devel\n\t<libcamera-devel@lists.libcamera.org>","Reply-To":"Kieran Bingham <kieran.bingham@ideasonboard.com>","Cc":"libcamera-devel@lists.libcamera.org","Errors-To":"libcamera-devel-bounces@lists.libcamera.org","Sender":"\"libcamera-devel\" <libcamera-devel-bounces@lists.libcamera.org>"}}]