[PATCH] new kernel configuration 5/7

This adds the driver config files. (part 1)

2 files changed, 245 insertions, 0 deletions

diff --git a/drivers/message/fusion/Kconfig b/drivers/message/fusion/Kconfig
new file mode 100644
index 000000000000..e482a6b7ca9e
--- /dev/null
+++ b/drivers/message/fusion/Kconfig
@@ -0,0 +1,152 @@
+
+menu "Fusion MPT device support"
+
+config FUSION
+	tristate "Fusion MPT (base + ScsiHost) drivers"
+	depends on BLK_DEV_SD
+	---help---
+	  LSI Logic Fusion(TM) Message Passing Technology (MPT) device support
+	  provides high performance SCSI host initiator, and LAN [1] interface
+	  services to a host system.  The Fusion architecture is capable of
+	  duplexing these protocols on high-speed Fibre Channel
+	  (up to 2 GHz x 2 ports = 4 GHz) and parallel SCSI (up to Ultra-320)
+	  physical medium.
+
+	  [1] LAN is not supported on parallel SCSI medium.
+
+	  These drivers require a Fusion MPT compatible PCI adapter installed
+	  in the host system.  MPT adapters contain specialized I/O processors
+	  to handle I/O workload, and more importantly to offload this work
+	  from the host CPU(s).
+
+	  If you have Fusion MPT hardware and want to use it, you can say
+	  Y or M here to add MPT (base + ScsiHost) drivers.
+	  <Y> = build lib (fusion.o), and link [static] into the kernel [2]
+	  proper
+	  <M> = compiled as [dynamic] modules [3] named: (mptbase.o,
+	  mptscsih.o)
+
+	  [2] In order enable capability to boot the linux kernel
+	  natively from a Fusion MPT target device, you MUST
+	  answer Y here! (currently requires CONFIG_BLK_DEV_SD)
+	  [3] This support is also available as a module ( = code
+	  which can be inserted in and removed from the running
+	  kernel whenever you want).  If you want to compile as
+	  modules, say M here and read
+	  <file:Documentation/modules.txt>.
+
+	  If unsure, say N.
+
+	  If you say Y or M here you will get a choice of these
+	  additional protocol and support module options:         Module Name:
+	  <M>   Enhanced SCSI error reporting                     (isense.o)
+	  <M>   Fusion MPT misc device (ioctl) driver             (mptctl.o)
+	  <M>   Fusion MPT LAN driver                             (mptlan.o)
+
+	  ---
+	  Fusion MPT is trademark of LSI Logic Corporation, and its
+	  architecture is based on LSI Logic's Message Passing Interface (MPI)
+	  specification.
+
+config FUSION_BOOT
+	bool
+	depends on FUSION=y
+	default y
+
+config FUSION_MAX_SGE
+	int "Maximum number of scatter gather entries"
+	depends on FUSION
+	default "40"
+	help
+	  This option allows you to specify the maximum number of scatter-
+	  gather entries per I/O. The driver defaults to 40, a reasonable number
+	  for most systems. However, the user may increase this up to 128.
+	  Increasing this parameter will require significantly more memory 
+	  on a per controller instance. Increasing the parameter is not
+	  necessary (or recommended) unless the user will be running 
+	  large I/O's via the raw interface.
+
+#  How can we force these options to module or nothing?
+config FUSION_ISENSE
+	tristate "Enhanced SCSI error reporting"
+	depends on MODULES && FUSION && m
+	---help---
+	  The isense module (roughly stands for Interpret SENSE data) is
+	  completely optional.  It simply provides extra English readable
+	  strings in SCSI Error Report(s) that might be generated from the
+	  Fusion MPT SCSI Host driver, for example when a target device
+	  returns a SCSI check condition on a I/O.  Without this module
+	  loaded you might see:
+
+	  SCSI Error Report =-=-= (ioc0,scsi5:0)
+	  SCSI_Status=02h (CHECK_CONDITION)
+	  Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00
+	  SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
+	  SenseKey=2h (NOT READY); FRU=02h
+	  ASC/ASCQ=29h/00h
+
+	  Where otherwise, if this module had been loaded, you would see:
+
+	  SCSI Error Report =-=-= (ioc0,scsi5:0)
+	  SCSI_Status=02h (CHECK_CONDITION)
+	  Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00 - "WRITE(10)"
+	  SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
+	  SenseKey=2h (NOT READY); FRU=02h
+	  ASC/ASCQ=29h/00h "LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED"
+
+	  Say M for "Enhanced SCSI error reporting" to compile this optional module,
+	  creating a driver named: isense.o.
+
+	  NOTE: Support for building this feature into the kernel is not
+	  available, due to kernel size considerations.
+
+config FUSION_CTL
+	tristate "Fusion MPT misc device (ioctl) driver"
+	depends on MODULES && FUSION && m
+	---help---
+	  The Fusion MPT misc device driver provides specialized control
+	  of MPT adapters via system ioctl calls.  Use of ioctl calls to
+	  the MPT driver requires that you create and use a misc device
+	  node ala:
+	  mknod /dev/mptctl c 10 240
+
+	  One use of this ioctl interface is to perform an upgrade (reflash)
+	  of the MPT adapter firmware.  Refer to readme file(s) distributed
+	  with the Fusion MPT linux driver for additional details.
+
+	  If enabled by saying M to this, a driver named: mptctl.o
+	  will be compiled.
+
+	  If unsure whether you really want or need this, say N.
+
+config FUSION_LAN
+	tristate "Fusion MPT LAN driver"
+	depends on FUSION && NET_FC
+	---help---
+	  This module supports LAN IP traffic over Fibre Channel port(s)
+	  on Fusion MPT compatible hardware (LSIFC9xx chips).
+	  The physical interface used is defined in RFC 2625.
+	  Please refer to that document for details.
+
+	  Installing this driver requires the knowledge to configure and
+	  activate a new network interface, "fc0", using standard Linux tools.
+
+	  If enabled by saying M to this, a driver named: mptlan.o
+	  will be compiled.
+
+	  If unsure whether you really want or need this, say N.
+
+	  NOTES: This feature is NOT available nor supported for linux-2.2.x
+	  kernels.  You must be building a linux-2.3.x or linux-2.4.x kernel
+	  in order to configure this option.
+	  Support for building this feature into the linux kernel is not
+	  yet available.
+
+#  if [ "$CONFIG_FUSION_LAN" != "n" ]; then
+#    define_bool CONFIG_NET_FC y
+#  fi
+# These <should> be define_tristate, but we leave them define_bool
+# for backward compatibility with pre-linux-2.2.15 kernels.
+# (Bugzilla:fibrebugs, #384)
+endmenu
+
diff --git a/drivers/message/i2o/Kconfig b/drivers/message/i2o/Kconfig
new file mode 100644
index 000000000000..3b7a061de441
--- /dev/null
+++ b/drivers/message/i2o/Kconfig
@@ -0,0 +1,93 @@
+
+menu "I2O device support"
+
+config I2O
+	tristate "I2O support"
+	---help---
+	  The Intelligent Input/Output (I2O) architecture allows hardware
+	  drivers to be split into two parts: an operating system specific
+	  module called the OSM and an hardware specific module called the
+	  HDM. The OSM can talk to a whole range of HDM's, and ideally the
+	  HDM's are not OS dependent. This allows for the same HDM driver to
+	  be used under different operating systems if the relevant OSM is in
+	  place. In order for this to work, you need to have an I2O interface
+	  adapter card in your computer. This card contains a special I/O
+	  processor (IOP), thus allowing high speeds since the CPU does not
+	  have to deal with I/O.
+
+	  If you say Y here, you will get a choice of interface adapter
+	  drivers and OSM's with the following questions.
+
+	  This support is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.  You will get modules called
+	  i2o_core.o and i2o_config.o.
+
+	  If unsure, say N.
+
+config I2O_PCI
+	tristate "I2O PCI support"
+	depends on PCI && I2O
+	help
+	  Say Y for support of PCI bus I2O interface adapters. Currently this
+	  is the only variety supported, so you should say Y.
+
+	  This support is also available as a module called i2o_pci.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config I2O_BLOCK
+	tristate "I2O Block OSM"
+	depends on I2O
+	help
+	  Include support for the I2O Block OSM. The Block OSM presents disk
+	  and other structured block devices to the operating system.
+
+	  This support is also available as a module called i2o_block.o ( =
+	  code which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config I2O_LAN
+	tristate "I2O LAN OSM"
+	depends on NET && I2O
+	help
+	  Include support for the LAN OSM. You will also need to include
+	  support for token ring or FDDI if you wish to use token ring or FDDI
+	  I2O cards with this driver.
+
+	  This support is also available as a module called i2o_lan.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config I2O_SCSI
+	tristate "I2O SCSI OSM"
+	depends on I2O && SCSI
+	help
+	  Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
+	  I2O controller. You can use both the SCSI and Block OSM together if
+	  you wish.
+
+	  This support is also available as a module called i2o_scsi.o ( =
+	  code which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config I2O_PROC
+	tristate "I2O /proc support"
+	depends on I2O
+	help
+	  If you say Y here and to "/proc file system support", you will be
+	  able to read I2O related information from the virtual directory
+	  /proc/i2o.
+
+	  This support is also available as a module called i2o_proc.o ( =
+	  code which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+endmenu
+