Searched refs:vendor (Results 101 – 125 of 183) sorted by relevance
12345678
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob_srv.rst | 46 Client and the BLOB Transfer Server through some higher level procedure, like a vendor specific
|
| D | dfu.rst | 117 available. The format of the firmware ID is vendor specific, but generally, it should include
125 vendor specific, and should contain all information the Target node needs to verify the image, as
168 | | | vendor-specific behaviors using |
|
| /Zephyr-latest/scripts/ |
| D | list_hardware.py | 303 vendor=''
|
| /Zephyr-latest/scripts/west_commands/completion/ |
| D | west-completion.fish | 309 set -l boards (west boards --format="{name}|{qualifiers}|{vendor}" 2> /dev/null)
319 set -l vendor $split_b[3]
321 if test $vendor != "None"
323 printf "%s\t%s\n" $name/$qualifier $vendor >> $cache_file
|
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | Kconfig.df | 319 integer, see Vol 4, Part E section 7.7.65.21. This option enables a vendor specific
329 integer, see Vol 4, Part E section 7.7.65.22. This option enables a vendor specific
|
| /Zephyr-latest/boards/others/esp32c3_supermini/doc/ |
| D | index.rst | 8 There may be multiple variations depending on the specific vendor. For more information a reasonbly…
|
| /Zephyr-latest/doc/connectivity/bluetooth/autopts/ |
| D | autopts-win10.rst | 22 Update drivers, following the instructions from your hardware vendor.
|
| /Zephyr-latest/boards/espressif/esp32s2_devkitc/doc/ |
| D | index.rst | 201 Further documentation can be obtained from the SoC vendor in `JTAG debugging for ESP32-S2`_.
|
| /Zephyr-latest/boards/espressif/esp32s2_saola/doc/ |
| D | index.rst | 201 Further documentation can be obtained from the SoC vendor in `JTAG debugging for ESP32-S2`_.
|
| /Zephyr-latest/drivers/sensor/ |
| D | sensor_shell.c | 945 sensor->dev->name, sensor->vendor ? sensor->vendor : null_str, in cmd_get_sensor_info()
|
| /Zephyr-latest/boards/dptechnics/walter/doc/ |
| D | index.rst | 203 Further documentation can be obtained from the SoC vendor in `JTAG debugging for ESP32-S3`_.
|
| /Zephyr-latest/boards/seeed/xiao_esp32s3/doc/ |
| D | index.rst | 216 Further documentation can be obtained from the SoC vendor in `JTAG debugging for ESP32-S3`_.
|
| /Zephyr-latest/boards/st/sensortile_box/doc/ |
| D | index.rst | 120 certain standard or vendor class, e.g. a CDC, a mass storage or a composite device with both
|
| /Zephyr-latest/modules/hal_nordic/nrfx/ |
| D | CMakeLists.txt | 250 build_info(vendor-specific nordic svdfile VALUE ${SOC_SVD_FILE})
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 28 significantly in nature and conditions. It is up to the vendor to specify the
60 - A reference to vendor-provided documentation
|
| /Zephyr-latest/subsys/bluetooth/audio/ |
| D | codec.c | 1155 const uint8_t *vendor, size_t vendor_len) in codec_meta_set_vendor() argument
1162 CHECKIF(vendor == NULL) { in codec_meta_set_vendor()
1167 return codec_meta_set_val(meta, meta_len, meta_size, BT_AUDIO_METADATA_TYPE_VENDOR, vendor, in codec_meta_set_vendor()
|
| /Zephyr-latest/arch/arm/ |
| D | Kconfig | 184 MCU implements the nRF (vendor-specific) Security Attribution Unit.
|
| /Zephyr-latest/boards/enjoydigital/litex_vexriscv/doc/ |
| D | index.rst | 11 vendor-specific and open-source tools, including the
|
| /Zephyr-latest/boards/espressif/esp32_devkitc_wroom/doc/ |
| D | index.rst | 218 Further documentation can be obtained from the SoC vendor in `JTAG debugging for ESP32`_.
|
| /Zephyr-latest/boards/espressif/esp32_devkitc_wrover/doc/ |
| D | index.rst | 218 Further documentation can be obtained from the SoC vendor in `JTAG debugging for ESP32`_.
|
| /Zephyr-latest/boards/adafruit/qt_py_esp32s3/doc/ |
| D | index.rst | 201 Further documentation can be obtained from the SoC vendor
|
| /Zephyr-latest/subsys/net/lib/config/ |
| D | Kconfig | 224 application and vendor should choose a suitable setting based
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 170 ├─── <vendor/private-repositories>/
1139 │ └── vendor
1152 Use the vendor name as the folder name (which must match the vendor prefix in
1153 :zephyr_file:`dts/bindings/vendor-prefixes.txt` if submitting upstream to Zephyr, or be
1154 ``others`` if it is not a vendor board) under ``boards`` for ``my_custom_board``.
|
| /Zephyr-latest/doc/security/ |
| D | security-overview.rst | 132 APIs for vendor specific cryptographic IPs in both hardware and software
634 potentially IP of the vendor or manufacturer.
641 which the vendor could use to certify their Zephyr-enabled
671 product vendor.
|
| /Zephyr-latest/boards/vcc-gnd/yd_esp32/doc/ |
| D | index.rst | 232 Further documentation can be obtained from the SoC vendor in `JTAG debugging for ESP32`_.
|
12345678
