From 988666b05e7e83e4f5672a58897cd3a355afd9c6 Mon Sep 17 00:00:00 2001 From: Pierre Haessig Date: Thu, 11 Jul 2024 11:47:39 +0200 Subject: [PATCH] Minor documentation updates (#360) * fix typo in udev-rules.rst missing double backticks * remove Python 3.4 requirement notice for Zephyr and fix typo (extra "is") --- core/installation/udev-rules.rst | 2 +- frameworks/zephyr_extra.rst | 5 +---- 2 files changed, 2 insertions(+), 5 deletions(-) diff --git a/core/installation/udev-rules.rst b/core/installation/udev-rules.rst index ec19b44801..79024330e0 100644 --- a/core/installation/udev-rules.rst +++ b/core/installation/udev-rules.rst @@ -70,7 +70,7 @@ command). For example, the file permissions for the serial port ``/dev/ttyACM0`` # prints something like: # crw-rw---- 1 root dialout 166, 0 juil. 10 13:43 /dev/ttyACM0 -In that case, the read/write permission (`rw`) is granted to both the “root” user and members of the “dialout” group. Now, it is possible to grant read/write access to all users (``$ sudo chmod a+rw /dev/ttyACM0``), but this would only last as long as the card remains connected (only the udev rules file mentioned above can make such change permanent). +In that case, the read/write permission (``rw``) is granted to both the “root” user and members of the “dialout” group. Now, it is possible to grant read/write access to all users (``$ sudo chmod a+rw /dev/ttyACM0``), but this would only last as long as the card remains connected (only the udev rules file mentioned above can make such change permanent). The alternative permanent solution is to add its own “username” to the “dialout” group, or whichever group name was identified at the preceding step. Typical names are “dialout”, “plugdev” (Debian/Ubuntu, Fedora), or “uucp” (Arch Linux). Adding a user to a group is done by: diff --git a/frameworks/zephyr_extra.rst b/frameworks/zephyr_extra.rst index 560a10d37b..e0a9665597 100644 --- a/frameworks/zephyr_extra.rst +++ b/frameworks/zephyr_extra.rst @@ -24,10 +24,7 @@ Configuration Project Structure ~~~~~~~~~~~~~~~~~ -.. warning:: - Zephyr framework currently requires Python 3.4 or later. - -`Zephyr `_ is framework requires an unusual project structure because most of the framework +`Zephyr `_ framework requires an unusual project structure because most of the framework configuration is performed by the native for Zephyr build system called ``CMake``. .. note::