Home
last modified time | relevance | path

Searched full:bases (Results 1 – 16 of 16) sorted by relevance

/Zephyr-latest/include/zephyr/xen/public/
Dmemory.h40 * OUT: MFN (*not* GMFN) bases of extents that were allocated
42 * IN: GMFN bases of extents to free
44 * IN: GPFN bases of extents to populate with memory
45 * OUT: GMFN bases of extents that were allocated
/Zephyr-latest/soc/nxp/kinetis/k8x/
Dsoc.h29 /* address bases */
/Zephyr-latest/soc/nxp/kinetis/kv5x/
Dsoc.h29 /* address bases */
/Zephyr-latest/soc/nxp/kinetis/k6x/
Dsoc.h22 /* address bases */
/Zephyr-latest/soc/nxp/kinetis/k2x/
Dsoc.h27 /* address bases */
/Zephyr-latest/include/zephyr/xen/
Dmemory.h60 * @param extent_start page frame bases of extents to populate with memory.
/Zephyr-latest/tests/bluetooth/shell/
Daudio.conf4 # Needed for devices with many PAC records or large BASEs
/Zephyr-latest/dts/bindings/gpio/
Dadi,max22190-gpio.yaml8 Fiter configuration could be done on per channel bases, which
/Zephyr-latest/scripts/ci/
Dpylintrc111 duplicate-bases,
/Zephyr-latest/include/zephyr/sys/
Dmulti_heap.h182 * for the heap used will be bases on the cfg parameter (same as in sys_multi_heap_aligned_alloc).
/Zephyr-latest/doc/project/
Drelease_process.rst351 auditable code bases shall be kept in sync after the audit branch is created,
/Zephyr-latest/doc/security/
Dsecurity-overview.rst383 mistakes in large code bases. All code shall be analyzed using an
/Zephyr-latest/arch/x86/
Dgen_mmu.py42 both memory bases.
/Zephyr-latest/doc/develop/west/
Dmanifest.rst149 bases are respectively ``https://git.example.com/base1`` and
150 ``https://git.example.com/base2``. You can use SSH URL bases as well; for
/Zephyr-latest/doc/releases/
Drelease-notes-3.6.rst112 so that Zephyr supports all BASEs regardless of the size.
/Zephyr-latest/doc/
Dzephyr.doxyfile.in2911 # or 2 may greatly reduce the computation time needed for large code bases. Also