| /Zephyr-latest/doc/hardware/porting/ |
| D | soc_porting.rst | 34 Each SoC must have a unique name. Use the official name given by the SoC vendor
43 ``<VENDOR>`` is your vendor subdirectory.
49 The ``<VENDOR>`` subdirectory must match a vendor defined in the list in
50 :zephyr_file:`dts/bindings/vendor-prefixes.txt`. If the SoC vendor does not
217 soc/<vendor>/<your soc>
|
| D | board_porting.rst | 188 - asking your SoC vendor
216 When adding a new SoC family or series for a vendor that already has SoC
218 files to avoid duplication. If there is no support for your vendor yet, you can
236 ``<VENDOR>`` is your vendor subdirectory. (You don't have to put your
245 If the vendor is defined in the list in
246 :zephyr_file:`dts/bindings/vendor-prefixes.txt` then you must use
247 that vendor prefix as ``<VENDOR>``. ``others`` may be used as vendor prefix if
248 the vendor is not defined.
329 vendor: <board-vendor>
357 vendor: <board-vendor>
[all …]
|
| /Zephyr-latest/samples/drivers/ethernet/eth_ivshmem/boards/ |
| D | qemu_cortex_a53.overlay | 48 vendor-id = <0x110A>; /* Siemens */
|
| /Zephyr-latest/samples/bluetooth/hci_vs_scan_req/ |
| D | README.rst | 5 Use vendor-specific HCI commands to enable Scan Request events when using legacy advertising.
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig | 48 This option enables setting custom vendor
58 Custom vendor OUI, which makes 24 most-significant
|
| /Zephyr-latest/soc/ |
| D | Kconfig.v2 | 29 indicates the vendor of the SoC.
|
| /Zephyr-latest/subsys/usb/device/class/ |
| D | Kconfig.msc | 19 string "T10 assigned vendor ID for inquiry (must be 8 characters)"
|
| /Zephyr-latest/subsys/usb/device_next/class/ |
| D | usbd_msc_scsi.c | 385 void scsi_init(struct scsi_ctx *ctx, const char *disk, const char *vendor, in scsi_init() argument
390 ctx->vendor = vendor; in scsi_init()
481 strncpy(r.scsi_vendor, ctx->vendor, sizeof(r.scsi_vendor)); in fill_inquiry()
516 strncpy(&page_start[offset], ctx->vendor, T10_VENDOR_LENGTH); in fill_vpd_page()
|
| /Zephyr-latest/subsys/net/lib/tls_credentials/ |
| D | Kconfig | 53 device's secure file system; eg, via a vendor tool or
|
| /Zephyr-latest/doc/connectivity/usb/device/ |
| D | usb_device.rst | 98 Since the designation of the controller nodes varies from vendor to vendor,
405 * Optionally class, vendor and custom handlers
432 The vendor device requests are forwarded by the USB stack core driver to the
433 class driver through the registered vendor handler.
436 the vendor requests:
440 :start-after: usb.rst vendor handler start
441 :end-before: usb.rst vendor handler end
534 1-1: unknown vendor : unknown product (2fe3:0100)
554 unknown vendor : unknown product (2fe3:0100)
564 This USB Vendor ID must not be used when a vendor
|
| /Zephyr-latest/scripts/tests/twister_blackbox/ |
| D | test_filter.py | 227 def test_vendor(self, capfd, out_path, vendor, expected): argument
231 ['--vendor', vendor] + \
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.stats | 138 from vendor specific hardware registers in a form of
140 vendor documentation.
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | video.rst | 41 controls available which can be generic, related to a device class or vendor
|
| /Zephyr-latest/samples/bluetooth/hci_pwr_ctrl/ |
| D | README.rst | 5 Dynamically control the Tx power of a Bluetooth LE Controller using HCI vendor-specific commands.
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.cortex_m_systick | 58 On such SoCs, a vendor-specific timer that remains active in low-power
62 With this option, such vendor-specific timer can be selected and used by
|
| /Zephyr-latest/drivers/bluetooth/hci/ |
| D | Kconfig.infineon | 67 custom or vendor AIROC modules in AIROC_CUSTOM_FIRMWARE_HCD_BLOB.
196 Path to BT firmware HCD file for custom or vendor CYW43xx modules.
199 # Change size of command lengths. It for vendor commands related to
|
| D | Kconfig | 310 public identity through vendor-specific commands. They can then implement the
319 Enable the HCI vendor-specific Setup function.
322 of the vendor-specific commands sequence to initialize the BT Controller
326 configuration files. This option are enabled by the vendor-specific
|
| /Zephyr-latest/subsys/net/lib/shell/ |
| D | stats.c | 112 if (data->vendor) { in print_eth_stats()
119 PR("%s : %u\n", data->vendor[i].key, in print_eth_stats()
120 data->vendor[i].value); in print_eth_stats()
122 } while (data->vendor[i].key); in print_eth_stats()
|
| /Zephyr-latest/boards/ |
| D | index.rst | 23 both a vendor and an architecture, only boards that match both will be displayed. Within a
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfd_srv.rst | 26 nodes in the network in any order. The contents, format and size of the firmware images are vendor
|
| /Zephyr-latest/cmake/modules/ |
| D | dts.cmake | 70 # implementation files (like bindings, vendor prefixes, etc.) are
131 # The location of a file containing known vendor prefixes, relative to
134 set(VENDOR_PREFIXES dts/bindings/vendor-prefixes.txt)
178 # well as all the devicetree bindings and vendor prefixes associated
233 list(APPEND EXTRA_GEN_EDT_ARGS --vendor-prefixes ${vendor_prefixes})
|
| /Zephyr-latest/subsys/usb/device/class/dfu/ |
| D | Kconfig | 19 USB device product ID in DFU mode. MUST be configured by vendor.
|
| /Zephyr-latest/subsys/usb/device/class/netusb/ |
| D | Kconfig | 33 Remote NDIS (RNDIS) is commonly used Microsoft vendor protocol with
|
| /Zephyr-latest/scripts/ |
| D | list_boards.py | 99 vendor: str = None variable in Board
281 vendor=board.get('vendor'),
426 VENDOR='VENDOR;' + notfound(b.vendor),
|
| /Zephyr-latest/doc/_extensions/zephyr/domain/static/css/ |
| D | board-catalog.css | 177 .board-card .vendor {
252 #catalog.compact .board-card .vendor,
|
