| /Zephyr-latest/boards/microchip/ |
| D | index.rst | 1 .. _boards-microchip-technology-inc:
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server/src/ |
| D | response_big.html.bin | 27 …oject where silicon vendors, OEMs, ODMs, ISVs, and OSVs can contribute technology to reduce the co…
35 …technology known as Virtuoso. The RTOS has been used in several commercial applications including …
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server_mt/src/ |
| D | response_big.html.bin | 27 …oject where silicon vendors, OEMs, ODMs, ISVs, and OSVs can contribute technology to reduce the co…
35 …technology known as Virtuoso. The RTOS has been used in several commercial applications including …
|
| /Zephyr-latest/subsys/bluetooth/audio/shell/ |
| D | tbs.c | 78 .technology = BT_TBS_TECHNOLOGY_3G, in cmd_tbs_init()
101 .technology = (i % BT_TBS_TECHNOLOGY_WCDMA) + 1, in cmd_tbs_init()
515 unsigned long technology; in cmd_tbs_set_bearer_technology() local
542 technology = shell_strtoul(argv[argc - 1], 0, &result); in cmd_tbs_set_bearer_technology()
549 if (technology > UINT8_MAX) { in cmd_tbs_set_bearer_technology()
550 shell_error(sh, "Invalid technology: %lu", technology); in cmd_tbs_set_bearer_technology()
556 (uint8_t)technology); in cmd_tbs_set_bearer_technology()
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 11 Connectivity implementations are technology-specific modules that allow specific Zephyr ifaces to s…
75 /* Cause your underlying technology to associate */
78 /* Cause your underlying technology to disassociate */
81 /* Perform any required initialization for your underlying technology */
193 …disable or enable these features, regardless of the inherent behavior of the underlying technology.
194 In other words, no matter how the underlying technology behaves, your implementation must make it a…
244 * If the technology also handles IP assignment, ensure those IP addresses are :ref:`assigned to the…
274 …should not prevent applications from interacting directly with associated technology-specific APIs.
276 In other words, it should be possible for an application to directly use your underlying technology…
284 …For instance, if an application directly instructs an underlying technology to disassociate, it wo…
[all …]
|
| /Zephyr-latest/tests/bsim/bluetooth/audio/src/ |
| D | tbs_client_test.c | 39 CREATE_FLAG(technology);
165 SET_FLAG(technology); in tbs_client_technology_cb()
315 .technology = tbs_client_technology_cb,
414 UNSET_FLAG(technology); in test_technology()
424 WAIT_FOR_FLAG(technology); in test_technology()
|
| D | tbs_test.c | 339 .technology = BT_TBS_TECHNOLOGY_3G, in init()
387 .technology = (i % BT_TBS_TECHNOLOGY_WCDMA) + 1, in init()
|
| /Zephyr-latest/drivers/tee/optee/ |
| D | Kconfig | 10 of the hardware isolation and rely to ARM TrustZone technology.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | thread.rst | 12 Thread is a low-power mesh networking technology, designed specifically for home
14 technology over IEEE 802.15.4 protocol. IP connectivity lets you easily connect
|
| D | ethernet.rst | 20 Ethernet is a networking technology commonly used in local area networks (LAN).
|
| D | net_mgmt.rst | 177 technology as well. For instance, all IP layer management request code
179 of an L2 technology, let's say Ethernet, these would be found in
208 code, event code can be also found on specific L2 technology mgmt headers,
210 802.15.4 L2 is the technology one wants to listen to events.
|
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | Kconfig.intel_vtd | 14 technology. It's being used, currently, only for MSI/MSI-X
|
| /Zephyr-latest/subsys/bluetooth/audio/ |
| D | tbs_client.c | 400 uint8_t technology) in technology_changed() argument
405 if (listener->technology != NULL) { in technology_changed()
406 listener->technology(conn, err, inst_index, technology); in technology_changed()
415 uint8_t technology; in technology_notify_handler() local
419 if (length == sizeof(technology)) { in technology_notify_handler()
420 (void)memcpy(&technology, data, length); in technology_notify_handler()
421 LOG_DBG("%s (0x%02x)", bt_tbs_technology_str(technology), technology); in technology_notify_handler()
423 technology_changed(conn, 0, tbs_index(conn, tbs_inst), technology); in technology_notify_handler()
1011 uint8_t technology = 0; in read_technology_cb() local
1019 if (length == sizeof(technology)) { in read_technology_cb()
[all …]
|
| D | tbs.c | 47 uint8_t technology; member
571 LOG_DBG("Index %u: Technology 0x%02x", inst_index(inst), inst->technology); in read_technology()
573 return bt_gatt_attr_read(conn, attr, buf, len, offset, &inst->technology, in read_technology()
574 sizeof(inst->technology)); in read_technology()
1530 inst->technology = param->technology; in tbs_inst_init_and_register()
1603 if (!IN_RANGE(param->technology, BT_TBS_TECHNOLOGY_3G, BT_TBS_TECHNOLOGY_WCDMA)) { in valid_register_param()
1604 LOG_DBG("Invalid technology: %u", param->technology); in valid_register_param()
2061 if (inst->technology == new_technology) { in bt_tbs_set_bearer_technology()
2065 inst->technology = new_technology; in bt_tbs_set_bearer_technology()
2067 bt_gatt_notify_uuid(NULL, BT_UUID_TBS_TECHNOLOGY, inst->attrs, &inst->technology, in bt_tbs_set_bearer_technology()
[all …]
|
| /Zephyr-latest/arch/arm/core/ |
| D | Kconfig | 78 Thumb-2 technology is the instruction set underlying the ARM Cortex
83 Thumb-2 technology builds on the success of Thumb, the innovative
88 The technology is backwards compatible with existing ARM and Thumb
93 For performance optimized code Thumb-2 technology uses 31 percent
97 technology is featured in the processor, and in all ARMv7
112 the introduction of Thumb-2 technology.
|
| /Zephyr-latest/include/zephyr/drivers/ |
| D | cellular.h | 46 enum cellular_access_technology technology; member
|
| /Zephyr-latest/include/zephyr/bluetooth/audio/ |
| D | tbs.h | 504 uint8_t technology; member
730 bt_tbs_client_read_value_cb technology; member
|
| /Zephyr-latest/samples/net/zperf/ |
| D | README.rst | 56 Depending on the network technology chosen, extra steps may be required
|
| /Zephyr-latest/boards/intel/adl/doc/ |
| D | index.rst | 9 technology process.
|
| /Zephyr-latest/boards/intel/rpl/doc/ |
| D | index.rst | 9 on a 10-nanometer technology process. Raptor Lake is based on a Hybrid
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | ccp.rst | 59 read_technology :Read the bearer technology [<{instance_index,
197 set_bearer_technology :Set the bearer technology [<{instance_index,
198 gtbs}>] <technology>
|
| /Zephyr-latest/cmake/ |
| D | target_toolchain_flags.cmake | 40 # Configure the toolchain flags based on what toolchain technology is used
|
| /Zephyr-latest/boards/beagle/beaglev_fire/doc/ |
| D | index.rst | 9 RISC-V architecture and FPGA technology. It has the same P8 & P9 cape header pins as BeagleBone
13 hobbyists, and researchers to explore and experiment with RISC-V technology.
|
| /Zephyr-latest/boards/shields/x_nucleo_53l0a1/doc/ |
| D | index.rst | 10 detection sensor, based on ST’s FlightSense™, Time-of-Flight technology. It is
|
| /Zephyr-latest/boards/sipeed/longan_nano/doc/ |
| D | index.rst | 7 an GigaDevice GD32VF103 SoC that based on N200 RISC-V IP core by Nuclei system technology.
|
