[{"id":13765,"web_url":"https://patchwork.libcamera.org/comment/13765/","msgid":"<20201117172451.73fhuyjj5br47qaw@uno.localdomain>","date":"2020-11-17T17:24:51","subject":"Re: [libcamera-devel] [PATCH v3] Documentation: Add descriptions\n\tfor env. variables","submitter":{"id":3,"url":"https://patchwork.libcamera.org/api/people/3/","name":"Jacopo Mondi","email":"jacopo@jmondi.org"},"content":"Hi Sebastian,\n\nOn Wed, Nov 04, 2020 at 07:48:48PM +0100, Sebastian Fricke wrote:\n> Describe the environment variables used in libcamera, excluded\n> variables are `LIBCAMERA_IPA_FORCE_C_API` and `LIBCAMERA_IPA_PROXY_PATH`,\n> the former because it is likely to be removed and the later because\n> it has no current use-case.\n>\n> Add a brief explanation for the IPA configuration and IPA modules.\n> List all the available Log levels and categories and add a short guide\n> for how to use them for debugging.\n\ns/for/on/\n\n>\n> Signed-off-by: Sebastian Fricke \n>\n> ---\n>\n> Changes since V2:\n> * replace bullet point list with definition list\n> * Remove the category list as it is too difficult to maintain, instead\n> explain how the categories are set with the LOG_DECLARE_CATEGORY &\n> LOG_DEFINE_CATEGORY macros\n> * Remove the short summary for the IPA module, as it can be misleading\n> and probably not accurate enough\n> * Improve the notes for debugging part by linking to a full explaination\n> while extending the description in the documentation as well\n> * Add an example for the Log level setting\n> * Remove the documentation from guides and add it to the documentation\n> base path\n>\n> Changes since V1:\n> * abandon the usage of tables as they are too clunky and difficult to\n> maintain\n> * Fix a wrong example that does not work on most distributions and setups\n> * Improve structure of log categories\n> ---\n> Documentation/environment_variables.rst | 129 ++++++++++++++++++++++++\n> Documentation/index.rst | 1 +\n> Documentation/meson.build | 1 +\n> 3 files changed, 131 insertions(+)\n> create mode 100644 Documentation/environment_variables.rst\n>\n> diff --git a/Documentation/environment_variables.rst b/Documentation/environment_variables.rst\n> new file mode 100644\n> index 0000000..a03412b\n> --- /dev/null\n> +++ b/Documentation/environment_variables.rst\n> @@ -0,0 +1,129 @@\n> +Environment variables\n> +=====================\n> +\n> +List of variables\n> +-----------------\n> +\n> +LIBCAMERA_LOG_FILE\n> + The custom destination for log output.\n> +\n> + Example value: ``/home/{user}/camera_log.log``\n> +\n> +LIBCAMERA_LOG_LEVELS\n> + Configure the verbosity of log messages for different categories (`more <#log-levels>`__)\n> +\n> + Example value: ``*:DEBUG``\n> +\n> +LIBCAMERA_IPA_CONFIG_PATH\n> + Define custom search locations for IPA configurations (`more <#ipa-configuration>`__)\n> +\n> + Example value: ``/usr/path/one:/tmp/path/two``\n> +\n> +LIBCAMERA_IPA_MODULE_PATH\n> + Define custom search locations for IPA modules (`more <#ipa-module>`__)\n> +\n> + Example value: ``/usr/path/one:/tmp/path/two``\n> +\n> +Further details\n> +---------------\n> +\n> +Notes about debugging\n> +~~~~~~~~~~~~~~~~~~~~~\n> +\n> +The environment variables `LIBCAMERA_LOG_FILE` and `LIBCAMERA_LOG_LEVELS`\n> +are used to modify the destination and verbosity of messages provided by\n> +the libcamera API.\n\ns/the libcamera API/libcamera/\n> +\n> +The `LIBCAMERA_LOG_LEVELS` variable expects a comma-separated list of\n> +'category:level' pairs. The `level <#log-levels>`__ part can either be given\n> +as the index or the name in uppercase letters.\n\nnot sure about 'index' maybe\n\n\"can either be specified by name or by the associated numerical\nindex\" ?\n\n> +While `category <#log-categories>`__ should either be the exact name of the\n> +category, the '*' wildcard symbol or no value, which targets every category.\n\nWe do pattern matching on categories.\n\nI woudl say:\n\nThe `LIBCAMERA_LOG_LEVELS` variable accepts a comma-separated list of\n'category:level' pairs.\n\nThe `level <#log-levels>`__ part is mandatory and can either be\nspecified by name or by numerical index associated to each level.\n\nThe optional `category <#log-categories>`__ part is a regular\nexpression which is matched against the categories defined by each\nfile in the source base using the logging infrastructure.\n\n> +While `category <#log-categories>`__ should either be the exact name of the\n> +category, the '*' wildcard symbol or no value, which targets every category.\n\n> +\n\nDouble empty line\n\n> +\n> +For more information refer to the `API-documentation `__\n> +\n> +Examples:\n> +\n> +Enable full debug output to a separate file, for every `category <#log-categories>`__\n> +within a local environment:\n\nI would drop 'within.. '\n\n> +\n> +.. code:: bash\n> +\n> + :~$ LIBCAMERA_LOG_FILE='/tmp/example_log.log' \\\n> + LIBCAMERA_LOG_LEVELS=0 \\\n> + cam --list\n> +\n> +Enable full debug output for the categories Camera & V4L2 within a\n> +global environment:\n\nAh I get what you mean with local/global.\nThat's pretty standard handling of environment variables, do we need\nit specified here ? It doesn't hurt though, up to you\n\n> +\n> +.. code:: bash\n> +\n> + :~$ export LIBCAMERA_LOG_LEVELS='Camera:DEBUG,V4L2:DEBUG'\n> + :~$ cam --list\n> +\n> +Log levels\n> +~~~~~~~~~~~\n> +\n> +This is the list of available log levels, notice that all levels below\n> +the chosen one are printed, while those above are discarded.\n> +\n> +- DEBUG (0)\n> +- INFO (1)\n> +- WARN (2)\n ^ double space. Intentional ?\n> +- ERROR (3)\n> +- FATAL (4)\n> +\n> +Example:\n> +If you choose WARN (2), you will be able to see WARN (2), ERROR (3) & FATAL (4)\n> +but not DEBUG (0) & INFO (1).\n> +\n> +Log categories\n> +~~~~~~~~~~~~~~~\n> +\n> +Every category represent a specific area of the libcamera codebase,\n> +the names can be located within the source code, for example:\n> +`src/libcamera/camera_manager.cpp `__\n> +\n> +.. code:: bash\n> +\n> + LOG_DEFINE_CATEGORY(Camera)\n> +\n> +There are 2 available macros used to assign a category name to a part of the\n> +libcamera API:\n\ns/API/code base/\n\n> +\n> +LOG_DEFINE_CATEGORY\n> + This macro is required, in order to use the `LOGC` macro for a\n> +\tparticular category. It can only be used once for each category.\n> +\tIf you want to create log messages within multiple compilation\n> +\tunits for the same category utilize the `LOG_DECLARE_CATEGORY` macro,\n> +\tin every file except the definition file.\n> +LOG_DECLARE_CATEGORY\n> + Used for sharing an already defined category in between multiple\n> +\tseparately compiled files.\n\ncompilation units maybe ?\n\n> +\n> +Both macros have to be used within the namespace part of the C++ source code.\n\nwithin the libcamera namespace.\n\nThis part is nice, but it's not much about environment variables but\non how to use the logging infrastructure.\n\n> +\n\ndouble empty line. Intentional /\n\n> +\n> +IPA configuration\n> +~~~~~~~~~~~~~~~~~~\n> +\n> +The format and contents of the configuration file are specific to the\n> +IPA (Image Processing Algorithm). It usually contains data that optimize\n\ns/data that optimize... /tuning parameters for the IPA algorithms/\n> +the behavior of the algorithms stored in JSON format. The\n> +`LIBCAMERA_IPA_CONFIG_PATH` variable can be used to specify custom\n> +storage locations to search for those configuration files.\n> +\n> +`Examples `__\n> +\n> +IPA module\n> +~~~~~~~~~~~\n> +\n> +In order to locate the correct IPA module for your hardware, libcamera gathers\n> +existing IPA modules from multiple locations. The default locations for this\n> +operation are the installed system path (for example on Debian:\n> +``/usr/local/x86_64-pc-linux-gnu/libcamera``) and the build directory.\n> +With the `LIBCAMERA_IPA_MODULE_PATH`, you can specify a non-default\n> +location to search for IPA modules.\n> +\n> +`Examples for existing IPA modules `__\n\nThanks, very useful ;)\n\nWith the above fixed\nReviewed-by: Jacopo Mondi \n\nThanks\n j\n\n> diff --git a/Documentation/index.rst b/Documentation/index.rst\n> index ff697d4..c49db18 100644\n> --- a/Documentation/index.rst\n> +++ b/Documentation/index.rst\n> @@ -17,3 +17,4 @@\n> Application Writer's Guide \n> Pipeline Handler Writer's Guide \n> Tracing guide \n> + Environment variables \n> diff --git a/Documentation/meson.build b/Documentation/meson.build\n> index 26a12fc..8086abf 100644\n> --- a/Documentation/meson.build\n> +++ b/Documentation/meson.build\n> @@ -53,6 +53,7 @@ if sphinx.found()\n> 'contributing.rst',\n> 'docs.rst',\n> 'index.rst',\n> + 'environment_variables.rst',\n> 'guides/introduction.rst',\n> 'guides/application-developer.rst',\n> 'guides/pipeline-handler.rst',\n> --\n> 2.20.1\n>\n> _______________________________________________\n> libcamera-devel mailing list\n> libcamera-devel@lists.libcamera.org\n> https://lists.libcamera.org/listinfo/libcamera-devel","headers":{"Return-Path":"","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 33920BE081\n\tfor ;\n\tTue, 17 Nov 2020 17:24:50 +0000 (UTC)","from lancelot.ideasonboard.com (localhost [IPv6:::1])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTP id A5B5B6331E;\n\tTue, 17 Nov 2020 18:24:49 +0100 (CET)","from relay11.mail.gandi.net (relay11.mail.gandi.net\n\t[217.70.178.231])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTPS id 04C856033B\n\tfor ;\n\tTue, 17 Nov 2020 18:24:49 +0100 (CET)","from uno.localdomain (93-34-118-233.ip49.fastwebnet.it\n\t[93.34.118.233]) (Authenticated sender: jacopo@jmondi.org)\n\tby relay11.mail.gandi.net (Postfix) with ESMTPSA id 880D9100004;\n\tTue, 17 Nov 2020 17:24:48 +0000 (UTC)"],"Date":"Tue, 17 Nov 2020 18:24:51 +0100","From":"Jacopo Mondi ","To":"Sebastian Fricke ","Message-ID":"<20201117172451.73fhuyjj5br47qaw@uno.localdomain>","References":"<20201104184848.14235-1-sebastian.fricke.linux@gmail.com>","MIME-Version":"1.0","Content-Disposition":"inline","In-Reply-To":"<20201104184848.14235-1-sebastian.fricke.linux@gmail.com>","Subject":"Re: [libcamera-devel] [PATCH v3] Documentation: Add descriptions\n\tfor env. variables","X-BeenThere":"libcamera-devel@lists.libcamera.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"","List-Unsubscribe":",\n\t","List-Archive":"","List-Post":"","List-Help":"","List-Subscribe":",\n\t","Cc":"libcamera-devel@lists.libcamera.org","Content-Type":"text/plain; charset=\"us-ascii\"","Content-Transfer-Encoding":"7bit","Errors-To":"libcamera-devel-bounces@lists.libcamera.org","Sender":"\"libcamera-devel\" "}},{"id":13818,"web_url":"https://patchwork.libcamera.org/comment/13818/","msgid":"<20201120153744.2bqiivm6ykukxype@basti.Speedport_W_724V_Typ_A_05011603_06_001>","date":"2020-11-20T15:37:44","subject":"Re: [libcamera-devel] [PATCH v3] Documentation: Add descriptions\n\tfor env. variables","submitter":{"id":73,"url":"https://patchwork.libcamera.org/api/people/73/","name":"Sebastian Fricke","email":"sebastian.fricke.linux@gmail.com"},"content":"On 17.11.2020 18:24, Jacopo Mondi wrote:\n>Hi Sebastian,\n\nHi Jacopo,\n\nthanks for the review!\n\n>\n>On Wed, Nov 04, 2020 at 07:48:48PM +0100, Sebastian Fricke wrote:\n>> Describe the environment variables used in libcamera, excluded\n>> variables are `LIBCAMERA_IPA_FORCE_C_API` and `LIBCAMERA_IPA_PROXY_PATH`,\n>> the former because it is likely to be removed and the later because\n>> it has no current use-case.\n>>\n>> Add a brief explanation for the IPA configuration and IPA modules.\n>> List all the available Log levels and categories and add a short guide\n>> for how to use them for debugging.\n>\n>s/for/on/\n>\n>>\n>> Signed-off-by: Sebastian Fricke \n>>\n>> ---\n>>\n>> Changes since V2:\n>> * replace bullet point list with definition list\n>> * Remove the category list as it is too difficult to maintain, instead\n>> explain how the categories are set with the LOG_DECLARE_CATEGORY &\n>> LOG_DEFINE_CATEGORY macros\n>> * Remove the short summary for the IPA module, as it can be misleading\n>> and probably not accurate enough\n>> * Improve the notes for debugging part by linking to a full explaination\n>> while extending the description in the documentation as well\n>> * Add an example for the Log level setting\n>> * Remove the documentation from guides and add it to the documentation\n>> base path\n>>\n>> Changes since V1:\n>> * abandon the usage of tables as they are too clunky and difficult to\n>> maintain\n>> * Fix a wrong example that does not work on most distributions and setups\n>> * Improve structure of log categories\n>> ---\n>> Documentation/environment_variables.rst | 129 ++++++++++++++++++++++++\n>> Documentation/index.rst | 1 +\n>> Documentation/meson.build | 1 +\n>> 3 files changed, 131 insertions(+)\n>> create mode 100644 Documentation/environment_variables.rst\n>>\n>> diff --git a/Documentation/environment_variables.rst b/Documentation/environment_variables.rst\n>> new file mode 100644\n>> index 0000000..a03412b\n>> --- /dev/null\n>> +++ b/Documentation/environment_variables.rst\n>> @@ -0,0 +1,129 @@\n>> +Environment variables\n>> +=====================\n>> +\n>> +List of variables\n>> +-----------------\n>> +\n>> +LIBCAMERA_LOG_FILE\n>> + The custom destination for log output.\n>> +\n>> + Example value: ``/home/{user}/camera_log.log``\n>> +\n>> +LIBCAMERA_LOG_LEVELS\n>> + Configure the verbosity of log messages for different categories (`more <#log-levels>`__)\n>> +\n>> + Example value: ``*:DEBUG``\n>> +\n>> +LIBCAMERA_IPA_CONFIG_PATH\n>> + Define custom search locations for IPA configurations (`more <#ipa-configuration>`__)\n>> +\n>> + Example value: ``/usr/path/one:/tmp/path/two``\n>> +\n>> +LIBCAMERA_IPA_MODULE_PATH\n>> + Define custom search locations for IPA modules (`more <#ipa-module>`__)\n>> +\n>> + Example value: ``/usr/path/one:/tmp/path/two``\n>> +\n>> +Further details\n>> +---------------\n>> +\n>> +Notes about debugging\n>> +~~~~~~~~~~~~~~~~~~~~~\n>> +\n>> +The environment variables `LIBCAMERA_LOG_FILE` and `LIBCAMERA_LOG_LEVELS`\n>> +are used to modify the destination and verbosity of messages provided by\n>> +the libcamera API.\n>\n>s/the libcamera API/libcamera/\n>> +\n>> +The `LIBCAMERA_LOG_LEVELS` variable expects a comma-separated list of\n>> +'category:level' pairs. The `level <#log-levels>`__ part can either be given\n>> +as the index or the name in uppercase letters.\n>\n>not sure about 'index' maybe\n>\n>\"can either be specified by name or by the associated numerical\n>index\" ?\n>\n>> +While `category <#log-categories>`__ should either be the exact name of the\n>> +category, the '*' wildcard symbol or no value, which targets every category.\n>\n>We do pattern matching on categories.\n>\n>I woudl say:\n>\n>The `LIBCAMERA_LOG_LEVELS` variable accepts a comma-separated list of\n>'category:level' pairs.\n>\n>The `level <#log-levels>`__ part is mandatory and can either be\n>specified by name or by numerical index associated to each level.\n>\n>The optional `category <#log-categories>`__ part is a regular\n>expression which is matched against the categories defined by each\n>file in the source base using the logging infrastructure.\n>\n>> +While `category <#log-categories>`__ should either be the exact name of the\n>> +category, the '*' wildcard symbol or no value, which targets every category.\n>\n>> +\n>\n>Double empty line\n>\n>> +\n>> +For more information refer to the `API-documentation `__\n>> +\n>> +Examples:\n>> +\n>> +Enable full debug output to a separate file, for every `category <#log-categories>`__\n>> +within a local environment:\n>\n>I would drop 'within.. '\n>\n>> +\n>> +.. code:: bash\n>> +\n>> + :~$ LIBCAMERA_LOG_FILE='/tmp/example_log.log' \\\n>> + LIBCAMERA_LOG_LEVELS=0 \\\n>> + cam --list\n>> +\n>> +Enable full debug output for the categories Camera & V4L2 within a\n>> +global environment:\n>\n>Ah I get what you mean with local/global.\n>That's pretty standard handling of environment variables, do we need\n>it specified here ? It doesn't hurt though, up to you\n\nI am not too sure if we have to keep it, I just noticed while testing\naround that it is sometimes quite handy to know that there are different\nways of doing something. And I know that there complete tutorials about\nthis stuff and we can not explain every thing about the unix environment\nwithin this documnetation. My thought process for this was the\nfollowing:\nIf I am able to explain two variants of doing something within about the\nsame amount of words, then why not?\n\n>\n>> +\n>> +.. code:: bash\n>> +\n>> + :~$ export LIBCAMERA_LOG_LEVELS='Camera:DEBUG,V4L2:DEBUG'\n>> + :~$ cam --list\n>> +\n>> +Log levels\n>> +~~~~~~~~~~~\n>> +\n>> +This is the list of available log levels, notice that all levels below\n>> +the chosen one are printed, while those above are discarded.\n>> +\n>> +- DEBUG (0)\n>> +- INFO (1)\n>> +- WARN (2)\n> ^ double space. Intentional ?\n>> +- ERROR (3)\n>> +- FATAL (4)\n>> +\n>> +Example:\n>> +If you choose WARN (2), you will be able to see WARN (2), ERROR (3) & FATAL (4)\n>> +but not DEBUG (0) & INFO (1).\n>> +\n>> +Log categories\n>> +~~~~~~~~~~~~~~~\n>> +\n>> +Every category represent a specific area of the libcamera codebase,\n>> +the names can be located within the source code, for example:\n>> +`src/libcamera/camera_manager.cpp `__\n>> +\n>> +.. code:: bash\n>> +\n>> + LOG_DEFINE_CATEGORY(Camera)\n>> +\n>> +There are 2 available macros used to assign a category name to a part of the\n>> +libcamera API:\n>\n>s/API/code base/\n>\n>> +\n>> +LOG_DEFINE_CATEGORY\n>> + This macro is required, in order to use the `LOGC` macro for a\n>> +\tparticular category. It can only be used once for each category.\n>> +\tIf you want to create log messages within multiple compilation\n>> +\tunits for the same category utilize the `LOG_DECLARE_CATEGORY` macro,\n>> +\tin every file except the definition file.\n>> +LOG_DECLARE_CATEGORY\n>> + Used for sharing an already defined category in between multiple\n>> +\tseparately compiled files.\n>\n>compilation units maybe ?\n>\n>> +\n>> +Both macros have to be used within the namespace part of the C++ source code.\n>\n>within the libcamera namespace.\n>\n>This part is nice, but it's not much about environment variables but\n>on how to use the logging infrastructure.\n\nI've got the main idea from Laurent,\nquote:\n\"Would it make sense to instead link to the Doxygen-generated documentation\n(and possibly expanding it a little bit to mention LOG_DEFINE_CATEGORY and LOG_DECLARE_CATEGORY)\"\n\nAnd I think that it fits quite well in here as logging is very tightly\nrelated to the environment variables, because you cannot activate the\nlogging without the variables. Also I think we do not have enough\ncontent for a logging documentation on it's own.\nI believe it helps using the env. variable, when you understand where\nthose names come from and how to expand the logging if one likes to.\n\n>\n>> +\n>\n>double empty line. Intentional /\n>\n>> +\n>> +IPA configuration\n>> +~~~~~~~~~~~~~~~~~~\n>> +\n>> +The format and contents of the configuration file are specific to the\n>> +IPA (Image Processing Algorithm). It usually contains data that optimize\n>\n>s/data that optimize... /tuning parameters for the IPA algorithms/\n>> +the behavior of the algorithms stored in JSON format. The\n>> +`LIBCAMERA_IPA_CONFIG_PATH` variable can be used to specify custom\n>> +storage locations to search for those configuration files.\n>> +\n>> +`Examples `__\n>> +\n>> +IPA module\n>> +~~~~~~~~~~~\n>> +\n>> +In order to locate the correct IPA module for your hardware, libcamera gathers\n>> +existing IPA modules from multiple locations. The default locations for this\n>> +operation are the installed system path (for example on Debian:\n>> +``/usr/local/x86_64-pc-linux-gnu/libcamera``) and the build directory.\n>> +With the `LIBCAMERA_IPA_MODULE_PATH`, you can specify a non-default\n>> +location to search for IPA modules.\n>> +\n>> +`Examples for existing IPA modules `__\n>\n>Thanks, very useful ;)\n\nThank you very much :)\n\n>\n>With the above fixed\n>Reviewed-by: Jacopo Mondi \n>\n>Thanks\n> j\n>\n>> diff --git a/Documentation/index.rst b/Documentation/index.rst\n>> index ff697d4..c49db18 100644\n>> --- a/Documentation/index.rst\n>> +++ b/Documentation/index.rst\n>> @@ -17,3 +17,4 @@\n>> Application Writer's Guide \n>> Pipeline Handler Writer's Guide \n>> Tracing guide \n>> + Environment variables \n>> diff --git a/Documentation/meson.build b/Documentation/meson.build\n>> index 26a12fc..8086abf 100644\n>> --- a/Documentation/meson.build\n>> +++ b/Documentation/meson.build\n>> @@ -53,6 +53,7 @@ if sphinx.found()\n>> 'contributing.rst',\n>> 'docs.rst',\n>> 'index.rst',\n>> + 'environment_variables.rst',\n>> 'guides/introduction.rst',\n>> 'guides/application-developer.rst',\n>> 'guides/pipeline-handler.rst',\n>> --\n>> 2.20.1\n>>\n>> _______________________________________________\n>> libcamera-devel mailing list\n>> libcamera-devel@lists.libcamera.org\n>> https://lists.libcamera.org/listinfo/libcamera-devel","headers":{"Return-Path":"","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 BD692BE08A\n\tfor ;\n\tFri, 20 Nov 2020 15:37:49 +0000 (UTC)","from lancelot.ideasonboard.com (localhost [IPv6:::1])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTP id 549EE625AC;\n\tFri, 20 Nov 2020 16:37:49 +0100 (CET)","from mail-ej1-x643.google.com (mail-ej1-x643.google.com\n\t[IPv6:2a00:1450:4864:20::643])\n\tby lancelot.ideasonboard.com (Postfix) with ESMTPS id D0EE66220D\n\tfor ;\n\tFri, 20 Nov 2020 16:37:47 +0100 (CET)","by mail-ej1-x643.google.com with SMTP id f23so13486612ejk.2\n\tfor ;\n\tFri, 20 Nov 2020 07:37:47 -0800 (PST)","from localhost\n\t(p200300d1ff28820039a2a82822a82fc5.dip0.t-ipconnect.de.\n\t[2003:d1:ff28:8200:39a2:a828:22a8:2fc5])\n\tby smtp.gmail.com with ESMTPSA id\n\tb6sm1253552edu.21.2020.11.20.07.37.46\n\t(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);\n\tFri, 20 Nov 2020 07:37:46 -0800 (PST)"],"Authentication-Results":"lancelot.ideasonboard.com;\n\tdkim=fail reason=\"signature verification failed\" (2048-bit key;\n\tunprotected) header.d=gmail.com header.i=@gmail.com\n\theader.b=\"Bdm5P4j9\"; dkim-atps=neutral","DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;\n\th=date:from:to:cc:subject:message-id:references:mime-version\n\t:content-disposition:in-reply-to:user-agent;\n\tbh=KA5888x/BFht7YVEnN/f8Jwd+nElIcuSNpAOLLenCmc=;\n\tb=Bdm5P4j9WZsLQatTLiBRNqsSK4dCpvonC9KibyOVkgRIxhjqSsn3MNj0bDFgUtA/nW\n\tSvlXMkt8G5pSpqYK7S4+gibomjsesSDUfWtas7xEq/unW+BYg1n04EsJgK7/VsQWUpGh\n\t29SS66M6C0lVQGwQ+ZcWJ0A+YM0BKDoUFkx8/LYvJtZGr9j5lD2uz2RSgdvC7mbduGj3\n\tFO8UGArn8CZw1OEJteeKEhVaRNVMoAxp1w3FhMkIo+X3OLooG0AVqGVD9uvY02RZ1eQZ\n\tubu7E1InoQu/bDBYujToJr+4V81aL9nex13PikWkAXoc2S7bi2VJEwQ5dagSGWKRd9Ud\n\tIxfw==","X-Google-DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=1e100.net; s=20161025;\n\th=x-gm-message-state:date:from:to:cc:subject:message-id:references\n\t:mime-version:content-disposition:in-reply-to:user-agent;\n\tbh=KA5888x/BFht7YVEnN/f8Jwd+nElIcuSNpAOLLenCmc=;\n\tb=OeBLuS3G3ns0uO8dz0/k+fsifcGvhr7cWocu8b1QS9Go0dUmCUEU8k27vLVot4QM0Z\n\tl6huHAcqqvzeyM/7oyoeNiLGs19CtvcOVNMDX0mzlc86oZDI3uu697IctP4YphZ6TNbO\n\tbtn/cZoM4Za6CpBlRsCsOYxm1a7TItCahfZrctjBapRD/9uzHrlEBsBKUeI6y55pPE6q\n\tU382ZcfnIWcorqw3GmF2Rg9ZFqXP3wdApBCT+a0/bJen0OjpO2JofkjU00Xf57LxPoQY\n\tQfnKzJZ303Ey6ZR3TAWS88pDQv4JJyQ6In+3qV317N/Okuq45l12HvtLHijdoWiy1B1n\n\t1Ghw==","X-Gm-Message-State":"AOAM532fOLSKy0WBsBiIbXAr4hATOAJxA8hUfGYlmFweGXg4xEhhsefW\n\tpTW8LIQ+4YT5LA4gDoGkAOY=","X-Google-Smtp-Source":"ABdhPJyhRTxIpuHvpCCBu+s8S/jp9oKUKFmEJRpKdGios+g3NfMxthbkEh0N362hn4VdPDhEXAT35A==","X-Received":"by 2002:a17:906:f881:: with SMTP id\n\tlg1mr6953173ejb.133.1605886667253; \n\tFri, 20 Nov 2020 07:37:47 -0800 (PST)","Date":"Fri, 20 Nov 2020 16:37:44 +0100","From":"Sebastian Fricke ","To":"Jacopo Mondi ","Message-ID":"<20201120153744.2bqiivm6ykukxype@basti.Speedport_W_724V_Typ_A_05011603_06_001>","References":"<20201104184848.14235-1-sebastian.fricke.linux@gmail.com>\n\t<20201117172451.73fhuyjj5br47qaw@uno.localdomain>","MIME-Version":"1.0","Content-Disposition":"inline","In-Reply-To":"<20201117172451.73fhuyjj5br47qaw@uno.localdomain>","User-Agent":"NeoMutt/20180716","Subject":"Re: [libcamera-devel] [PATCH v3] Documentation: Add descriptions\n\tfor env. variables","X-BeenThere":"libcamera-devel@lists.libcamera.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"","List-Unsubscribe":",\n\t","List-Archive":"","List-Post":"","List-Help":"","List-Subscribe":",\n\t","Cc":"libcamera-devel@lists.libcamera.org","Content-Transfer-Encoding":"7bit","Content-Type":"text/plain; charset=\"us-ascii\"; Format=\"flowed\"","Errors-To":"libcamera-devel-bounces@lists.libcamera.org","Sender":"\"libcamera-devel\" "}}]