freebsd-dev/sys/boot/efi/libefi/Makefile

# $FreeBSD$

LIB=	efi
INTERNALLIB=
WARNS?=	2

SRCS=	delay.c devpath.c efi_console.c efinet.c efipart.c env.c errno.c \
	handles.c libefi.c time.c

.if ${MACHINE_CPUARCH} == "aarch64"
CFLAGS+=	-msoft-float -mgeneral-regs-only
.endif
.if ${MACHINE_ARCH} == "amd64"
CFLAGS+= -fPIC -mno-red-zone
.endif
CFLAGS+= -I${.CURDIR}/../include
CFLAGS+= -I${.CURDIR}/../include/${MACHINE}
CFLAGS+= -I${.CURDIR}/../../../../lib/libstand

# Pick up the bootstrap header for some interface items
CFLAGS+= -I${.CURDIR}/../../common

# Handle FreeBSD specific %b and %D printf format specifiers
CFLAGS+= ${FORMAT_EXTENSIONS}
CFLAGS+= -DTERM_EMU

.include <bsd.lib.mk>
First approximation of an ia64 EFI loader. Not functional. 2001-06-09 16:49:51 +00:00			`# $FreeBSD$`

o Introduce efimd_va2pa() to translate addresses in efi_copy{in\|out}() and efi_readin(). This removes MD code from copy.c. o Don't unconditionally add pal.S to SRCS. It's specific to ia64. 2004-11-28 00:30:22 +00:00			`LIB= efi`
For variables that are only checked with defined(), don't provide any fake value. 2004-10-24 15:33:08 +00:00			`INTERNALLIB=`
Enable warnings in EFI boot code Set WARNS if not set for EFI boot code and fix the issues highlighted by setting it. Most components are set to WARNS level 6 with few being left at lower levels due to the amount of changes needed to fix at higher levels. Error types fixed: * Missing / invalid casts * Missing inner structs * Unused vars * Missing static for internal only funcs * Missing prototypes * Alignment changes * Use of uninitialised vars * Unknown pragma (intrinsic) * Missing types etc due to missing includes * printf formatting types Reviewed by: emaste (in part) MFC after: 2 weeks X-MFC-With: r293268 Sponsored by: Multiplay Differential Revision: https://reviews.freebsd.org/D4839 2016-01-12 02:17:39 +00:00			`WARNS?= 2`
First approximation of an ia64 EFI loader. Not functional. 2001-06-09 16:49:51 +00:00
Add some routines for working with EFI DEVICE_PATH objects. - efi_lookup_devpath() uses the DEVICE_PATH_PROTOCOL to obtain the DEVICE_PATH for a given EFI handle. - efi_lookup_image_devpath() uses the LOADED_IMAGE_DEVICE_PATH_PROTOCOL to lookup the device path of the device used to load a loaded image. - efi_devpath_name() uses the DEVICE_PATH_TO_TEXT_PROTOCOL to generate a string description of a device path. The returned string is a CHAR16 string that can be printed via the recently added '%S' format in libstand's printf(). Note that the returned string is returned in allocated storage that should be freed by calling efi_free_devpath_name(). - efi_devpath_last_node() walks a DEVICE_PATH returning a pointer to the final node in the path (not counting the terminating node). That is, it returns a pointer to the last meaninful node in a DEVICE_PATH. - efi_devpath_trim() generates a new DEVICE_PATH from an existing DEVICE_PATH. The new DEVICE_PATH does not include the last non-terminating node in the original path. If the original DEVICE_PATH only contains the terminating node, this function returns NULL. The caller is responsible for freeing the returned DEVICE_PATH via free(). - efi_devpath_handle() attempts to find a handle that corresponds to a given device path. However, if nodes at the end of the device path do not have valid handles associated with them, this function will return a handle that matches a node earlier in the device path. In particular, this function returns a handle for the node closest to the end of the device path which has a valid handle. Sponsored by: Cisco Systems 2016-05-26 21:43:22 +00:00			`SRCS= delay.c devpath.c efi_console.c efinet.c efipart.c env.c errno.c \`
			`handles.c libefi.c time.c`
Lookup the EFI_FPSWA driver and pass the interface pointer through to the kernel before we call ExitBootServices(). I've typed the definitions in efifpswa.h from the Intel FPSWA manual (urk). 2001-11-19 07:09:47 +00:00
Disable the use of floating-point and vector registers in the loader. They need the vfp unit to be enabled which may not be the case. 2015-05-05 11:00:50 +00:00			`.if ${MACHINE_CPUARCH} == "aarch64"`
			`CFLAGS+= -msoft-float -mgeneral-regs-only`
			`.endif`
