Searched refs:resolve (Results 26 – 50 of 59) sorted by relevance
123
/Zephyr-latest/scripts/west_commands/ |
D | patch.py | 545 return Path(module_name_or_path).resolve().relative_to(topdir)
|
/Zephyr-latest/scripts/west_commands/runners/ |
D | nrf_common.py | 76 return str(suit_starter.resolve())
|
D | jlink.py | 281 Path(self.require(self.commander)).resolve())
|
/Zephyr-latest/scripts/dts/python-devicetree/tests/ |
D | test_edtlib.py | 555 binding_file = Path("test-bindings/child-binding.yaml").resolve() 564 binding_file = Path("test-bindings/child-binding-with-compat.yaml").resolve()
|
/Zephyr-latest/scripts/pylib/twister/twisterlib/ |
D | hardwaremap.py | 336 return str((by_id / link).resolve())
|
/Zephyr-latest/scripts/release/ |
D | list_devicetree_bindings_changes.py | 20 HERE = Path(__file__).parent.resolve()
|
/Zephyr-latest/doc/services/tfm/ |
D | build.rst | 47 For example, the following will resolve to ``<path>/tfm_s.hex``:
|
/Zephyr-latest/doc/contribute/ |
D | contributor_expectations.rst | 207 resolve and hide comments, they must let the initial reviewer do it. The 276 - Optionally resolve in the next `Zephyr Dev Meeting`_ meeting with more
|
D | external.rst | 203 TSC approval or identify other approaches that can resolve the
|
D | bin_blobs.rst | 205 maintainers may accept and attempt to resolve such issues.
|
/Zephyr-latest/scripts/west_commands/completion/ |
D | west-completion.fish | 374 complete -c west -n "__zephyr_west_seen_subcommand_from manifest" -l resolve -d "resolve into singl… 375 complete -c west -n "__zephyr_west_seen_subcommand_from manifest" -l freeze -d "resolve into single…
|
/Zephyr-latest/scripts/kconfig/ |
D | kconfigfunctions.py | 15 ZEPHYR_BASE = str(Path(__file__).resolve().parents[2])
|
/Zephyr-latest/arch/xtensa/core/ |
D | README_MMU.txt | 180 exceptions is now complete, but cannot be used until we resolve the 185 doing data accesses yet (including refills), and will resolve the
|
/Zephyr-latest/doc/develop/west/ |
D | manifest.rst | 1284 :ref:`resolving your manifest <west-manifest-resolve>` to see the final results 1483 :file:`zephyr/west.yml` is ignored entirely. See :ref:`west-manifest-resolve` 1622 usual, see :ref:`west-manifest-resolve` for troubleshooting advice. 2175 .. _west-manifest-resolve: 2180 The ``--resolve`` action outputs a single manifest file equivalent to your 2185 west manifest --resolve [-o outfile] 2196 west -v manifest --resolve
|
D | built-in.rst | 159 should immediately resolve these conflicts as you usually do with
|
D | release-notes.rst | 91 and ``west manifest --resolve`` commands currently cannot be used when 468 - Commands like ``west manifest --resolve`` now correctly include group and
|
/Zephyr-latest/scripts/footprint/ |
D | size_report | 293 path = path.resolve()
|
/Zephyr-latest/doc/connectivity/bluetooth/ |
D | bluetooth-ctlr-arch.rst | 209 * Spec states rules for how to handle/resolve collisions when they happen
|
/Zephyr-latest/boards/nxp/mimxrt1040_evk/doc/ |
D | index.rst | 352 To resolve this, you may remove the M.2 WiFi module from the board when
|
/Zephyr-latest/tests/benchmarks/thread_metric/ |
D | thread_metric_readme.txt | 82 code to resolve some minor issues found during porting.
|
/Zephyr-latest/scripts/ci/ |
D | check_compliance.py | 33 sys.path.insert(0, str(Path(__file__).resolve().parents[1])) 1924 ZEPHYR_BASE = str(Path(__file__).resolve().parents[2])
|
/Zephyr-latest/doc/hardware/peripherals/can/ |
D | controller.rst | 67 They resolve by the fact that dominant bits override recessive bits.
|
/Zephyr-latest/doc/project/ |
D | project_roles.rst | 114 assignee to advance the review process and resolve any disagreements.
|
/Zephyr-latest/subsys/bluetooth/host/ |
D | Kconfig | 470 generate and resolve (recognize) the private addresses of an identity. 475 forever resolve addresses from that IRK, even if that bond has been
|
/Zephyr-latest/doc/_extensions/zephyr/doxytooltip/static/tippy/ |
D | popper.min.js | 7 …date(),e(f)}))},function(){return s||(s=new Promise((function(e){Promise.resolve().then((function(…
|
123