Home
last modified time | relevance | path

Searched refs:unaligned (Results 1 – 9 of 9) sorted by relevance

/rk3399_rockchip-uboot/doc/
H A DREADME.unaligned-memory-access.txt9 unaligned accesses, why you need to write code that doesn't cause them,
13 The definition of an unaligned access
19 reading 4 bytes of data from address 0x10005 would be an unaligned memory
46 Why unaligned access is bad
49 The effects of performing an unaligned memory access vary from architecture
53 - Some architectures are able to perform unaligned memory accesses
55 - Some architectures raise processor exceptions when unaligned accesses
56 happen. The exception handler is able to correct the unaligned access,
58 - Some architectures raise processor exceptions when unaligned accesses
60 unaligned access to be corrected.
[all …]
H A DREADME.displaying-bmps4 Some architectures cannot handle unaligned memory accesses, and an attempt to
24 the __u32 fields into unaligned addresses (in our example 0x80a00002,
H A DREADME.NDS3220 - Multiple aligned and unaligned memory accesses for memory copy and stack
/rk3399_rockchip-uboot/arch/arm/cpu/armv7m/
H A Dconfig.mk8 PLATFORM_CPPFLAGS += -march=armv7-m -mthumb -mno-unaligned-access
/rk3399_rockchip-uboot/arch/sh/include/asm/
H A Dunaligned-sh4a.h26 unsigned long unaligned; in __get_unaligned_cpu32() local
30 : "=z" (unaligned) in __get_unaligned_cpu32()
34 return unaligned; in __get_unaligned_cpu32()
/rk3399_rockchip-uboot/arch/arm/cpu/armv7/
H A Dconfig.mk12 PF_NO_UNALIGNED := $(call cc-option, -mno-unaligned-access,)
/rk3399_rockchip-uboot/doc/device-tree-bindings/mtd/
H A Dmtd-physmap.txt19 - no-unaligned-direct-access: boolean to disable the default direct
23 unaligned accesses as implemented in the JFFS2 code via memcpy().
24 By defining "no-unaligned-direct-access", the flash will not be
/rk3399_rockchip-uboot/arch/arm/lib/
H A Dmemset.S24 ands r3, r0, #3 @ 1 unaligned?
/rk3399_rockchip-uboot/
H A DREADME1453 abort. If you think you will not have problems with unaligned