d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
acf82d2659
freebsd-dev/sys/boot/efi/libefi/Makefile

54 lines
1.5 KiB
Makefile
Raw Normal View History

First approximation of an ia64 EFI loader. Not functional.
2001-06-09 16:49:51 +00:00
# $FreeBSD$
Fix the build on both arm64 and when WITHOUT_FORTH is defined. * On arm64 we need to use the ${MACHINE_CPUARCH} subdirectory. * env.c is only needed when using forth so only build it there. Sponsored by: ABT Systems Ltd
2016-10-25 14:01:13 +00:00
.include <src.opts.mk>
Really make WITHOUT_FORTH (MK_FORTH==no) work. The recent inclusion of FICL definitions not in ficl/ficl32 files broke this generally. This makes that stuff conditional on BOOT_FORTH. Also, move definitions related to the architecture (FICL_CPUARCH and friends) into Makefile.ficl that all parts of the tree that include files with ficl need to include (but only if MK_FORTH == yes). In addition, had to fix library ordering issue with LIBSTAND to keep it last. Without boot forth, there's no references to memset to bring in memset.o from libstand.a to satisfy libgeliboot.a's use of it. Listing libstand last solves this issue (and it's the proper place for libstand to boot).
2016-10-25 17:31:57 +00:00
.if ${MK_FORTH} != "no"
loader.efi environment related cleanups Since we have dedicated libefi/env.c file for variable support, the following changes are done: Simple cstyle changes in env.c Moved efi variable related commands from loader/main.c to libefi/env.c Did create function to set "efi-version" environment variable in env.c. This function does serve two purposes: for first a small clean up of the loader main(), and for second, it does replace the otherwise unused efi_variable_support hack. A bit of cleanup of ficl backend functions. The TEST_MAIN has no meaning, and removed few memory leaks. The forth code is updated to use "efi-version" variable, instead of ficl environment check. Reviewed by: imp Approved by: imp (mentor) Differential Revision: https://reviews.freebsd.org/D9165
2017-02-01 08:46:59 +00:00
CFLAGS+= -DBOOT_FORTH
Really make WITHOUT_FORTH (MK_FORTH==no) work. The recent inclusion of FICL definitions not in ficl/ficl32 files broke this generally. This makes that stuff conditional on BOOT_FORTH. Also, move definitions related to the architecture (FICL_CPUARCH and friends) into Makefile.ficl that all parts of the tree that include files with ficl need to include (but only if MK_FORTH == yes). In addition, had to fix library ordering issue with LIBSTAND to keep it last. Without boot forth, there's no references to memset to bring in memset.o from libstand.a to satisfy libgeliboot.a's use of it. Listing libstand last solves this issue (and it's the proper place for libstand to boot).
2016-10-25 17:31:57 +00:00
.include "${.CURDIR}/../../Makefile.ficl"
.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
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
loader.efi environment related cleanups Since we have dedicated libefi/env.c file for variable support, the following changes are done: Simple cstyle changes in env.c Moved efi variable related commands from loader/main.c to libefi/env.c Did create function to set "efi-version" environment variable in env.c. This function does serve two purposes: for first a small clean up of the loader main(), and for second, it does replace the otherwise unused efi_variable_support hack. A bit of cleanup of ficl backend functions. The TEST_MAIN has no meaning, and removed few memory leaks. The forth code is updated to use "efi-version" variable, instead of ficl environment check. Reviewed by: imp Approved by: imp (mentor) Differential Revision: https://reviews.freebsd.org/D9165
2017-02-01 08:46:59 +00:00
SRCS= delay.c devpath.c efi_console.c efinet.c efipart.c env.c errno.c \
Add definitions and utilities for EFI drivers This patch adds definitions and utility code for creating EFI drivers using the EFI_DRIVER_BINDING_PROTOCOL. Submitted by: Eric McCorkle Differential Revision: https://reviews.freebsd.org/D11852
2017-08-04 04:16:41 +00:00
handles.c wchar.c libefi.c efi_driver_utils.c
Use the UEFI event timer to update the time on arm and arm64. The current code uses the GetTime function from the Runtime Service, however this has been shown to not return a useable time on many arm64 UEFI implementations. Reviewed by: jhb, smh Sponsored by: ABT Systems Ltd Differential Revision: https://reviews.freebsd.org/D6709
2016-06-04 08:47:45 +00:00
.if ${MACHINE_CPUARCH} == "amd64" || ${MACHINE_CPUARCH} == "i386"
SRCS+= time.c
.elif ${MACHINE_CPUARCH} == "aarch64" || ${MACHINE_CPUARCH} == "arm"
SRCS+= time_event.c
.endif
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
Apply the printf %S band-aid for efinet.c to fix the arm64 build.
2016-05-26 23:07:20 +00:00
# We implement a slightly non-standard %S in that it always takes a
# CHAR16 that's common in UEFI-land instead of a wchar_t. This only
# seems to matter on arm64 where wchar_t defaults to an int instead
# of a short. There's no good cast to use here so just ignore the
# warnings for now.
CWARNFLAGS.efinet.c+= -Wno-format
efipart is also using the '%S' printf format, add -Wno-format for it. This fix building for armv6.
2017-02-07 15:16:01 +00:00
CWARNFLAGS.efipart.c+= -Wno-format
loader: libefi/env.c warnings in arm build The arm build has revealed some of the warnings, the fix for CHAR16 warning is to switch the warning off for env.c (same as for efinet.c). For error code we need to use macro. Reported by: gjb Reviewed by: imp Approved by: imp (mentor) Differential Revision: https://reviews.freebsd.org/D9422
2017-02-03 16:39:10 +00:00
CWARNFLAGS.env.c+= -Wno-format
Apply the printf %S band-aid for efinet.c to fix the arm64 build.
2016-05-26 23:07:20 +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"
Do not use -msoft-float with intention of disabling FP on aarch64 GNU GCC does does recognise it as a valid option and we already use -mgeneral-regs-only that has the desired effect. Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D10306
2017-04-07 22:58:25 +00:00
CFLAGS+= -mgeneral-regs-only
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
.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}
Do not use TERM_EMU on arm and arm64 as it doesn't behave well with serial console. Reviewed by: andrew, emaste MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D6783
2016-07-19 19:00:22 +00:00
# Do not use TERM_EMU on arm and arm64 as it doesn't behave well with serial console
.if ${MACHINE_CPUARCH} != "arm" && ${MACHINE_CPUARCH} != "aarch64"
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
Do not use TERM_EMU on arm and arm64 as it doesn't behave well with serial console. Reviewed by: andrew, emaste MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D6783
2016-07-19 19:00:22 +00:00
.endif
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>
Reference in New Issue Copy Permalink