Searched refs:wrapper (Results 1 – 19 of 19) sorted by relevance
138 $(libfdt) libfdt-wrapper.c \174 src-plat-$(CONFIG_EPAPR_BOOT) += epapr.c epapr-wrapper.c240 $(obj)/wrapper.a: $(obj-wlib) FORCE245 targets += $(patsubst $(obj)/%,%,$(obj-boot) wrapper.a) zImage.lds246 extra-y := $(obj)/wrapper.a $(obj-plat) $(obj)/empty.o \251 wrapper := $(src)/wrapper macro253 $(wrapper) FORCE454 WRAPPER_OBJDIR := /usr/lib/kernel-wrapper455 WRAPPER_DTSDIR := /usr/lib/kernel-wrapper/dts461 wrapper-installed := $(DESTDIR)$(WRAPPER_BINDIR)/wrapper[all …]
498 $platformo $tmp $object/wrapper.a
20 ldl $25,0($25) # Pick up the wrapper data.32 jmp ($3) # Return directly to caller of wrapper.
36 if a "wrapper" is not being used, the kernel will need to include
8 if a "wrapper" is not being used, the kernel will need to include
51 obj-$(CONFIG_EFI) += efi.o efi-rt-wrapper.o
187 * the wrapper. If your device doesn't support188 * passing data to the wrapper (in the form
501 /* Needed for dtbImage boot wrapper compatibility */
369 MCW0: memory-controller-wrapper {
144 * should provide a wrapper .dts file that
578 * The wrapper around the PCIe block has a bug
1581 compatible = "qcom,adreno-gmu-wrapper";
1807 compatible = "qcom,adreno-gmu-wrapper";
681 pcie_phy: phy-wrapper@34000 {
2229 ufs_mem_phy: phy-wrapper@1d87000 {
386 Used to allow a board to specify it wants an ePAPR compliant wrapper.
2136 ufs_wrapper: ufs-wrapper@4e80000 {
1831 ufs_wrapper: ufs-wrapper@4e80000 {
2261 * the AArch64 boot wrapper since commit 5e1261e08abf
Completed in 51 milliseconds