Add -fPIC for amd64 Sponsored by: The FreeBSD Foundation 2014-04-03 23:10:23 +00:00			`.if ${MACHINE_ARCH} == "amd64"`
The System V ABI for amd64 allows functions to use space in a 128 byte redzone below the stack pointer for scratch space and requires interrupt and signal frames to avoid overwriting it. However, EFI uses the Windows ABI which does not support this. As a result, interrupt handlers in EFI push their interrupt frames directly on top of the stack pointer. If the compiler used the red zone in a function in the EFI loader, then a device interrupt that occurred while that function was running could trash its local variables. In practice this happens fairly reliable when using gzipfs as an interrupt during decompression can trash the local variables in the inflate_table() function resulting in corrupted output or hangs. Fix this by disabling the redzone for amd64 EFI binaries. This requires building not only the loader but any libraries used by the loader without redzone support. Thanks to Jilles for pointing me at the redzone once I found the stack corruption. Differential Revision: https://reviews.freebsd.org/D2054 Reviewed by: imp MFC after: 2 weeks Sponsored by: Cisco Systems, Inc. 2015-03-13 09:38:16 +00:00			`CFLAGS+= -fPIC -mno-red-zone`
Add -fPIC for amd64 Sponsored by: The FreeBSD Foundation 2014-04-03 23:10:23 +00:00			`.endif`
o Introduce efimd_va2pa() to translate addresses in efi_copy{in\|out}() and efi_readin(). This removes MD code from copy.c. o Don't unconditionally add pal.S to SRCS. It's specific to ia64. 2004-11-28 00:30:22 +00:00			`CFLAGS+= -I${.CURDIR}/../include`
Use MACHINE in the efi loader when it is what we mean, it may not be the same as MACHINE_CPUARCH, it just happened to be the case the architectures this code currently supports. Sponsored by: The FreeBSD Foundation 2015-04-14 10:40:37 +00:00			`CFLAGS+= -I${.CURDIR}/../include/${MACHINE}`
o Introduce efimd_va2pa() to translate addresses in efi_copy{in\|out}() and efi_readin(). This removes MD code from copy.c. o Don't unconditionally add pal.S to SRCS. It's specific to ia64. 2004-11-28 00:30:22 +00:00			`CFLAGS+= -I${.CURDIR}/../../../../lib/libstand`
First approximation of an ia64 EFI loader. Not functional. 2001-06-09 16:49:51 +00:00
			`# Pick up the bootstrap header for some interface items`
o Introduce efimd_va2pa() to translate addresses in efi_copy{in\|out}() and efi_readin(). This removes MD code from copy.c. o Don't unconditionally add pal.S to SRCS. It's specific to ia64. 2004-11-28 00:30:22 +00:00			`CFLAGS+= -I${.CURDIR}/../../common`
First approximation of an ia64 EFI loader. Not functional. 2001-06-09 16:49:51 +00:00
Since clang 3.6.0 now implements the archetype 'freebsd_kprintf' for __attribute__((format(...))), and the -fformat-extensions flag was removed, introduce a new macro in bsd.sys.mk to choose the right variant of compile flag for the used compiler, and use it. Also add something similar to kern.mk, since including bsd.sys.mk from that file will anger Warner. :-) Note that bsd.sys.mk does not support the MK_FORMAT_EXTENSIONS knob used in kern.mk, since that knob is only available in kern.opts.mk, not in src.opts.mk. We might want to add it later, to more easily support external compilers for building world (in particular, sys/boot). 2015-01-28 18:36:33 +00:00			`# Handle FreeBSD specific %b and %D printf format specifiers`
			`CFLAGS+= ${FORMAT_EXTENSIONS}`
loader.efi: add terminal emulation support This is based on the vidconsole implementation. Submitted by: Toomas Soome <tsoome@me.com> Reviewed by: adrian MFC after: 2 weeks Relnotes: Yes Differential Revision: https://reviews.freebsd.org/D4797 2016-01-06 15:38:39 +00:00			`CFLAGS+= -DTERM_EMU`
Supress clang warning for FreeBSD printf %b and %D formats MFC after: 2 weeks 2014-07-22 04:37:47 +00:00
First approximation of an ia64 EFI loader. Not functional. 2001-06-09 16:49:51 +00:00			`.include <bsd.lib.mk>`