Searched refs:able (Results 226 – 250 of 289) sorted by relevance
12345678910>>...12
| /Zephyr-latest/samples/net/sockets/dumb_http_server_mt/src/ |
| D | response_100k.html.bin | 31 … Zephyr OS is modular and supports multiple architectures, developers are able to easily tailor an…
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig | 617 The Resolve List on a Controller is not able to accommodate multiple
659 With this option enabled, the application will be able to call the
722 With this option enabled, the application will be able to perform LESC
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 176 untrusted or exploited code will then be able to access the object. Use
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-le-host.rst | 94 non-connectable, i.e. other device will not be able to connect to it.
|
| D | bluetooth-tools.rst | 180 is very useful to be able to see the full log of exchanges between the two,
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | http_server.rst | 284 the application should be able to keep track of the received data progress.
|
| D | net_pkt.rst | 302 previously described API. It is able to handle both contiguous and
|
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 8 maintaining and extending Zephyr's APIs need to be able to introduce
|
| /Zephyr-latest/boards/st/b_u585i_iot02a/doc/ |
| D | index.rst | 233 options and get back the platform back to a "normal" state and be able to run
|
| /Zephyr-latest/doc/build/dts/ |
| D | phandles.rst | 248 Without the ``#baz-cells`` property, the devicetree tooling would not be able
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | sar_cfg.rst | 25 The transport layer is able to transport up to 32 segments with its SAR mechanism, with a maximum
|
| D | access.rst | 144 :c:func:`bt_mesh_model_data_store`. To be able to read out the data the
|
| /Zephyr-latest/doc/security/ |
| D | vulnerabilities.rst | 167 with physical access to the device is able to cause a memory
196 execution within a user thread is able to elevate privileges to that
223 able to elevate privileges to that of the kernel.
405 be parsed by Zephyr is able to cause a denial of service.
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.8.rst | 283 * ``ZEP-1966`` - Doesn't seem to be able to both send and receive locally via local address
|
| D | release-notes-1.10.rst | 50 to have those pointers validated; userspace must never be able to crash the
289 * :github:`3297` - ROM-able
|
| D | release-notes-2.1.rst | 682 * :github:`19685` - Samples: BluetoothMesh: not able to connect with device over GATT to provision …
721 * :github:`19413` - Not able to scan and connect to other ble devices with HCI commands
871 * :github:`16097` - STM32 Ethernet driver should be able to detect the carrier state
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | Kconfig | 556 message payload that the node needs to be able to receive.
578 message payload that the node needs to be able to send.
1589 Enable this option to be able to act as a Low Power Node.
1717 Enable this option to be able to act as a Friend Node.
|
| /Zephyr-latest/subsys/debug/ |
| D | Kconfig | 300 CFLAGS and not Kconfig. Added solely to be able to work
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_8.rst | 177 Weirdly, the current Zephyr implementation is half-stateless as is able to hold
|
| /Zephyr-latest/doc/services/ipc/ipc_service/backends/ |
| D | ipc_service_icbmsg.rst | 385 The newer implementations should be able to work with older ones in backward compatible mode.
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm_cortex_m.rst | 591 Baseline Cortex-M platforms without VTOR register might not be able to relocate their
597 it is able to relay exceptions and interrupts based on a vector table
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | bap.rst | 303 able to configure stream and properly manage capabilities in use.
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
| D | gap.rst | 178 After that, you can start the advertiser and then the target device will be able to reconnect.
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | index.rst | 138 #. Add the Homebrew Python folder to the path, in order to be able to
|
| /Zephyr-latest/samples/subsys/mgmt/updatehub/ |
| D | README.rst | 379 able to reached the updatehub server for some reason. The most common
|
12345678910>>...12
