Home
last modified time | relevance | path

Searched refs:resolver (Results 1 – 20 of 20) sorted by relevance

/Zephyr-latest/doc/connectivity/networking/api/
Ddns_resolve.rst13 The DNS resolver implements a basic DNS resolver according
17 If a CNAME is received, the DNS resolver will create another DNS query.
21 The multicast DNS (mDNS) client resolver support can be enabled by setting
26 The link-local multicast name resolution (LLMNR) client resolver support can be
32 :zephyr_file:`subsys/net/lib/dns/Kconfig`. The DNS resolver API can be found at
Dlwm2m.rst410 When DNS names are used, the DNS resolver must be enabled.
/Zephyr-latest/samples/modules/tflite-micro/hello_world/src/
Dmain_functions.cpp57 static tflite::MicroMutableOpResolver <1> resolver; in setup() local
58 resolver.AddFullyConnected(); in setup()
62 model, resolver, tensor_arena, kTensorArenaSize); in setup()
/Zephyr-latest/subsys/net/lib/dns/
DKconfig5 bool "DNS resolver"
42 Number of additional DNS queries that the DNS resolver may
52 resolution the DNS resolver can handle.
94 resolver connects to server by selecting the output network interface
133 module-str = Log level for DNS resolver
134 module-help = Enables DNS resolver code to output debug messages.
138 bool "DNS resolver cache"
140 This option enables the dns resolver cache. DNS queries
295 # resolver support is enabled to simplify things. Strictly speaking the
296 # dispatcher is really needed for supporting resolver and responder at the same
[all …]
/Zephyr-latest/samples/modules/tflite-micro/tflm_ethosu/src/
Dinference_process.cpp121 tflite::MicroMutableOpResolver <1> resolver; in runJob() local
122 resolver.AddEthosU(); in runJob()
124 tflite::MicroInterpreter interpreter(model, resolver, tensorArena, tensorArenaSize); in runJob()
/Zephyr-latest/samples/net/tftp_client/
DKconfig19 When DNS resolver is enabled, DNS domain names could be used as well.
DREADME.rst66 To connect to server using hostname, enable DNS resolver by changing these two
/Zephyr-latest/samples/bluetooth/eddystone/
DREADME.rst15 a trusted resolver.
/Zephyr-latest/samples/net/lwm2m_client/
DKconfig40 When DNS resolver is enabled, DNS domain names could be used as well.
/Zephyr-latest/doc/_extensions/zephyr/domain/
D__init__.py867 resolver = Resolver("name")
876 node = resolver.get(tree, category_path)
916 resolver = Resolver("name")
920 node = resolver.get(category_tree, "/" + path.dirname(code_sample["docname"]))
/Zephyr-latest/drivers/wifi/esp_at/
DKconfig.esp_at162 list to system DNS resolver.
/Zephyr-latest/subsys/net/lib/dhcpv4/
DKconfig90 bool "Use DNS server from DHCPv4 option and save it in the DNS resolver default context"
/Zephyr-latest/doc/releases/
Drelease-notes-1.8.rst95 * DNS resolver sample application added
Dmigration-guide-3.7.rst890 * The DNS resolver and mDNS/LLMNR responders are converted to use socket service API.
Drelease-notes-2.0.rst391 * mDNS and LLMNR resolver fixes.
1255 * :github:`15472` - DNS resolver sample sends only one A query
Drelease-notes-2.6.rst683 * Added support for reconfiguring DNS resolver when DNS servers are changed.
1695 * :github:`33101` - DNS resolver misbehaves if receiving response too late
Drelease-notes-3.7.rst1365 * Reworked LLMNR and mDNS responders, and DNS resolver to use sockets and socket services API.
Drelease-notes-1.14.rst1033 network configuration library, DNS resolver, DHCPv4, DTS, flash_area,
Drelease-notes-3.3.rst2810 - :github:`54674` - modem: hl7800: DNS resolver does not start for IPv6 only
/Zephyr-latest/subsys/net/ip/
DKconfig227 bool "DNS resolver"