Home
last modified time | relevance | path

Searched full:differently (Results 1 – 25 of 39) sorted by relevance

12

/Zephyr-Core-3.5.0/kernel/
Dmain_weak.c8 /* Linkers may treat weak functions differently if they are located within
/Zephyr-Core-3.5.0/doc/connectivity/networking/
Dnet_pkt_processing_stats.rst68 differently so there is slight difference because of rounding errors.
84 differently so there is slight difference because of rounding errors.
/Zephyr-Core-3.5.0/boards/arm/lpcxpresso55s69/
Dlpcxpresso55s69_cpu1.dts31 * allocate the SRAM0-4 differently.
Dlpcxpresso55s69_cpu0.dts79 * allocate the SRAM0-4 differently.
/Zephyr-Core-3.5.0/samples/application_development/code_relocation_nocopy/
DREADME.rst11 Differently from the code relocation sample, this sample is relocating the
/Zephyr-Core-3.5.0/doc/_extensions/zephyr/
Ddtcompatible-role.py20 that happens if a binding behaves differently depending on the bus the
/Zephyr-Core-3.5.0/drivers/serial/
Duart_native_tty_bottom.h20 /* Below enums are just differently namespaced copies of uart_config_* enums. Options that are not
/Zephyr-Core-3.5.0/boards/arm/lpcxpresso54114/
Dlpcxpresso54114_m4.dts54 * allocate the SRAM0-3 differently.
/Zephyr-Core-3.5.0/dts/bindings/gpio/
Datmel-xplained-pro-header.yaml23 large boards), and EXT3. EXT4 to EXT7 can be placed differently depending
/Zephyr-Core-3.5.0/dts/bindings/pinctrl/
Dnxp,imx-iomuxc.yaml47 # will need to initialize the pin configuration register differently based on
/Zephyr-Core-3.5.0/cmake/linker/lld/
Dtarget.cmake16 # Different generators deal with depfiles differently.
/Zephyr-Core-3.5.0/include/zephyr/net/
Dnet_linkaddr.h85 * handled differently than uint8_t addr[] and the fields are purposely
/Zephyr-Core-3.5.0/cmake/linker/arcmwdt/
Dtarget.cmake16 # Different generators deal with depfiles differently.
/Zephyr-Core-3.5.0/kernel/include/
Dkswap.h45 * Stated differently: there's a chicken and egg bug with the question
/Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/cavs/
Dmultiprocessing.c45 /* On cAVS v2.5, MP startup works differently. The core has in soc_start_core()
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/
Dblob.rst175 same Timeout Base value, but they calculate timeout differently.
/Zephyr-Core-3.5.0/subsys/bluetooth/controller/util/
Dmfifo.h25 * Enqueuing is performed differently between APIs:
/Zephyr-Core-3.5.0/cmake/modules/
Dkconfig.cmake116 # cmake commands are escaped differently
/Zephyr-Core-3.5.0/drivers/interrupt_controller/
Dintc_ioapic.c21 * system. The IO APIC handles interrupts very differently than the 8259A.
/Zephyr-Core-3.5.0/arch/arc/include/
Dswap_macros.h271 * status32 differently depending on the execution context they are
/Zephyr-Core-3.5.0/subsys/bluetooth/controller/ll_sw/
Dull_sched.c491 * might work differently in a non-debug build. in after_match_slot_get()
/Zephyr-Core-3.5.0/tests/subsys/logging/log_msg/src/
Dmain.c128 * The various tests create cbprintf packages differently in clear_pkg_flags()
/Zephyr-Core-3.5.0/boards/xtensa/intel_adsp_cavs25/doc/
Dchromebooks_adsp.rst232 You will need to set some custom configuration variables differently
/Zephyr-Core-3.5.0/boards/arm/nrf9160dk_nrf52840/doc/
Dindex.rst175 If you want to route some of the above pins differently or enable any of the
/Zephyr-Core-3.5.0/doc/_scripts/
Dgen_devicetree_rest.py347 differently depending on the bus the node appears on.

12