Home
last modified time | relevance | path

Searched refs:vendor (Results 151 – 175 of 183) sorted by relevance

12345678

/Zephyr-latest/samples/tfm_integration/psa_crypto/
DREADME.rst11 of the RTOS vendor requirements for a `PSA Certified Level 1`_ product, such
/Zephyr-latest/doc/develop/
Dbeyond-GSG.rst69 recommended by the SoC vendor or a specific board (check your specific
Dmodules.rst30 - Silicon vendor Hardware Abstraction Layers (HALs)
35 Additionally, in some cases modules (particularly vendor HALs) can contain
/Zephyr-latest/subsys/bluetooth/controller/
DKconfig.ll_sw_split771 This option enables a vendor specific sink for the controller assertion
773 vendor debug HAL interface as \"BT_ASSERT_VND(cond, param1, param2)\", and
908 Enables vendor specific per-connection meta data as part of the
/Zephyr-latest/modules/hostap/src/
Dsupp_api.c699 user->methods[0].vendor = 0; in hostapd_process_eap_user_phase1()
767 user->methods[0].vendor = 0; in hostapd_process_eap_user()
/Zephyr-latest/doc/releases/
Drelease-notes-2.7.rst782 <dt-important-props>` in the ``vendor,device`` format uses an unknown
783 vendor prefix. This warning does not apply to the root node.
785 Known vendor prefixes are defined in
786 :file:`dts/bindings/vendor-prefixes.txt` files, which may appear in any
794 * Various bindings had incorrect vendor prefixes in their :ref:`compatible
1365 * :github:`37797` - Merge vendor-prefixes.txt from all modules with build.settings.dts_root in zeph…
Drelease-notes-3.3.rst173 voltage level. All drivers now use vendor-specific flags as needed.
1225 - Generic or vendor-independent:
1430 - A stand-in for a real vendor which can be used in examples and tests (vnd):
1453 - Generic or vendor-independent:
1475 - Generic or vendor-independent:
1493 - new property: ``vendor-id``
1589 - new property: ``vendor-id``
1726 - new property: ``vendor-id``
1776 - new property: ``vendor-id``
1964 - A stand-in for a real vendor which can be used in examples and tests (vnd):
Drelease-notes-2.3.rst74 vendor-specific assumptions of byte order and should express the identifier
831 * :github:`25433` - Add vendor specific class custom usb device sample
902 * :github:`25067` - Insufficient ticker nodes for vendor implementations
909 * :github:`25012` - checkpatch.pl doesn't match the vendor string properly
Dmigration-guide-3.7.rst699 * The ``BT_HCI_VS_EVT`` Kconfig option was removed, since vendor event support is implicit if
703 Enable the :kconfig:option:`CONFIG_BT_HCI_VS` Kconfig option instead, and use vendor specific
Drelease-notes-4.0.rst25 runtime configuration through vendor specific APIs. Initially the :dtcompatible:`nordic,nrf-comp`,
396 * ``--vendor-prefixes``
413 such as name, architecture, vendor, or SoC.
Drelease-notes-3.5.rst354 * Changed vendor prefix for ARC QEMU platforms from "qemu" to "snps"
993 * Generic or vendor-independent:
1963 * A stand-in for a real vendor which can be used in examples and tests (vnd):
Dmigration-guide-4.1.rst545 for any vendor to enable builds without blobs.
Drelease-notes-3.4.rst275 operations on flash devices, defined by Zephyr Flash API or by vendor specific
870 extra operations on flash devices, defined by Zephyr Flash API or by vendor
Drelease-notes-2.2.rst42 * :github:`25067` - Insufficient ticker nodes for vendor implementations
637 * Added dynamic TX power control, including a set of vendor-specific commands
Drelease-notes-3.2.rst321 * Added support for setting vendor-specific non-HCI data paths for audio
657 * Kconfig is split into smaller, vendor oriented files.
2635 …:`32665` - Bluetooth: controller: inclusion of vendor data type and function overrides provided by…
Drelease-notes-3.7.rst1105 * Moved most drivers to vendor subdirectories.
1330 * Added support for encapsulated vendor specific options. By enabling
/Zephyr-latest/scripts/
Dcheckpatch.pl3153 my $vendor = $1;
3154 `grep -Eq "^$vendor\\b" $vp_file`;
3157 … "DT compatible string vendor \"$vendor\" appears un-documented -- check $vp_file\n" . $herecurr);
/Zephyr-latest/doc/project/
Dproject_roles.rst382 to implementation of an API supporting vendor specific hardware and not the
/Zephyr-latest/doc/develop/test/
Dtwister.rst471 vendor is defined as part of the board definition. Boards associated with
473 vendor will be excluded.
477 The vendor is defined as part of the board. Boards associated with this
/Zephyr-latest/subsys/bluetooth/host/
DKconfig983 integer, see Vol 4, Part E section 7.7.65.21. This option enables a vendor specific Host
993 integer, see Vol 4, Part E sections 7.7.65.22. This option enables a vendor specific Host
/Zephyr-latest/doc/develop/flash_debug/
Dprobes.rst345 vendor-specific device (debug port).
/Zephyr-latest/boards/openisa/rv32m1_vega/doc/
Dindex.rst315 toolchain and an OpenOCD build. There are vendor-specific versions of
/Zephyr-latest/subsys/bluetooth/mesh/
DKconfig775 bool "Force vendor model to use the corresponding CID field message"
778 This option forces vendor model to use messages for the
/Zephyr-latest/cmake/modules/
Dextensions.cmake3713 # build_info(vendor-specific foo VALUE bar)
3714 # Will place the vendor specific key 'foo' with value 'bar' in the vendor specific section
3717 # <tag>...: One of the pre-defined valid CMake keys supported by build info or vendor-specific.
3768 if(ARGV0 STREQUAL "vendor-specific")
/Zephyr-latest/doc/contribute/
Dguidelines.rst956 whenever possible so that the device can be used with any SoC from any vendor

12345678