Searched refs:permission (Results 1 – 25 of 39) sorted by relevance
12
/Zephyr-Core-3.7.0/.github/ISSUE_TEMPLATE/ |
D | 006_nomination.md | 17 with Read permission do not have the permission to add reviewers to a pull 21 Triage permission level, which allows the user to add reviewers to a pull
|
/Zephyr-Core-3.7.0/subsys/bluetooth/services/ |
D | Kconfig.hrs | 16 used when no permission is set for the report.
|
/Zephyr-Core-3.7.0/doc/kernel/usermode/ |
D | kernelobjects.rst | 88 may drop their own permission on an object with 96 the access control aspects of the permission system are not enforced. 123 numerical ID assigned to them at build time, used to index the permission 124 bitfield for an object to see if that thread has permission on it. The size 163 * A thread that has permission on an object, or is running in supervisor mode, 164 may grant permission on that object to another thread via the 169 permission, or the object whose access is being granted, do not need to be 194 permission on the allocated object to the calling thread.
|
D | overview.rst | 66 with the permission granularity on a per object or per driver instance 151 - User threads by default have no permission to access any kernel object or 153 another thread that is either in supervisor mode or has permission on both
|
/Zephyr-Core-3.7.0/doc/_doxygen/ |
D | doxygen-awesome-sidebar-only-darkmode-toggle.css | 17 The above copyright notice and this permission notice shall be included in all
|
D | doxygen-awesome-sidebar-only.css | 17 The above copyright notice and this permission notice shall be included in all
|
/Zephyr-Core-3.7.0/include/zephyr/drivers/mspi/ |
D | devicetree.h | 84 .permission = DT_PROP_BY_IDX(mspi_dev, xip_config, 3), \
|
/Zephyr-Core-3.7.0/doc/connectivity/bluetooth/api/ |
D | gatt.rst | 46 callback, a ``write`` callback and a set of permission. Both read and write 47 callbacks can be set to NULL if the attribute permission don't allow their
|
/Zephyr-Core-3.7.0/samples/subsys/smf/hsm_psicc2/ |
D | README.rst | 34 topologies up to four levels of state nesting and is used with permission of the author.
|
/Zephyr-Core-3.7.0/doc/develop/ |
D | beyond-GSG.rst | 238 Flashing a board requires permission to directly access the board 241 define udev rules to grant the needed access permission. 246 permission by non-root users to certain USB-connected devices. 270 permission to access the board hardware for flashing. Check your
|
/Zephyr-Core-3.7.0/tests/bluetooth/tester/src/btp/ |
D | btp_gatt.h | 306 uint8_t permission; member
|
/Zephyr-Core-3.7.0/include/zephyr/drivers/ |
D | mspi.h | 313 enum mspi_xip_permit permission; member
|
/Zephyr-Core-3.7.0/doc/project/ |
D | project_roles.rst | 54 …izations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-or… 61 Contributors who show dedication and skill are granted the Triage permission 65 permission level by creating a GitHub issue, using the :github:`nomination 68 Contributors granted the Triage permission level are permitted to add reviewers
|
/Zephyr-Core-3.7.0/include/zephyr/arch/x86/intel64/ |
D | linker.ld | 14 /* Used to align areas with separate memory permission characteristics
|
/Zephyr-Core-3.7.0/include/zephyr/arch/x86/ia32/ |
D | linker.ld | 30 * into the RAMABLE_REGION region so it can be accessed with read and write permission. 61 /* Used to align areas with separate memory permission characteristics
|
/Zephyr-Core-3.7.0/ |
D | CODE_OF_CONDUCT.md | 35 without their explicit permission
|
D | LICENSE | 138 6. Trademarks. This License does not grant permission to use the trade
|
/Zephyr-Core-3.7.0/boards/96boards/nitrogen/doc/ |
D | index.rst | 254 To fix the permission issue, simply add the following udev rule for the
|
/Zephyr-Core-3.7.0/doc/kernel/services/synchronization/ |
D | mutexes.rst | 176 user memory so that any access bypasses the kernel object permission
|
/Zephyr-Core-3.7.0/doc/introduction/ |
D | index.rst | 104 kernel object and device driver permission tracking, and thread isolation
|
/Zephyr-Core-3.7.0/boards/andestech/adp_xc7k_ae350/doc/ |
D | index.rst | 248 # Enable execute file permission of ICEman
|
/Zephyr-Core-3.7.0/doc/security/ |
D | reporting.rst | 13 advisory GitHub_. The original submitter will be granted permission to
|
/Zephyr-Core-3.7.0/doc/kernel/services/other/ |
D | fatal.rst | 196 as the thread will simply not have permission to write to adjacent memory
|
/Zephyr-Core-3.7.0/arch/ |
D | Kconfig | 892 1) All program text will be have read-only, execute memory permission 893 2) All read-only data will have read-only permission, and execution 895 3) All other RAM addresses will have read-write permission, and
|
/Zephyr-Core-3.7.0/boards/qemu/x86/ |
D | qemu_x86_tiny.ld | 113 /* Used to align areas with separate memory permission characteristics
|
12