move efivars to drivers/efi

PATCH New Matt Tolentino 1 participant 1 message Aug 9, 2003

lore

Share & tools

lore

Matt Tolentino

author

2003-08-09 01:04 UTC #0 lore raw

PATCH 1/1 move efivars to drivers/efi

Hi,

This patch against 2.6.0-test2 does several things:

1. Creates a new directory (drivers/efi) into which I propose current and future drivers that interact with EFI firmware be placed. This enables architectures that employ EFI compliant firmware to use the same drivers and avoid the maintenance hassle of multiple copies.

2. Move the current EFI variable services driver (efivars) found in arch/ia64/kernel into drivers/efi.

Note that I've added similar config options for x86 in a separate patch that also enables EFI awareness that I'll resend to the list shortly.

Thoughts? Comments?

thanks,
matt

arch/ia64/defconfig +1 -0

diff -urN linux-2.6.0-test2-bk/arch/ia64/defconfig linux-2.6.0-test2-bk-efi/arch/ia64/defconfig
@@ -76,6 +76,7 @@
 CONFIG_COMPAT=y
 CONFIG_PERFMON=y
 CONFIG_IA64_PALINFO=y
+CONFIG_EFI=y
 CONFIG_EFI_VARS=y
 CONFIG_NR_CPUS
 CONFIG_BINFMT_ELF=y

arch/ia64/Kconfig +1 -9

diff -urN linux-2.6.0-test2-bk/arch/ia64/Kconfig linux-2.6.0-test2-bk-efi/arch/ia64/Kconfig
@@ -433,15 +433,7 @@
 	  To use this option, you have to ensure that the "/proc file system
 	  support" (CONFIG_PROC_FS) is enabled, too.
 
-config EFI_VARS
-	tristate "/proc/efi/vars support"
-	help
-	  If you say Y here, you are able to get EFI (Extensible Firmware
-	  Interface) variable information in /proc/efi/vars.  You may read,
-	  write, create, and destroy EFI variables through this interface.
-
-	  To use this option, you have to check that the "/proc file system
-	  support" (CONFIG_PROC_FS) is enabled, too.
+source "drivers/efi/Kconfig"
 
 config NR_CPUS
 	int "Maximum number of CPUs (2-64)"

arch/ia64/kernel/efivars.c +0 ~~-442~~

442 lines not on this page · raw message

arch/ia64/kernel/Makefile +0 -1

diff -urN linux-2.6.0-test2-bk/arch/ia64/kernel/Makefile linux-2.6.0-test2-bk-efi/arch/ia64/kernel/Makefile
@@ -8,7 +8,6 @@
 	 irq_lsapic.o ivt.o machvec.o pal.o patch.o process.o perfmon.o ptrace.o sal.o		\
 	 semaphore.o setup.o signal.o sys_ia64.o time.o traps.o unaligned.o unwind.o
 
-obj-$(CONFIG_EFI_VARS)		+= efivars.o
 obj-$(CONFIG_IA64_BRL_EMU)	+= brl_emu.o
 obj-$(CONFIG_IA64_GENERIC)	+= acpi-ext.o
 obj-$(CONFIG_IA64_HP_ZX1)	+= acpi-ext.o

drivers/efi/efivars.c +442 -0

442 lines not on this page · raw message

drivers/efi/Kconfig +26 -0

diff -urN linux-2.6.0-test2-bk/drivers/efi/Kconfig linux-2.6.0-test2-bk-efi/drivers/efi/Kconfig
@@ -0,0 +1,26 @@
+#
+# EFI Configuration
+#
+
+menu "EFI Support"
+
+config EFI
+	bool "EFI Driver Support"
+	---help---
+	  EFI (Extensible Firmware Interface) support for Linux enables 
+	  the use of drivers that provide architecturally independent 
+	  functionality.  This support is applicable to architectures 
+	  that support EFI.  
+
+config EFI_VARS
+	tristate "/proc/efi/vars support"
+	depends on PROC_FS && EFI
+	---help---
+	  If you say Y here, you are able to get EFI (Extensible Firmware
+	  Interface) variable information in /proc/efi/vars.  You may read,
+	  write, create, and destroy EFI variables through this interface.
+
+ 	  To use this option, you have to check that the "/proc file system
+	  support (CONFIG_PROC_FS) is enabled, too.
+
+endmenu

drivers/efi/Makefile +3 -0

diff -urN linux-2.6.0-test2-bk/drivers/efi/Makefile linux-2.6.0-test2-bk-efi/drivers/efi/Makefile
@@ -0,0 +1,3 @@
+# EFI Variable Access
+obj-$(CONFIG_EFI_VARS)		+= efivars.o
+

drivers/Makefile +1 -0

diff -urN linux-2.6.0-test2-bk/drivers/Makefile linux-2.6.0-test2-bk-efi/drivers/Makefile
@@ -49,3 +49,4 @@
 obj-$(CONFIG_MCA)		+= mca/
 obj-$(CONFIG_EISA)		+= eisa/
 obj-$(CONFIG_CPU_FREQ)		+= cpufreq/
+obj-$(CONFIG_EFI)		+= efi/