From 017143720b85c252158cfec9400c867986054d3a Mon Sep 17 00:00:00 2001 From: "Restyled.io" Date: Mon, 24 Jun 2024 11:51:05 +0000 Subject: [PATCH] Restyled by prettier-markdown --- examples/all-clusters-app/esp32/README.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/examples/all-clusters-app/esp32/README.md b/examples/all-clusters-app/esp32/README.md index 0e95fc52392e10..0a3145dbc24da2 100644 --- a/examples/all-clusters-app/esp32/README.md +++ b/examples/all-clusters-app/esp32/README.md @@ -48,17 +48,19 @@ interface. For ESP32-C6 DevKits, if `CHIP_DEVICE_CONFIG_ENABLE_WIFI` and `CHIP_DEVICE_CONFIG_ENABLE_THREAD` are both enabled, please set -`CONFIG_THREAD_NETWORK_ENDPOINT_ID` to 0 and set `CONFIG_WIFI_NETWORK_ENDPOINT_ID` -to 65534, which presents that the NetworkCommissioning cluster in Endpoint 0 will -be used for Thread network driver and the same cluster on Endpoint 65534 will be -used for Wi-Fi network driver. Or vice versa. +`CONFIG_THREAD_NETWORK_ENDPOINT_ID` to 0 and set +`CONFIG_WIFI_NETWORK_ENDPOINT_ID` to 65534, which presents that the +NetworkCommissioning cluster in Endpoint 0 will be used for Thread network +driver and the same cluster on Endpoint 65534 will be used for Wi-Fi network +driver. Or vice versa. For ESP32-Ethernet-Kits, if `CHIP_DEVICE_CONFIG_ENABLE_WIFI` and `CHIP_DEVICE_CONFIG_ENABLE_ETHERNET` are both enabled, please set -`CONFIG_ETHERNET_NETWORK_ENDPOINT_ID` to 0 and set `CONFIG_WIFI_NETWORK_ENDPOINT_ID` -to 65534, which presents that the NetworkCommissioning cluster in Endpoint 0 will be -used for Ethernet network driver and the same cluster on Endpoint 65534 will be used -for Wi-Fi network driver. Or vice versa. +`CONFIG_ETHERNET_NETWORK_ENDPOINT_ID` to 0 and set +`CONFIG_WIFI_NETWORK_ENDPOINT_ID` to 65534, which presents that the +NetworkCommissioning cluster in Endpoint 0 will be used for Ethernet network +driver and the same cluster on Endpoint 65534 will be used for Wi-Fi network +driver. Or vice versa. ---