Home
last modified time | relevance | path

Searched refs:revision (Results 1 – 25 of 84) sorted by relevance

1234

/Zephyr-Core-3.4.0/doc/hardware/porting/
Dboard_porting.rst380 :file:`.config` whenever an application is compiled for your board revision
526 To create a new board revision for the ``plank`` board, create these additional
532 ├── plank_<revision>.conf # optional
533 ├── plank_<revision>.overlay # optional
534 └── revision.cmake
536 When the user builds for board ``plank@<revision>``:
539 :file:`plank_<revision>.conf` will be merged into the board's default Kconfig
542 - The optional devicetree overlay :file:`plank_<revision>.overlay` will be added
545 - The :file:`revision.cmake` file controls how the Zephyr build system matches
546 the ``<board>@<revision>`` string specified by the user when building an
[all …]
Dshields.rst76 revision, you can override a shield description for a specific board by adding
77 board or board revision overriding files to a shield, as follows:
83 ├── <board>_<revision>.overlay
86 ├── <board>_<revision>.conf
122 In this case, a shield-particular revision name can be used:
130 revision:
/Zephyr-Core-3.4.0/include/zephyr/usb/class/
Dusbd_msc.h23 const char *revision; member
31 .revision = t10_revision, \
/Zephyr-Core-3.4.0/subsys/dfu/boot/
Dmcuboot.c50 uint16_t revision; member
86 v1_raw->version.revision = in boot_read_v1_header()
87 sys_le16_to_cpu(v1_raw->version.revision); in boot_read_v1_header()
142 sem_ver->revision = v1_raw.version.revision; in boot_read_bank_header()
/Zephyr-Core-3.4.0/cmake/modules/
Dboards.cmake22 # - BOARD: Board, without revision field.
23 # - BOARD_REVISION: Board revision
32 # - BOARD: Board name, including any optional revision field, for example: `foo` or `foo@1.0.0`
123 if(EXISTS ${BOARD_DIR}/revision.cmake)
124 # Board provides revision handling.
125 include(${BOARD_DIR}/revision.cmake)
127 message(WARNING "Board revision ${BOARD_REVISION} specified for ${BOARD}, \
128 but board has no revision so revision will be ignored.")
/Zephyr-Core-3.4.0/submanifests/
Dexample.yaml.sample12 # branch, change the 'revision' line accordingly.
18 revision: main
/Zephyr-Core-3.4.0/boards/arm/nrf9160dk_nrf52840/
Dnrf9160dk_nrf52840_0_14_0.overlay39 /* New signal added in this revision (0.14.0). */
44 /* No need to drive P0.12 together with P1.12 in this board revision. */
/Zephyr-Core-3.4.0/subsys/bluetooth/services/
DKconfig.dis118 string "Firmware revision"
121 Enable firmware revision characteristic in Device Information Service.
129 string "Hardware revision"
132 Enable hardware revision characteristic in Device Information Service.
140 string "Software revision"
143 Enable software revision characteristic in Device Information Service.
/Zephyr-Core-3.4.0/subsys/usb/device_next/class/
Dusbd_msc_scsi.h68 const char *revision; member
86 const char *product, const char *revision);
Dusbd_msc_scsi.c166 char revision[T10_REVISION_LENGTH]; member
386 const char *product, const char *revision) in scsi_init() argument
392 ctx->revision = revision; in scsi_init()
483 strncpy(r.revision, ctx->revision, sizeof(r.revision)); in fill_inquiry()
/Zephyr-Core-3.4.0/soc/arm/atmel_sam/same70/
DKconfig.defconfig.series33 # for the revision A and 74 for the revision B (not all Peripheral Identifiers
/Zephyr-Core-3.4.0/soc/arm/atmel_sam/samv71/
DKconfig.defconfig.series34 # for the revision A and 74 for the revision B (not all Peripheral Identifiers
/Zephyr-Core-3.4.0/scripts/
Dzephyr_module.py435 revision = stdout.rstrip()
443 return revision + '-dirty', True
444 return revision, False
469 revision, dirty = git_revision(project_path)
471 if project.sha(MANIFEST_REV_BRANCH) != revision:
472 revision += '-off'
475 'revision': revision}
485 revision, dirty = git_revision(module_path)
489 'revision': revision}
/Zephyr-Core-3.4.0/subsys/mgmt/hawkbit/
Dhawkbit_firmware.c25 header.h.v1.sem_ver.minor, header.h.v1.sem_ver.revision); in hawkbit_get_firmware_version()
/Zephyr-Core-3.4.0/boards/arm/legend/
Drevision.cmake6 …message(FATAL_ERROR "${BOARD_REVISION} is not a valid revision for Legend. Accepted revisions: ${L…
/Zephyr-Core-3.4.0/subsys/mgmt/updatehub/
Dupdatehub_firmware.c35 header.h.v1.sem_ver.revision); in updatehub_get_firmware_version()
/Zephyr-Core-3.4.0/subsys/bluetooth/mesh/
Ddfu_metadata.c24 metadata->fw_ver.revision = net_buf_simple_pull_le16(buf); in bt_mesh_dfu_metadata_decode()
60 net_buf_simple_add_le16(buf, metadata->fw_ver.revision); in bt_mesh_dfu_metadata_encode()
/Zephyr-Core-3.4.0/include/zephyr/bluetooth/mesh/
Ddfu_metadata.h35 uint16_t revision; member
/Zephyr-Core-3.4.0/include/zephyr/arch/x86/
Dacpi.h18 uint8_t revision; member
30 uint8_t revision; member
/Zephyr-Core-3.4.0/include/zephyr/dfu/
Dmcuboot.h95 uint16_t revision; member
/Zephyr-Core-3.4.0/doc/develop/west/
Dbuilt-in.rst40 the ``-m`` switch, the initial revision to check out using ``--mr``, and
109 #. Inspects the project's ``revision`` field in the manifest, and fetches
112 commit specified by the revision in the previous step
120 ``revision`` values which are Git SHAs or tags that are already available
128 If the project ``revision`` is a Git ref that is neither a tag nor a SHA (i.e.
133 these like SHAs. You can disambiguate by prefixing the ``revision`` value with
134 ``refs/heads/``, e.g. ``revision: refs/heads/deadbeef``.
137 detached ``HEAD`` at the manifest revision for each updated project,
270 West may fetch all refs from the Git server when given a SHA as a revision.
Dworkspaces.rst15 project. This branch points to the revision that the manifest file
18 point for the upstream revision as of this latest update. Among other
219 revision: v2.5.0
242 revision: v2.5.0
245 revision: some-sha-goes-here
258 :file:`zephyr/west.yml` revision, instead of having to be copy/pasted (and
313 revision: v2.5.0
316 revision: SOME_SHA_OR_BRANCH_OR_TAG
318 revision: ANOTHER_SHA_OR_BRANCH_OR_TAG
Dmanifest.rst61 going back to a revision before it was introduced.
69 name as a manifest revision, at the cost of being able to bisect
182 revision: v1.3
185 revision: abcde413a111
197 Since the project has no ``revision`` specified, ``master`` is used by
251 * - ``revision``
252 - Optional. The Git revision that ``west update`` should
255 ``revision`` value from the ``defaults`` subsection will be used if
258 A project revision can be a branch, tag, or SHA.
260 The default ``revision`` is ``master`` if not otherwise specified.
[all …]
/Zephyr-Core-3.4.0/boards/arm/legend/doc/
Dindex.rst10 The Legend 2.5" HDD board (revision 25hdd) can be found in the Seagate FireCuda
17 The Legend 2.5" SSD board (revision 25ssd) is found in the Seagate SSD Gaming
21 The Legend 3.5" board (revision 35) can be found in the Seagate FireCuda Gaming
/Zephyr-Core-3.4.0/doc/_extensions/zephyr/
Dlink-roles.py83 rev = project.revision

1234