Home
last modified time | relevance | path

Searched refs:client (Results 201 – 225 of 326) sorted by relevance

12345678910>>...14

/Zephyr-latest/drivers/serial/
DKconfig.native_posix43 bool "Support waiting for pseudo terminal client readiness"
49 client has connected to the slave side of the pseudoterminal.
/Zephyr-latest/samples/net/lwm2m_client/src/
Dlwm2m-client.c201 static void rd_client_event(struct lwm2m_ctx *client, in rd_client_event() argument
260 lwm2m_rd_client_stop(client, rd_client_event, true); in rd_client_event()
/Zephyr-latest/doc/connectivity/networking/
Dnetworking_with_multiple_instances.rst127 :zephyr:code-sample:`sockets-echo-client` sample applications. You can use other applications
165 west build -d build/client -b qemu_x86 -t run \
180 west build -d build/client -b native_sim -t run \
/Zephyr-latest/samples/net/mqtt_sn_publisher/
DREADME.rst21 client that sends MQTT-SN PUBLISH messages to an MQTT-SN gateway.
107 [00:00:00.000,000] <inf> mqtt_sn_publisher_sample: Connecting client
110 [00:00:00.510,000] <inf> net_mqtt_sn: MQTT_SN client connected
/Zephyr-latest/doc/releases/
Drelease-notes-1.5.rst116 - Added mbedTLS sample client.
160 * ``ZEP-416`` - MQTT client capability: QoS1, QoS2
167 * ``ZEP-500`` - Domain Name System client library
224 * ``ZEP-522`` - TCP/client-mode: disconnect
252 * ``ZEP-669`` - MQTT fail to pingreq if broker deliver topic to client but client doesn't read it.
255 * ``ZEP-681`` - MQTT client sample throws too many warnings when build.
Drelease-notes-1.7.rst95 * Added DNS client library.
100 * Created IRC client sample application.
101 * Created HTTP server and client sample applications.
168 * ``ZEP-613`` - TCP/UDP client and server mode functionality
239 * ``ZEP-975`` - DNS client port to new IP stack
240 * ``ZEP-1012`` - NATS client port to new IP stack
254 * ``ZEP-1233`` - mbedDTLS DTLS client stability does not work on top of the tree for the net branch
366 * ``ZEP-1570`` - net/tcp: TCP in server mode is unable to close client connections
388 * ``ZEP-1617`` - mbedTLS server/client failing to run on qemu
451 * ``ZEP-1858`` - Zephyr NATS client fails to respond to server MSG
[all …]
/Zephyr-latest/samples/net/prometheus/src/
Dmain.c45 static int dyn_handler(struct http_client_ctx *client, enum http_data_status status, in dyn_handler() argument
/Zephyr-latest/samples/net/sockets/http_get/
DREADME.rst5 Implement an HTTP(S) client using plain BSD sockets.
11 HTTP GET client using a BSD Sockets compatible API. The purpose of this
/Zephyr-latest/samples/net/sockets/can/
DREADME.rst10 The socket CAN sample is a server/client application that sends and receives
/Zephyr-latest/doc/services/device_mgmt/
Dsmp_transport.rst6 The documents specifies information needed for implementing server and client
15 SMP client:
45 MCUmgr client/server over UART transport that does not have framing at all,
Dmcumgr_callbacks.rst135 by a handler will be returned to the MCUmgr client.
160 /* Return an access denied error code to the client and abort calling
168 /* Return a no entry error code to the client, call additional handlers
298 will disallow it and return that code to the client
316 return code will disallow it and return that code to the client
324 return code will disallow it and return that code to the client
/Zephyr-latest/cmake/emu/
Dqemu.cmake170 client
175 if((${target} STREQUAL client) OR (${target} STREQUAL server))
213 set(PIPE_CLIENT_IN /tmp/ip-stack-client.in)
214 set(PIPE_CLIENT_OUT /tmp/ip-stack-client.out)
271 /tmp/ip-stack-client
/Zephyr-latest/samples/net/cloud/tagoio_http_post/
DREADME.rst10 This sample application implements an HTTP client that will do an HTTP post
48 tagoio-http-client sample application with minimal configuration:
/Zephyr-latest/subsys/shell/backends/
Dshell_mqtt.c44 static void mqtt_evt_handler(struct mqtt_client *const client, const struct mqtt_evt *evt);
529 static void mqtt_evt_handler(struct mqtt_client *const client, const struct mqtt_evt *evt) in mqtt_evt_handler() argument
581 (void)mqtt_publish_qos1_ack(client, &puback); in mqtt_evt_handler()
589 rc = mqtt_read_publish_payload_blocking(client, sh_mqtt->rx_rb_ptr, size); in mqtt_evt_handler()
/Zephyr-latest/subsys/bluetooth/audio/
DKconfig.micp65 enabled for MICP client.
/Zephyr-latest/tests/bsim/bluetooth/host/att/retry_on_sec_err/client/
Dmain.c20 LOG_MODULE_REGISTER(client, LOG_LEVEL_DBG);
/Zephyr-latest/tests/bsim/bluetooth/host/gatt/settings_clear/src/
Dclient.c28 LOG_MODULE_REGISTER(client, LOG_LEVEL_DBG);
/Zephyr-latest/samples/net/cloud/mqtt_azure/
DREADME.rst10 This sample application demonstrates how an MQTT client
106 [00:00:19.412,000] <dbg> mqtt_azure.mqtt_event_handler: MQTT client connected!
/Zephyr-latest/samples/drivers/ipm/ipm_ivshmem/
DREADME.rst16 ivshmem-client needs to be available as it is employed in this sample as an
26 #. You may also find ivshmem-client utility, it can be useful to check if everything works
/Zephyr-latest/subsys/bluetooth/host/
DKconfig.gatt90 a reconnection to a GATT client is established and
159 When enable this option blocks notification and indications to client
163 a client until it becomes change-aware."
178 bool "GATT client support"
/Zephyr-latest/scripts/west_commands/runners/
Dcore.py807 def run_server_and_client(self, server, client, **kwargs): argument
822 self.run_client(client, **kwargs)
827 def run_client(self, client, **kwargs): argument
831 self.check_call(client, **kwargs)
/Zephyr-latest/doc/services/sensing/
Dindex.rst14 space service layer. It is a framework focused on sensor fusion, client
164 For ``Sensor clients``, there is no open API for opening a reporter, because the client-report
167 The ``Sensing Subsystem`` will auto open and create ``handlers`` for client sensor
177 generated by Sensing Subsystem according devicetree definitions, handlers between client sensor
/Zephyr-latest/doc/services/storage/stream/
Dstream_flash.rst8 providing the read-back buffer to the client to use in validating the persisted
/Zephyr-latest/lib/utils/
DKconfig10 applications such as the NATS client.
/Zephyr-latest/tests/bluetooth/tester/
DREADME51 Use serial client, e.g. PUTTY to communicate over the serial port

12345678910>>...14