Home
last modified time | relevance | path

Searched full:i386 (Results 1 – 25 of 42) sorted by relevance

12

/rk3399_rockchip-uboot/tools/binman/test/
H A Du_boot_ucode_ptr.lds7 OUTPUT_FORMAT("elf32-i386", "elf32-i386", "elf32-i386")
8 OUTPUT_ARCH(i386)
H A Du_boot_no_ucode_ptr.c10 * cc -march=i386 -m32 -o u_boot_no_ucode_ptr -T u_boot_ucode_ptr.lds \
H A Du_boot_ucode_ptr.c10 * cc -march=i386 -m32 -o u_boot_ucode_ptr -T u_boot_ucode_ptr.lds -nostdlib \
/rk3399_rockchip-uboot/arch/x86/cpu/
H A Du-boot-spl.lds9 OUTPUT_FORMAT("elf32-i386", "elf32-i386", "elf32-i386")
10 OUTPUT_ARCH(i386)
H A Du-boot.lds9 OUTPUT_FORMAT("elf32-i386", "elf32-i386", "elf32-i386")
10 OUTPUT_ARCH(i386)
H A DMakefile22 $(if $(CONFIG_EFI_STUB_64BIT),-march=i386 -m32)
54 obj-y += i386/
H A Dconfig.mk8 CROSS_COMPILE ?= i386-linux-
H A Du-boot-64.lds10 OUTPUT_ARCH(i386:x86-64)
/rk3399_rockchip-uboot/arch/x86/lib/
H A Delf_ia32_efi.lds9 OUTPUT_FORMAT("elf32-i386", "elf32-i386", "elf32-i386")
10 OUTPUT_ARCH(i386)
H A DMakefile68 # When building for 64-bit we must remove the i386-specific flags
69 CFLAGS_REMOVE_reloc_x86_64_efi.o += -mregparm=3 -march=i386 -m32
72 AFLAGS_REMOVE_crt0_x86_64_efi.o += -mregparm=3 -march=i386 -m32
H A Delf_x86_64_efi.lds10 OUTPUT_ARCH(i386:x86-64)
/rk3399_rockchip-uboot/lib/efi/
H A DMakefile11 $(if $(CONFIG_EFI_STUB_64BIT),-march=i386 -m32)
14 $(if $(CONFIG_EFI_STUB_64BIT),-march=i386 -m32)
/rk3399_rockchip-uboot/arch/x86/
H A Dconfig.mk27 PLATFORM_CPPFLAGS += -march=i386 -m32
55 EFIPAYLOAD_BFDTARGET = elf32-i386
61 EFIPAYLOAD_BFDARCH = i386
/rk3399_rockchip-uboot/tools/gdb/
H A DMakefile28 #BFD_ROOT_DIR = /LinuxPPC/CDK # Linux/i386
29 #BFD_ROOT_DIR = /usr/pkg/cross # NetBSD/i386
/rk3399_rockchip-uboot/arch/x86/include/asm/
H A Dsetjmp.h4 * From Linux arch/um/sys-i386/setjmp.S
H A Dzimage.h14 /* linux i386 zImage/bzImage header. Offsets relative to
H A Dmsr.h58 * both i386 and x86_64 returns 64-bit value in edx:eax, but gcc's "A"
59 * constraint has different meanings. For i386, "A" means exactly
/rk3399_rockchip-uboot/include/linux/
H A Dedd.h12 * In a nutshell, arch/{i386,x86_64}/boot/setup.S populates a scratch
15 * In arch/{i386,x86_64}/kernel/setup.c, this information is
H A Dapm_bios.h101 * in arch/i386/kernel/setup.c
/rk3399_rockchip-uboot/tools/buildman/
H A DREADME176 x86: i386
188 The toolchain-alias section indicates that the i386 toolchain should be used
242 - scanning path '/toolchains/gcc-4.9.0-nolibc/i386-linux'
243 - looking in '/toolchains/gcc-4.9.0-nolibc/i386-linux/.'
244 - looking in '/toolchains/gcc-4.9.0-nolibc/i386-linux/bin'
245 - found '/toolchains/gcc-4.9.0-nolibc/i386-linux/bin/i386-linux-gcc'
246 - looking in '/toolchains/gcc-4.9.0-nolibc/i386-linux/usr/bin'
247 Tool chain test: OK, arch='i386', priority 4
385 i386 : /toolchains/gcc-4.9.0-nolibc/i386-linux/bin/i386-linux-gcc
425 hppa hppa64 i386 ia64 m32r m68k mips mips64 or32 powerpc powerpc64 s390x sh4
[all …]
H A Dbsettings.py87 x86 = i386
/rk3399_rockchip-uboot/arch/powerpc/
H A Dconfig.mk27 # [Tested on NetBSD/i386 1.5 + cross-powerpc-netbsd-1.3]
/rk3399_rockchip-uboot/arch/x86/cpu/i386/
H A Dsetjmp.S4 * From Linux arch/um/sys-i386/setjmp.S
/rk3399_rockchip-uboot/doc/
H A DREADME.nvme86 $ ./qemu-system-i386 -drive file=nvme.img,if=none,id=drv0 -device nvme,drive=drv0,serial=QEMUNVME00…
/rk3399_rockchip-uboot/arch/mips/include/asm/
H A Dprocessor.h111 * (MIPS, Alpha) or is unuseable with -fomit-frame-pointer (i386).

12