vserver 1.9.5.x5

[linux-2.6.git] / drivers / firmware / Kconfig

diff --git a/drivers/firmware/Kconfig b/drivers/firmware/Kconfig
index f5a883e..5b29c3b 100644 (file)
--- a/drivers/firmware/Kconfig
+++ b/drivers/firmware/Kconfig
@@ -12,10 +12,11 @@ config EDD
        help
          Say Y or M here if you want to enable BIOS Enhanced Disk Drive
          Services real mode BIOS calls to determine which disk
-         BIOS tries boot from.  This information is then exported via driverfs.
+         BIOS tries boot from.  This information is then exported via sysfs.
 
-         This option is experimental, but believed to be safe,
-         and most disk controller BIOS vendors do not yet implement this feature.
+         This option is experimental and is known to fail to boot on some
+          obscure configurations. Most disk controller BIOS vendors do
+          not yet implement this feature.
 
 config EFI_VARS
        tristate "EFI Variable Support via sysfs"
@@ -29,9 +30,32 @@ config EFI_VARS
          Note that using this driver in concert with efibootmgr requires
          at least test release version 0.5.0-test3 or later, which is
          available from Matt Domsch's website located at:
-         http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz
+         <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
 
          Subsequent efibootmgr releases may be found at:
-         http://linux.dell.com/efibootmgr
+         <http://linux.dell.com/efibootmgr>
+
+config EFI_PCDP
+       bool "Console device selection via EFI PCDP or HCDP table"
+       depends on ACPI && EFI && IA64
+       default y if IA64
+       help
+         If your firmware supplies the PCDP table, and you want to
+         automatically use the primary console device it describes
+         as the Linux console, say Y here.
+
+         If your firmware supplies the HCDP table, and you want to
+         use the first serial port it describes as the Linux console,
+         say Y here.  If your EFI ConOut path contains only a UART
+         device, it will become the console automatically.  Otherwise,
+         you must specify the "console=hcdp" kernel boot argument.
+
+         Neither the PCDP nor the HCDP affects naming of serial devices,
+         so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
+         on how the driver discovers devices.
+
+         You must also enable the appropriate drivers (serial, VGA, etc.)
+
+         See <http://www.dig64.org/specifications/DIG64_HCDPv20_042804.pdf>
 
 endmenu