Home
last modified time | relevance | path

Searched refs:base (Results 776 – 800 of 833) sorted by relevance

1...<<31323334

/Zephyr-latest/cmake/modules/
Dkconfig.cmake383 --zephyr-base=${ZEPHYR_BASE}
Dextensions.cmake435 # provided base and writes it to the argument "lib_name"
436 macro(zephyr_library_get_current_dir_lib_name base lib_name)
438 file(RELATIVE_PATH name ${base} ${CMAKE_CURRENT_LIST_FILE})
947 # OPTIONAL: Revision specifier is optional. If revision is not provided the base
2658 # BASE_DIR <base-dir>: convert paths relative to <base-dir>
4191 # Get the base address of the register block at index <idx>, or with
4204 # - The base address of the register block
5022 # When MMU is active and Kernel VM base and offset is different
5023 # from SRAM base and offset, then the region defined by KVMA will
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_callbacks.rst24 The base callback/notification system can be enabled using
/Zephyr-latest/boards/nxp/mr_canhubk3/doc/
Dindex.rst344 …roducts/interfaces/ethernet-/automotive-ethernet-phys/asil-b-compliant-100base-t1-ethernet-phy:TJA…
/Zephyr-latest/doc/hardware/porting/
Dboard_porting.rst286 #. :file:`Kconfig.plank`: the base software configuration for selecting SoC and
433 This allows board maintainers to write a base devicetree file for the board
590 CPU clusters, and board variants in the base :file:`plank_defconfig` and only
/Zephyr-latest/doc/security/
Dsecure-coding.rst188 project's code base, is comfortable making changes to it, and is
/Zephyr-latest/boards/microchip/mec15xxevb_assy6853/doc/
Dindex.rst198 The jumper configuration explained above covers the base board. The ASSY
/Zephyr-latest/boards/qemu/x86/
Dqemu_x86_tiny.ld24 /* Virtual base address for the kernel; with CONFIG_MMU this is not necessarily
/Zephyr-latest/doc/contribute/
Dguidelines.rst858 a ``This branch is out-of-date with the base branch`` message and a
931 https://git-scm.com/docs/git-rebase#Documentation/git-rebase.txt---keep-base
933 #. When pushing follow-up changes, use the ``--keep-base`` option of
/Zephyr-latest/doc/releases/
Drelease-notes-3.1.rst430 * Renamed the base Bosch M_CAN devicetree binding compatible from ``bosch,m-can-base`` to
431 :dtcompatible:`bosch,m_can-base`.
821 * :dtcompatible:`bosch,m_can-base` has replaced ``bosch,m-can-base``
1186 - :github:`42030` - can: "bosch,m-can-base": Warning "missing or empty reg/ranges property"
1826 * :github:`42310` - Support for TCA6408A gpio expander, which existing driver as a base?
/Zephyr-latest/subsys/debug/
DKconfig148 continue, which can be useful if a code base has known
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/
Dcap.rst230 CAP Broadcast source updated with new metadata. Update the advertised base via `bt per-adv-data`
/Zephyr-latest/doc/services/device_mgmt/smp_groups/
Dsmp_group_8.rst406 the base functionality, supported hash/checksum are opt-in with
/Zephyr-latest/boards/toradex/colibri_imx7d/doc/
Dindex.rst506 …https://developer.toradex.com/knowledge-base/freertos-on-the-cortex-m4-of-a-colibri-imx7#Memory_ar…
/Zephyr-latest/arch/arm/core/cortex_m/
DKconfig137 The VTOR indicates the offset of the vector table base
/Zephyr-latest/subsys/net/ip/
DKconfig443 int "Transmit traffic class base thread priority"
452 int "Receive traffic class base thread priority"
/Zephyr-latest/doc/build/kconfig/
Dtips.rst863 file in Zephyr), it is best to only give the symbol type for the "base"
865 value``) for the remaining definitions. That way, if the base definition of
/Zephyr-latest/doc/develop/tools/
Dcoccinelle.rst283 spatch could proceed the entire code base more quickly.
/Zephyr-latest/samples/subsys/mgmt/updatehub/
DREADME.rst172 The ethernet depends only from base configuration.
/Zephyr-latest/modules/trusted-firmware-m/
DKconfig.tfm82 bool "TF-M build profile: not set (base)"
/Zephyr-latest/boards/arm/mps2/doc/
Dmps2_an521.rst63 the offset value is the offset from the base of the 4MB code or SRAM block,
/Zephyr-latest/arch/
DKconfig226 The SRAM base address. The default value comes from
249 This option specifies the base address of the flash on the board. It is
/Zephyr-latest/doc/kernel/drivers/
Dindex.rst110 example, base memory mapped IO addresses, IRQ line numbers, or other fixed
/Zephyr-latest/doc/connectivity/networking/conn_mgr/
Dimplementation.rst263 Therefore, do not base implementation behaviors on iface state.
/Zephyr-latest/doc/hardware/pinctrl/
Dindex.rst409 include: [base.yaml, pinctrl-device.yaml]

1...<<31323334