sata & scsi suggestion for make menuconfig

sata & scsi suggestion for make menuconfig

[Folkert van Heusden]

Hi,

Maybe it is a nice enhancement for make menuconfig to more explicitly
give a pop-up or so when someone selects for example a sata controller
while no 'scsi-disk' support was selected?


Folkert van Heusden

-- 
Multi tail barnamaj mowahib li mora9abat attasjilat wa nataij awamir
al 7asoub. damj, talwin, mora9abat attarchi7 wa ila akhirih.
http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

Re: sata & scsi suggestion for make menuconfig

[Jan Engelhardt]

On Sep 7 2007 14:48, Folkert van Heusden wrote:
>
>Maybe it is a nice enhancement for make menuconfig to more explicitly
>give a pop-up or so when someone selects for example a sata controller
>while no 'scsi-disk' support was selected?

Having no sd support is perfectly valid. Imagine a diskless boot
with only sr support.

Re: sata & scsi suggestion for make menuconfig

[Folkert van Heusden]

> >Maybe it is a nice enhancement for make menuconfig to more explicitly
> >give a pop-up or so when someone selects for example a sata controller
> >while no 'scsi-disk' support was selected?
> 
> Having no sd support is perfectly valid. Imagine a diskless boot
> with only sr support.

Ok, but that's not the most common situaties. What I'm suggesting is a
warning or a please note popup. Not neccessarily an error or refusing to
continue thing.


Folkert van Heusden

-- 
www.vanheusden.com/multitail - win een vlaai van multivlaai! zorg
ervoor dat multitail opgenomen wordt in Fedora Core, AIX, Solaris of
HP/UX en win een vlaai naar keuze
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

Re: sata & scsi suggestion for make menuconfig

[Krzysztof Halasa]

Folkert van Heusden <folkert@vanheusden.com> writes:

> Ok, but that's not the most common situaties. What I'm suggesting is a
> warning or a please note popup. Not neccessarily an error or refusing to
> continue thing.

What IMHO makes sense is changing all references to SCSI CDROM,
SCSI DISK etc. to just CDROM, DISK, and changing SCSI (menu) to
something like MASS STORAGE.
-- 
Krzysztof Halasa

Re: sata & scsi suggestion for make menuconfig

[Jan Engelhardt]

On Sep 7 2007 21:38, Krzysztof Halasa wrote:
>> Ok, but that's not the most common situaties. What I'm suggesting is a
>> warning or a please note popup. Not neccessarily an error or refusing to
>> continue thing.
>
>What IMHO makes sense is changing all references to SCSI CDROM,
>SCSI DISK etc. to just CDROM, DISK, and changing SCSI (menu) to
>something like MASS STORAGE.

There is still too much SCSI in it IMO :-)

Re: sata & scsi suggestion for make menuconfig

[Jan Engelhardt]

On Sep 8 2007 01:02, Jan Engelhardt wrote:
>On Sep 7 2007 21:38, Krzysztof Halasa wrote:
>>> Ok, but that's not the most common situaties. What I'm suggesting is a
>>> warning or a please note popup. Not neccessarily an error or refusing to
>>> continue thing.
>>
>>What IMHO makes sense is changing all references to SCSI CDROM,
>>SCSI DISK etc. to just CDROM, DISK, and changing SCSI (menu) to
>>something like MASS STORAGE.
>
>There is still too much SCSI in it IMO :-)

And to explain that point: SCSI device name inquiry is limited to 16 bytes.
That may be a limitation of SCSI (as in: the protocol), but the SCSI
*subsystem* should not impose such a tight limit.


	Jan
-- 

Re: sata & scsi suggestion for make menuconfig

[Randy Dunlap]

On Fri, 7 Sep 2007 14:48:00 +0200 Folkert van Heusden wrote:

> Hi,
> 
> Maybe it is a nice enhancement for make menuconfig to more explicitly
> give a pop-up or so when someone selects for example a sata controller
> while no 'scsi-disk' support was selected?

I know that it's difficult to get people to read docs & help text,
and maybe it is needed in more places, but CONFIG_ATA (SATA/PATA)
help text says:

  NOTE: ATA enables basic SCSI support; *however*,
  'SCSI disk support', 'SCSI tape support', or
  'SCSI CDROM support' may also be needed,
  depending on your hardware configuration.


A popup makes some sense, but I don't know if menuconfig knows how to
do popup warnings... and it needs to be done for all *configs,
not just menuconfig.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

Re: sata & scsi suggestion for make menuconfig

[Folkert van Heusden]

> > Maybe it is a nice enhancement for make menuconfig to more explicitly
> > give a pop-up or so when someone selects for example a sata controller
> > while no 'scsi-disk' support was selected?
> 
> I know that it's difficult to get people to read docs & help text,
> and maybe it is needed in more places, but CONFIG_ATA (SATA/PATA)
> help text says:
>   NOTE: ATA enables basic SCSI support; *however*,
>   'SCSI disk support', 'SCSI tape support', or
>   'SCSI CDROM support' may also be needed,
>   depending on your hardware configuration.

Yes but that would mean that you have to open the help for each item
that you add.

> A popup makes some sense, but I don't know if menuconfig knows how to
> do popup warnings... and it needs to be done for all *configs,
> not just menuconfig.

Maybe add a new type?


Folkert van Heusden

-- 
MultiTail na wan makriki wrokosani fu tan luku den logfile nanga san
den commando spiti puru. Piki puru spesrutu sani, wroko nanga difreti
kroru, tja kon makandra, nanga wan lo moro.
http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

Folkert van Heusden wrote:
>> I know that it's difficult to get people to read docs & help text,
>> and maybe it is needed in more places, but CONFIG_ATA (SATA/PATA)
>> help text says:
>>   NOTE: ATA enables basic SCSI support; *however*,
>>   'SCSI disk support', 'SCSI tape support', or
>>   'SCSI CDROM support' may also be needed,
>>   depending on your hardware configuration.
> 
> Yes but that would mean that you have to open the help for each item
> that you add.
> 
>> A popup makes some sense, but I don't know if menuconfig knows how to
>> do popup warnings... and it needs to be done for all *configs,
>> not just menuconfig.
> 
> Maybe add a new type?

How about

comment "Note: 'SCSI disk support' is required for SATA/PATA HDDs!"
	depends on ATA && !BLK_DEV_SD

-- 
Stefan Richter
-=====-=-=== =--= --===
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Folkert van Heusden]

> >> I know that it's difficult to get people to read docs & help text,
> >> and maybe it is needed in more places, but CONFIG_ATA (SATA/PATA)
> >> help text says:
> >>   NOTE: ATA enables basic SCSI support; *however*,
> >>   'SCSI disk support', 'SCSI tape support', or
> >>   'SCSI CDROM support' may also be needed,
> >>   depending on your hardware configuration.
> > 
> > Yes but that would mean that you have to open the help for each item
> > that you add.
> > 
> >> A popup makes some sense, but I don't know if menuconfig knows how to
> >> do popup warnings... and it needs to be done for all *configs,
> >> not just menuconfig.
> > 
> > Maybe add a new type?
> 
> How about
> comment "Note: 'SCSI disk support' is required for SATA/PATA HDDs!"
> 	depends on ATA && !BLK_DEV_SD

Yes! Maybe create some status-line at the bottom of the screen in which
these hints scrollby. Like powertop does.


Folkert van Heusden

-- 
MultiTail är en flexibel redskap för att fälja logfilar, utför av
commandoer, filtrera, ge färg, sammanfoga, o.s.v. följa.
http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

(added Cc linux-ide)

Folkert van Heusden wrote:
>>>> A popup makes some sense, but I don't know if menuconfig knows how to
>>>> do popup warnings... and it needs to be done for all *configs,
>>>> not just menuconfig.
>>> Maybe add a new type?
>> How about
>> comment "Note: 'SCSI disk support' is required for SATA/PATA HDDs!"
>> 	depends on ATA && !BLK_DEV_SD
> 
> Yes! Maybe create some status-line at the bottom of the screen in which
> these hints scrollby. Like powertop does.

'comment' is already supported by make {menu,x,g}config and AFAIK by
make oldconfig too.  It is not effective in make oldconfig though
because it will scroll off the screen quickly.

I am not a friend of 'select', but maybe the following actually helps.
I didn't follow all of this and previous related discussions, so I guess
somebody else suggested something like this before:


# drivers/ata/Kconfig

config ATA
	[...]

comment "Controller drivers"

[...low-level drivers go here...]

comment "Storage device drivers"

config ATA_SD
	tristate "SATA/PATA HDD support (via SCSI disk support)"
	depends on ATA
	select BLK_DEV_SD
	help
	  'SCSI disk support' is required to access SATA HDDs.  It is
	  also necessary for parallel ATA (IDE) HDDs if you use the
	  experimental parallel ATA option.

	  You can say Y or M here to select SCSI disk support, or you
	  can do so in the 'SCSI device support' section.

[...ditto for CD/DVD-ROMs, tapes, and generic support...]
-- 
Stefan Richter
-=====-=-=== =--= -=---
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Jan Engelhardt]

On Sep 8 2007 09:05, Stefan Richter wrote:
>config ATA
>	[...]
>
>comment "Controller drivers"
>
>[...low-level drivers go here...]
>
>comment "Storage device drivers"
>
>config ATA_SD
>	tristate "SATA/PATA HDD support (via SCSI disk support)"
>	depends on ATA
>	select BLK_DEV_SD
>	help
>	  'SCSI disk support' is required to access SATA HDDs.  It is
>	  also necessary for parallel ATA (IDE) HDDs if you use the
>	  experimental parallel ATA option.
>
>	  You can say Y or M here to select SCSI disk support, or you
>	  can do so in the 'SCSI device support' section.
>
>[...ditto for CD/DVD-ROMs, tapes, and generic support...]

And what uses ATA_SD, or is the user supposed to manually enable it?



	Jan
-- 

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

Jan Engelhardt wrote:
> On Sep 8 2007 09:05, Stefan Richter wrote:
>> config ATA_SD
>> 	tristate "SATA/PATA HDD support (via SCSI disk support)"
>> 	depends on ATA
>> 	select BLK_DEV_SD
>> 	help
>> 	  'SCSI disk support' is required to access SATA HDDs.  It is
[...]
>>	  You can say Y or M here to select SCSI disk support, or you
>>	  can do so in the 'SCSI device support' section.
[...]
> And what uses ATA_SD, or is the user supposed to manually enable it?

It is merely there to produce the prompt which people asked for.
CONFIG_ATA_SD (or CONFIG_ATA_BLK_DEV_SD or whatever) won't turn up in
any Makefile or source code.

Note, I'm not fond of 'select' nor of dummy Kconfig variables.  Plus I
can personally live very well with the current solution (sd_mod et al
are mentioned in the help text at CONFIG_ATA).  That's why I posted only
the example instead of a complete patch.
-- 
Stefan Richter
-=====-=-=== =--= -=---
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Randy Dunlap]

Stefan Richter wrote:
> (added Cc linux-ide)
> 
> Folkert van Heusden wrote:
>>>>> A popup makes some sense, but I don't know if menuconfig knows how to
>>>>> do popup warnings... and it needs to be done for all *configs,
>>>>> not just menuconfig.
>>>> Maybe add a new type?
>>> How about
>>> comment "Note: 'SCSI disk support' is required for SATA/PATA HDDs!"
>>> 	depends on ATA && !BLK_DEV_SD
>> Yes! Maybe create some status-line at the bottom of the screen in which
>> these hints scrollby. Like powertop does.
> 
> 'comment' is already supported by make {menu,x,g}config and AFAIK by
> make oldconfig too.  It is not effective in make oldconfig though
> because it will scroll off the screen quickly.
> 
> I am not a friend of 'select', but maybe the following actually helps.
> I didn't follow all of this and previous related discussions, so I guess
> somebody else suggested something like this before:
> 

The problem with 'select' here is that it will enable BLK_DEV_SD,
but if SCSI is not enabled, it will not become enabled -- i.e.,
select does not follow the dependency chain.  So usually the
kernel will not build unless SCSI is enabled by the user.

> # drivers/ata/Kconfig
> 
> config ATA
> 	[...]
> 
> comment "Controller drivers"
> 
> [...low-level drivers go here...]
> 
> comment "Storage device drivers"
> 
> config ATA_SD
> 	tristate "SATA/PATA HDD support (via SCSI disk support)"
> 	depends on ATA
> 	select BLK_DEV_SD
> 	help
> 	  'SCSI disk support' is required to access SATA HDDs.  It is
> 	  also necessary for parallel ATA (IDE) HDDs if you use the
> 	  experimental parallel ATA option.
> 
> 	  You can say Y or M here to select SCSI disk support, or you
> 	  can do so in the 'SCSI device support' section.
> 
> [...ditto for CD/DVD-ROMs, tapes, and generic support...]


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

Randy Dunlap wrote:
> Stefan Richter wrote:
>> I am not a friend of 'select', but maybe the following actually helps.
...
> The problem with 'select' here is that it will enable BLK_DEV_SD,
> but if SCSI is not enabled, it will not become enabled -- i.e.,
> select does not follow the dependency chain.  So usually the
> kernel will not build unless SCSI is enabled by the user.
...
>> config ATA_SD
>>     tristate "SATA/PATA HDD support (via SCSI disk support)"
>>     depends on ATA
>>     select BLK_DEV_SD
>>     help
>>       'SCSI disk support' is required to access SATA HDDs.  It is
...

I checked the dependencies.  ATA depends on SCSI (actually, selects
SCSI), so all is well.  Otherwise I would have added more dependencies
to ATA_SD.
-- 
Stefan Richter
-=====-=-=== =--= -=---
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Randy Dunlap]

On Sat, 08 Sep 2007 18:44:46 +0200 Stefan Richter wrote:

> Randy Dunlap wrote:
> > Stefan Richter wrote:
> >> I am not a friend of 'select', but maybe the following actually helps.
> ...
> > The problem with 'select' here is that it will enable BLK_DEV_SD,
> > but if SCSI is not enabled, it will not become enabled -- i.e.,
> > select does not follow the dependency chain.  So usually the
> > kernel will not build unless SCSI is enabled by the user.
> ...
> >> config ATA_SD
> >>     tristate "SATA/PATA HDD support (via SCSI disk support)"
> >>     depends on ATA
> >>     select BLK_DEV_SD
> >>     help
> >>       'SCSI disk support' is required to access SATA HDDs.  It is
> ...
> 
> I checked the dependencies.  ATA depends on SCSI (actually, selects
> SCSI), so all is well.  Otherwise I would have added more dependencies
> to ATA_SD.

Ah, that's good, then.  Thanks.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

Randy Dunlap wrote:
> On Sat, 08 Sep 2007 18:44:46 +0200 Stefan Richter wrote:
>> Randy Dunlap wrote:
>>> The problem with 'select' here is that it will enable BLK_DEV_SD,
>>> but if SCSI is not enabled, it will not become enabled -- i.e.,
>>> select does not follow the dependency chain.  So usually the
>>> kernel will not build unless SCSI is enabled by the user.
...
>> I checked the dependencies.  ATA depends on SCSI (actually, selects
>> SCSI), so all is well.  Otherwise I would have added more dependencies
>> to ATA_SD.
> 
> Ah, that's good, then.

Not completely though.  Whenever a 'select' is inserted into the
dependency graph, the whole thing becomes more fragile WRT future changes.
-- 
Stefan Richter
-=====-=-=== =--= -=---
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Sam Ravnborg]

On Fri, Sep 07, 2007 at 08:35:22AM -0700, Randy Dunlap wrote:
> On Fri, 7 Sep 2007 14:48:00 +0200 Folkert van Heusden wrote:
> 
> > Hi,
> > 
> > Maybe it is a nice enhancement for make menuconfig to more explicitly
> > give a pop-up or so when someone selects for example a sata controller
> > while no 'scsi-disk' support was selected?
> 
> I know that it's difficult to get people to read docs & help text,
> and maybe it is needed in more places, but CONFIG_ATA (SATA/PATA)
> help text says:
> 
>   NOTE: ATA enables basic SCSI support; *however*,
>   'SCSI disk support', 'SCSI tape support', or
>   'SCSI CDROM support' may also be needed,
>   depending on your hardware configuration.
> 
> 
> A popup makes some sense, but I don't know if menuconfig knows how to
> do popup warnings... and it needs to be done for all *configs,
> not just menuconfig.
For menuconfig I would much rather see that it had an additional
window at the bottom displaying the help text for the active menu line.

Implementing support for a pop-up in the kconfig language seems to be a bit
off the purpose of the kconfig language.

	Sam

Re: sata & scsi suggestion for make menuconfig

[Helge Hafting]

Randy Dunlap wrote:
> On Fri, 7 Sep 2007 14:48:00 +0200 Folkert van Heusden wrote:
>
>   
>> Hi,
>>
>> Maybe it is a nice enhancement for make menuconfig to more explicitly
>> give a pop-up or so when someone selects for example a sata controller
>> while no 'scsi-disk' support was selected?
>>     
>
> I know that it's difficult to get people to read docs & help text,
> and maybe it is needed in more places, but CONFIG_ATA (SATA/PATA)
> help text says:
>
>   NOTE: ATA enables basic SCSI support; *however*,
>   'SCSI disk support', 'SCSI tape support', or
>   'SCSI CDROM support' may also be needed,
>   depending on your hardware configuration.
>
>
> A popup makes some sense, but I don't know if menuconfig knows how to
> do popup warnings... and it needs to be done for all *configs,
> not just menuconfig.
>   
A popup hardly ever makes sense - popups generally are a
bad user interface. The user will have to dismiss the popup -
every time - whether he needs the warning or not.

But feel free to print a warning somewhere, such as a
status line. The warning itself is useful, but not something
we will have to dismiss in order to go on with the job.

Helge Hafting

Re: sata & scsi suggestion for make menuconfig

[Goswin von Brederlow]

Helge Hafting <helge.hafting@aitel.hist.no> writes:

> Randy Dunlap wrote:
>> On Fri, 7 Sep 2007 14:48:00 +0200 Folkert van Heusden wrote:
>>
>>
>>> Hi,
>>>
>>> Maybe it is a nice enhancement for make menuconfig to more explicitly
>>> give a pop-up or so when someone selects for example a sata controller
>>> while no 'scsi-disk' support was selected?
>>>
>>
>> I know that it's difficult to get people to read docs & help text,
>> and maybe it is needed in more places, but CONFIG_ATA (SATA/PATA)
>> help text says:
>>
>>   NOTE: ATA enables basic SCSI support; *however*,
>>   'SCSI disk support', 'SCSI tape support', or
>>   'SCSI CDROM support' may also be needed,
>>   depending on your hardware configuration.

Could one duplicate the configure options for scsi disk/tape/cdrom at
that place? The text should then probably read SCSI/SATA disk support
in both places.

MfG
        Goswin

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

Goswin von Brederlow wrote:
> Helge Hafting <helge.hafting@aitel.hist.no> writes:
>> Randy Dunlap wrote:
>>>   NOTE: ATA enables basic SCSI support; *however*,
>>>   'SCSI disk support', 'SCSI tape support', or
>>>   'SCSI CDROM support' may also be needed,
>>>   depending on your hardware configuration.
> 
> Could one duplicate the configure options for scsi disk/tape/cdrom at
> that place?

Yes, e.g. like in http://lkml.org/lkml/2007/9/8/9.

> The text should then probably read SCSI/SATA disk support in both places.

Or rather than duplicating the menu items for the same options, split
the SCSI high-level options out into a top-level menu and adjust the
wording of the prompts.  http://lkml.org/lkml/2007/9/14/217

(top level)
menu "Storage (core and SCSI commands)"
	config SCSI
		tristate "Storage support (core and SCSI commands)"
	config BLK_DEV_SD
		tristate "Harddisks and other Direct access devices"
	config CHR_DEV_ST
		tristate "Tape drives"
	config CHR_DEV_OSST
		tristate "SCSI OnStream SC-x0 tape support"
	config BLK_DEV_SR
		tristate "CD-ROMs, DVD-ROMs"
	...

menu "Device Drivers"
	...
	menu "SCSI device support"
		config RAID_ATTRS
		config SCSI_TGT
		menu "SCSI Transports"
			...
		menuconfig SCSI_LOWLEVEL
			bool "SCSI low-level drivers"
			...

-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Andi Kleen]

Folkert van Heusden <folkert@vanheusden.com> writes:

> Hi,
> 
> Maybe it is a nice enhancement for make menuconfig to more explicitly
> give a pop-up or so when someone selects for example a sata controller
> while no 'scsi-disk' support was selected?

This has also bitten me one or two times. A reasonable way would
be to just select SD automatically for !EMBEDDED

Here's a patch:

-Andi

Select BLK_DEV_SD for all SCSI/libata drivers

This avoid a common user mistake.


Signed-off-by: Andi Kleen <ak@suse.de>

Index: linux-2.6.23-rc1-misc/drivers/ata/Kconfig
===================================================================
--- linux-2.6.23-rc1-misc.orig/drivers/ata/Kconfig
+++ linux-2.6.23-rc1-misc/drivers/ata/Kconfig
@@ -42,6 +42,7 @@ config ATA_ACPI
 
 config SATA_AHCI
 	tristate "AHCI SATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for AHCI Serial ATA.
@@ -50,6 +51,7 @@ config SATA_AHCI
 
 config SATA_SVW
 	tristate "ServerWorks Frodo / Apple K2 SATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for Broadcom/Serverworks/Apple K2
@@ -59,6 +61,7 @@ config SATA_SVW
 
 config ATA_PIIX
 	tristate "Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for ICH5/6/7/8 Serial ATA
@@ -69,6 +72,7 @@ config ATA_PIIX
 
 config SATA_MV
 	tristate "Marvell SATA support (HIGHLY EXPERIMENTAL)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the Marvell Serial ATA family.
@@ -78,6 +82,7 @@ config SATA_MV
 
 config SATA_NV
 	tristate "NVIDIA SATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for NVIDIA Serial ATA.
@@ -86,6 +91,7 @@ config SATA_NV
 
 config PDC_ADMA
 	tristate "Pacific Digital ADMA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for Pacific Digital ADMA controllers
@@ -94,6 +100,7 @@ config PDC_ADMA
 
 config SATA_QSTOR
 	tristate "Pacific Digital SATA QStor support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for Pacific Digital Serial ATA QStor.
@@ -102,6 +109,7 @@ config SATA_QSTOR
 
 config SATA_PROMISE
 	tristate "Promise SATA TX2/TX4 support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for Promise Serial ATA TX2/TX4.
@@ -110,6 +118,7 @@ config SATA_PROMISE
 
 config SATA_SX4
 	tristate "Promise SATA SX4 support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for Promise Serial ATA SX4.
@@ -118,6 +127,7 @@ config SATA_SX4
 
 config SATA_SIL
 	tristate "Silicon Image SATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for Silicon Image Serial ATA.
@@ -126,6 +136,7 @@ config SATA_SIL
 
 config SATA_SIL24
 	tristate "Silicon Image 3124/3132 SATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for Silicon Image 3124/3132 Serial ATA.
@@ -134,6 +145,7 @@ config SATA_SIL24
 
 config SATA_SIS
 	tristate "SiS 964/965/966/180 SATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	select PATA_SIS
 	help
@@ -145,6 +157,7 @@ config SATA_SIS
 
 config SATA_ULI
 	tristate "ULi Electronics SATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for ULi Electronics SATA.
@@ -153,6 +166,7 @@ config SATA_ULI
 
 config SATA_VIA
 	tristate "VIA SATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for VIA Serial ATA.
@@ -161,6 +175,7 @@ config SATA_VIA
 
 config SATA_VITESSE
 	tristate "VITESSE VSC-7174 / INTEL 31244 SATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for Vitesse VSC7174 and Intel 31244 Serial ATA.
@@ -169,12 +184,14 @@ config SATA_VITESSE
 
 config SATA_INIC162X
 	tristate "Initio 162x SATA support (HIGHLY EXPERIMENTAL)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for Initio 162x Serial ATA.
 
 config PATA_ALI
 	tristate "ALi PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the ALi ATA interfaces
@@ -184,6 +201,7 @@ config PATA_ALI
 
 config PATA_AMD
 	tristate "AMD/NVidia PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for the AMD and NVidia PATA
@@ -193,6 +211,7 @@ config PATA_AMD
 
 config PATA_ARTOP
 	tristate "ARTOP 6210/6260 PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for ARTOP PATA controllers.
@@ -201,6 +220,7 @@ config PATA_ARTOP
 
 config PATA_ATIIXP
 	tristate "ATI PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the ATI ATA interfaces
@@ -210,6 +230,7 @@ config PATA_ATIIXP
 
 config PATA_CMD640_PCI
 	tristate "CMD640 PCI PATA support (Very Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the CMD640 PCI IDE
@@ -220,6 +241,7 @@ config PATA_CMD640_PCI
 
 config PATA_CMD64X
 	tristate "CMD64x PATA support (Very Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI&& EXPERIMENTAL
 	help
 	  This option enables support for the CMD64x series chips
@@ -229,6 +251,7 @@ config PATA_CMD64X
 
 config PATA_CS5520
 	tristate "CS5510/5520 PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for the Cyrix 5510/5520
@@ -238,6 +261,7 @@ config PATA_CS5520
 
 config PATA_CS5530
 	tristate "CS5530 PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the Cyrix/NatSemi/AMD CS5530
@@ -247,6 +271,7 @@ config PATA_CS5530
 
 config PATA_CS5535
 	tristate "CS5535 PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && X86 && !X86_64 && EXPERIMENTAL
 	help
 	  This option enables support for the NatSemi/AMD CS5535
@@ -256,6 +281,7 @@ config PATA_CS5535
 
 config PATA_CYPRESS
 	tristate "Cypress CY82C693 PATA support (Very Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the Cypress/Contaq CY82C693
@@ -265,6 +291,7 @@ config PATA_CYPRESS
 
 config PATA_EFAR
 	tristate "EFAR SLC90E66 support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for the EFAR SLC90E66
@@ -274,6 +301,7 @@ config PATA_EFAR
 
 config ATA_GENERIC
 	tristate "Generic ATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for generic BIOS configured
@@ -283,6 +311,7 @@ config ATA_GENERIC
 
 config PATA_HPT366
 	tristate "HPT 366/368 PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the HPT 366 and 368
@@ -292,6 +321,7 @@ config PATA_HPT366
 
 config PATA_HPT37X
 	tristate "HPT 370/370A/371/372/374/302 PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the majority of the later HPT
@@ -301,6 +331,7 @@ config PATA_HPT37X
 
 config PATA_HPT3X2N
 	tristate "HPT 372N/302N PATA support (Very Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the N variant HPT PATA
@@ -310,6 +341,7 @@ config PATA_HPT3X2N
 
 config PATA_HPT3X3
 	tristate "HPT 343/363 PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for the HPT 343/363
@@ -327,6 +359,7 @@ config PATA_HPT3X3_DMA
 
 config PATA_ISAPNP
 	tristate "ISA Plug and Play PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on EXPERIMENTAL && ISAPNP
 	help
 	  This option enables support for ISA plug & play ATA
@@ -336,6 +369,7 @@ config PATA_ISAPNP
 
 config PATA_IT821X
 	tristate "IT8211/2 PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for the ITE 8211 and 8212
@@ -346,6 +380,7 @@ config PATA_IT821X
 
 config PATA_IT8213
 	tristate "IT8213 PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the ITE 821 PATA
@@ -355,6 +390,7 @@ config PATA_IT8213
 
 config PATA_JMICRON
 	tristate "JMicron PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  Enable support for the JMicron IDE controller, via the new
@@ -364,6 +400,7 @@ config PATA_JMICRON
 
 config PATA_LEGACY
 	tristate "Legacy ISA PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA && EXPERIMENTAL
 	help
 	  This option enables support for ISA/VLB bus legacy PATA
@@ -373,6 +410,7 @@ config PATA_LEGACY
 
 config PATA_TRIFLEX
 	tristate "Compaq Triflex PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  Enable support for the Compaq 'Triflex' IDE controller as found
@@ -382,6 +420,7 @@ config PATA_TRIFLEX
 
 config PATA_MARVELL
 	tristate "Marvell PATA support via legacy mode"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables limited support for the Marvell 88SE6145 ATA
@@ -391,6 +430,7 @@ config PATA_MARVELL
 
 config PATA_MPC52xx
 	tristate "Freescale MPC52xx SoC internal IDE"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PPC_MPC52xx
 	help
 	  This option enables support for integrated IDE controller
@@ -400,6 +440,7 @@ config PATA_MPC52xx
 
 config PATA_MPIIX
 	tristate "Intel PATA MPIIX support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for MPIIX PATA support.
@@ -408,6 +449,7 @@ config PATA_MPIIX
 
 config PATA_OLDPIIX
 	tristate "Intel PATA old PIIX support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for early PIIX PATA support.
@@ -416,6 +458,7 @@ config PATA_OLDPIIX
 
 config PATA_NETCELL
 	tristate "NETCELL Revolution RAID support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for the Netcell Revolution RAID
@@ -425,6 +468,7 @@ config PATA_NETCELL
 
 config PATA_NS87410
 	tristate "Nat Semi NS87410 PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the National Semiconductor
@@ -434,6 +478,7 @@ config PATA_NS87410
 
 config PATA_OPTI
 	tristate "OPTI621/6215 PATA support (Very Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables full PIO support for the early Opti ATA
@@ -443,6 +488,7 @@ config PATA_OPTI
 
 config PATA_OPTIDMA
 	tristate "OPTI FireStar PATA support (Very Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables DMA/PIO support for the later OPTi
@@ -462,6 +508,7 @@ config PATA_PCMCIA
 
 config PATA_PDC_OLD
 	tristate "Older Promise PATA controller support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the Promise 20246, 20262, 20263,
@@ -471,12 +518,14 @@ config PATA_PDC_OLD
 
 config PATA_QDI
 	tristate "QDI VLB PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA
 	help
 	  Support for QDI 6500 and 6580 PATA controllers on VESA local bus.
 
 config PATA_RADISYS
 	tristate "RADISYS 82600 PATA support (Very Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the RADISYS 82600
@@ -486,6 +535,7 @@ config PATA_RADISYS
 
 config PATA_RZ1000
 	tristate "PC Tech RZ1000 PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables basic support for the PC Tech RZ1000/1
@@ -495,6 +545,7 @@ config PATA_RZ1000
 
 config PATA_SC1200
 	tristate "SC1200 PATA support (Very Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for the NatSemi/AMD SC1200 SoC
@@ -504,6 +555,7 @@ config PATA_SC1200
 
 config PATA_SERVERWORKS
 	tristate "SERVERWORKS OSB4/CSB5/CSB6/HT1000 PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for the Serverworks OSB4/CSB5/CSB6 and
@@ -513,6 +565,7 @@ config PATA_SERVERWORKS
 
 config PATA_PDC2027X
 	tristate "Promise PATA 2027x support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for Promise PATA pdc20268 to pdc20277 host adapters.
@@ -521,6 +574,7 @@ config PATA_PDC2027X
 
 config PATA_SIL680
 	tristate "CMD / Silicon Image 680 PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for CMD / Silicon Image 680 PATA.
@@ -529,6 +583,7 @@ config PATA_SIL680
 
 config PATA_SIS
 	tristate "SiS PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && EXPERIMENTAL
 	help
 	  This option enables support for SiS PATA controllers
@@ -537,6 +592,7 @@ config PATA_SIS
 
 config PATA_VIA
 	tristate "VIA PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for the VIA PATA interfaces
@@ -546,6 +602,7 @@ config PATA_VIA
 
 config PATA_WINBOND
 	tristate "Winbond SL82C105 PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	help
 	  This option enables support for SL82C105 PATA devices found in the
@@ -555,6 +612,7 @@ config PATA_WINBOND
 
 config PATA_WINBOND_VLB
 	tristate "Winbond W83759A VLB PATA support (Experimental)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA && EXPERIMENTAL
 	help
 	  Support for the Winbond W83759A controller on Vesa Local Bus
@@ -562,6 +620,7 @@ config PATA_WINBOND_VLB
 
 config PATA_PLATFORM
 	tristate "Generic platform device PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on EMBEDDED || ARCH_RPC
 	help
 	  This option enables support for generic directly connected ATA
@@ -571,6 +630,7 @@ config PATA_PLATFORM
 
 config PATA_ICSIDE
 	tristate "Acorn ICS PATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ARM && ARCH_ACORN
 	help
 	  On Acorn systems, say Y here if you wish to use the ICS PATA
@@ -579,6 +639,7 @@ config PATA_ICSIDE
 
 config PATA_IXP4XX_CF
 	tristate "IXP4XX Compact Flash support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ARCH_IXP4XX
 	help
 	  This option enables support for a Compact Flash connected on
@@ -589,6 +650,7 @@ config PATA_IXP4XX_CF
 
 config PATA_SCC
 	tristate "Toshiba's Cell Reference Set IDE support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && PPC_CELLEB
 	help
 	  This option enables support for the built-in IDE controller on
Index: linux-2.6.23-rc1-misc/drivers/scsi/Kconfig
===================================================================
--- linux-2.6.23-rc1-misc.orig/drivers/scsi/Kconfig
+++ linux-2.6.23-rc1-misc/drivers/scsi/Kconfig
@@ -305,6 +305,7 @@ config ISCSI_TCP
 	select CRYPTO_MD5
 	select CRYPTO_CRC32C
 	select SCSI_ISCSI_ATTRS
+	select BLK_DEV_SD if !EMBEDDED
 	help
 	 The iSCSI Driver provides a host with the ability to access storage
 	 through an IP network. The driver uses the iSCSI protocol to transport
@@ -325,6 +326,7 @@ config ISCSI_TCP
 config SGIWD93_SCSI
 	tristate "SGI WD93C93 SCSI Driver"
 	depends on SGI_IP22 && SCSI
+	select BLK_DEV_SD if !EMBEDDED
   	help
 	  If you have a Western Digital WD93 SCSI controller on
 	  an SGI MIPS system, say Y.  Otherwise, say N.
@@ -332,16 +334,19 @@ config SGIWD93_SCSI
 config SCSI_DECNCR
 	tristate "DEC NCR53C94 Scsi Driver"
 	depends on MACH_DECSTATION && SCSI && TC
+	select BLK_DEV_SD if !EMBEDDED
 	help
 	  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
 	  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
 
 config SCSI_DECSII
 	tristate "DEC SII Scsi Driver"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on MACH_DECSTATION && SCSI && 32BIT
 
 config BLK_DEV_3W_XXXX_RAID
 	tristate "3ware 5/6/7/8xxx ATA-RAID support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	help
 	  3ware is the only hardware ATA-Raid product in Linux to date.
@@ -355,6 +360,7 @@ config BLK_DEV_3W_XXXX_RAID
 
 config SCSI_3W_9XXX
 	tristate "3ware 9xxx SATA-RAID support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	help
 	  This driver supports the 9000 series 3ware SATA-RAID cards.
@@ -366,6 +372,7 @@ config SCSI_3W_9XXX
 
 config SCSI_7000FASST
 	tristate "7000FASST SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA && SCSI && ISA_DMA_API
 	help
 	  This driver supports the Western Digital 7000 SCSI host adapter
@@ -377,6 +384,7 @@ config SCSI_7000FASST
 
 config SCSI_ACARD
 	tristate "ACARD SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	help
 	  This driver supports the ACARD SCSI host adapter.
@@ -387,6 +395,7 @@ config SCSI_ACARD
 config SCSI_AHA152X
 	tristate "Adaptec AHA152X/2825 support"
 	depends on ISA && SCSI && !64BIT
+	select BLK_DEV_SD if !EMBEDDED
 	select SCSI_SPI_ATTRS
 	---help---
 	  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
@@ -402,6 +411,7 @@ config SCSI_AHA152X
 
 config SCSI_AHA1542
 	tristate "Adaptec AHA1542 support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA && SCSI && ISA_DMA_API
 	---help---
 	  This is support for a SCSI host adapter.  It is explained in section
@@ -416,6 +426,7 @@ config SCSI_AHA1542
 
 config SCSI_AHA1740
 	tristate "Adaptec AHA1740 support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on EISA && SCSI
 	---help---
 	  This is support for a SCSI host adapter.  It is explained in section
@@ -429,6 +440,7 @@ config SCSI_AHA1740
 
 config SCSI_AACRAID
 	tristate "Adaptec AACRAID support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on SCSI && PCI
 	help
 	  This driver supports a variety of Dell, HP, Adaptec, IBM and
@@ -443,6 +455,7 @@ source "drivers/scsi/aic7xxx/Kconfig.aic
 
 config SCSI_AIC7XXX_OLD
 	tristate "Adaptec AIC7xxx support (old driver)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on (ISA || EISA || PCI ) && SCSI
 	help
 	  WARNING This driver is an older aic7xxx driver and is no longer
@@ -487,6 +500,7 @@ source "drivers/scsi/aic94xx/Kconfig"
 # All the I2O code and drivers do not seem to be 64bit safe.
 config SCSI_DPT_I2O
 	tristate "Adaptec I2O RAID support "
+	select BLK_DEV_SD if !EMBEDDED
 	depends on !64BIT && SCSI && PCI && VIRT_TO_BUS
 	help
 	  This driver supports all of Adaptec's I2O based RAID controllers as 
@@ -501,6 +515,7 @@ config SCSI_ADVANSYS
 	depends on SCSI
 	depends on ISA || EISA || PCI
 	depends on BROKEN || X86_32
+	select BLK_DEV_SD if !EMBEDDED
 	help
 	  This is a driver for all SCSI host adapters manufactured by
 	  AdvanSys. It is documented in the kernel source in
@@ -512,6 +527,7 @@ config SCSI_ADVANSYS
 config SCSI_IN2000
 	tristate "Always IN2000 SCSI support"
 	depends on ISA && SCSI
+	select BLK_DEV_SD if !EMBEDDED
 	help
 	  This is support for an ISA bus SCSI host adapter.  You'll find more
 	  information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
@@ -524,6 +540,7 @@ config SCSI_IN2000
 config SCSI_ARCMSR
 	tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
 	depends on PCI && SCSI
+	select BLK_DEV_SD if !EMBEDDED
 	help
 	  This driver supports all of ARECA's SATA RAID controller cards.
 	  This is an ARECA-maintained driver by Erich Chen.
@@ -540,6 +557,7 @@ source "drivers/scsi/megaraid/Kconfig.me
 config SCSI_HPTIOP
 	tristate "HighPoint RocketRAID 3xxx Controller support"
 	depends on SCSI && PCI
+	select BLK_DEV_SD if !EMBEDDED
 	help
 	  This option enables support for HighPoint RocketRAID 3xxx
 	  controllers.
@@ -549,6 +567,7 @@ config SCSI_HPTIOP
 
 config SCSI_BUSLOGIC
 	tristate "BusLogic SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
 	---help---
 	  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
@@ -563,6 +582,7 @@ config SCSI_BUSLOGIC
 config SCSI_OMIT_FLASHPOINT
 	bool "Omit FlashPoint support"
 	depends on SCSI_BUSLOGIC
+	select BLK_DEV_SD if !EMBEDDED
 	help
 	  This option allows you to omit the FlashPoint support from the
 	  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
@@ -573,6 +593,7 @@ config SCSI_DMX3191D
 	tristate "DMX3191D SCSI support"
 	depends on PCI && SCSI
 	select SCSI_SPI_ATTRS
+	select BLK_DEV_SD if !EMBEDDED
 	help
 	  This is support for Domex DMX3191D SCSI Host Adapters.
 
@@ -583,6 +604,7 @@ config SCSI_DTC3280
 	tristate "DTC3180/3280 SCSI support"
 	depends on ISA && SCSI
 	select SCSI_SPI_ATTRS
+	select BLK_DEV_SD if !EMBEDDED
 	help
 	  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
 	  the SCSI-HOWTO, available from
@@ -595,6 +617,7 @@ config SCSI_DTC3280
 config SCSI_EATA
 	tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
 	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
+	select BLK_DEV_SD if !EMBEDDED
 	---help---
 	  This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
 	  ISA and all EISA I/O addresses are probed looking for the "EATA"
@@ -656,6 +679,7 @@ config SCSI_EATA_PIO
 
 config SCSI_FUTURE_DOMAIN
 	tristate "Future Domain 16xx SCSI/AHA-2920A support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on (ISA || PCI) && SCSI
 	---help---
 	  This is support for Future Domain's 16-bit SCSI host adapters
@@ -675,6 +699,7 @@ config SCSI_FUTURE_DOMAIN
 
 config SCSI_FD_MCS
 	tristate "Future Domain MCS-600/700 SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on MCA_LEGACY && SCSI
 	---help---
 	  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
@@ -688,6 +713,7 @@ config SCSI_FD_MCS
 
 config SCSI_GDTH
 	tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
 	---help---
 	  Formerly called GDT SCSI Disk Array Controller Support.
@@ -702,6 +728,7 @@ config SCSI_GDTH
 
 config SCSI_GENERIC_NCR5380
 	tristate "Generic NCR5380/53c400 SCSI PIO support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA && SCSI
 	select SCSI_SPI_ATTRS
 	---help---
@@ -722,6 +749,7 @@ config SCSI_GENERIC_NCR5380
 
 config SCSI_GENERIC_NCR5380_MMIO
 	tristate "Generic NCR5380/53c400 SCSI MMIO support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA && SCSI
 	select SCSI_SPI_ATTRS
 	---help---
@@ -748,6 +776,7 @@ config SCSI_GENERIC_NCR53C400
 
 config SCSI_IBMMCA
 	tristate "IBMMCA SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on MCA && SCSI
 	---help---
 	  This is support for the IBM SCSI adapter found in many of the PS/2
@@ -818,6 +847,7 @@ config IBMMCA_SCSI_DEV_RESET
 
 config SCSI_IPS
 	tristate "IBM ServeRAID support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	---help---
 	  This is support for the IBM ServeRAID hardware RAID controllers.
@@ -831,6 +861,7 @@ config SCSI_IPS
 
 config SCSI_IBMVSCSI
 	tristate "IBM Virtual SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PPC_PSERIES || PPC_ISERIES
 	help
 	  This is the IBM POWER Virtual SCSI Client
@@ -840,6 +871,7 @@ config SCSI_IBMVSCSI
 
 config SCSI_IBMVSCSIS
 	tristate "IBM Virtual SCSI Server support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PPC_PSERIES && SCSI_TGT && SCSI_SRP
 	help
 	  This is the SRP target driver for IBM pSeries virtual environments.
@@ -854,6 +886,7 @@ config SCSI_IBMVSCSIS
 
 config SCSI_INITIO
 	tristate "Initio 9100U(W) support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	help
 	  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
@@ -865,6 +898,7 @@ config SCSI_INITIO
 
 config SCSI_INIA100
 	tristate "Initio INI-A100U2W support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	help
 	  This is support for the Initio INI-A100U2W SCSI host adapter.
@@ -876,6 +910,7 @@ config SCSI_INIA100
 
 config SCSI_PPA
 	tristate "IOMEGA parallel port (ppa - older drives)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on SCSI && PARPORT_PC
 	---help---
 	  This driver supports older versions of IOMEGA's parallel port ZIP
@@ -903,6 +938,7 @@ config SCSI_PPA
 
 config SCSI_IMM
 	tristate "IOMEGA parallel port (imm - newer drives)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on SCSI && PARPORT_PC
 	---help---
 	  This driver supports newer versions of IOMEGA's parallel port ZIP
@@ -959,6 +995,7 @@ config SCSI_IZIP_SLOW_CTR
 
 config SCSI_NCR53C406A
 	tristate "NCR53c406a SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA && SCSI
 	help
 	  This is support for the NCR53c406a SCSI host adapter.  For user
@@ -971,6 +1008,7 @@ config SCSI_NCR53C406A
 
 config SCSI_NCR_D700
 	tristate "NCR Dual 700 MCA SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on MCA && SCSI
 	select SCSI_SPI_ATTRS
 	help
@@ -983,6 +1021,7 @@ config SCSI_NCR_D700
 
 config SCSI_LASI700
 	tristate "HP Lasi SCSI support for 53c700/710"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on GSC && SCSI
 	select SCSI_SPI_ATTRS
 	help
@@ -992,6 +1031,7 @@ config SCSI_LASI700
 
 config SCSI_SNI_53C710
 	tristate "SNI RM SCSI support for 53c710"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on SNI_RM && SCSI
 	select SCSI_SPI_ATTRS
 	select 53C700_LE_ON_BE
@@ -1006,6 +1046,7 @@ config 53C700_LE_ON_BE
 
 config SCSI_STEX
 	tristate "Promise SuperTrak EX Series support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	---help---
 	  This driver supports Promise SuperTrak EX series storage controllers.
@@ -1023,6 +1064,7 @@ config 53C700_BE_BUS
 
 config SCSI_SYM53C8XX_2
 	tristate "SYM53C8XX Version 2 SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	select SCSI_SPI_ATTRS
 	---help---
@@ -1090,6 +1132,7 @@ config SCSI_SYM53C8XX_MMIO
 
 config SCSI_IPR
 	tristate "IBM Power Linux RAID adapter support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI && ATA
 	select FW_LOADER
 	---help---
@@ -1117,6 +1160,7 @@ config SCSI_IPR_DUMP
 
 config SCSI_ZALON
 	tristate "Zalon SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on GSC && SCSI
 	select SCSI_SPI_ATTRS
 	help
@@ -1128,6 +1172,7 @@ config SCSI_ZALON
 
 config SCSI_NCR_Q720
 	tristate "NCR Quad 720 MCA SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on MCA && SCSI
 	select SCSI_SPI_ATTRS
 	help
@@ -1227,6 +1272,7 @@ config SCSI_NCR53C8XX_NO_DISCONNECT
 
 config SCSI_MCA_53C9X
 	tristate "NCR MCA 53C9x SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
 	help
 	  Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
@@ -1238,6 +1284,7 @@ config SCSI_MCA_53C9X
 
 config SCSI_PAS16
 	tristate "PAS16 SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA && SCSI
 	select SCSI_SPI_ATTRS
 	---help---
@@ -1263,6 +1310,7 @@ config SCSI_PSI240I
 
 config SCSI_QLOGIC_FAS
 	tristate "Qlogic FAS SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA && SCSI
 	---help---
 	  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
@@ -1291,6 +1339,7 @@ config SCSI_QLOGIC_FC_FIRMWARE
 
 config SCSI_QLOGIC_1280
 	tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	help
 	  Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
@@ -1300,6 +1349,7 @@ config SCSI_QLOGIC_1280
 
 config SCSI_QLOGICPTI
 	tristate "PTI Qlogic, ISP Driver"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on SBUS && SCSI
 	help
 	  This driver supports SBUS SCSI controllers from PTI or QLogic. These
@@ -1315,6 +1365,7 @@ source "drivers/scsi/qla4xxx/Kconfig"
 
 config SCSI_LPFC
 	tristate "Emulex LightPulse Fibre Channel Support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	select SCSI_FC_ATTRS
 	help
@@ -1323,6 +1374,7 @@ config SCSI_LPFC
 
 config SCSI_SEAGATE
 	tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on X86 && ISA && SCSI
 	---help---
 	  These are 8-bit SCSI controllers; the ST-01 is also supported by
@@ -1337,6 +1389,7 @@ config SCSI_SEAGATE
 # definitely looks not 64bit safe:
 config SCSI_SIM710
 	tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on (EISA || MCA) && SCSI
 	select SCSI_SPI_ATTRS
 	---help---
@@ -1346,6 +1399,7 @@ config SCSI_SIM710
 
 config SCSI_SYM53C416
 	tristate "Symbios 53c416 SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA && SCSI
 	---help---
 	  This is support for the sym53c416 SCSI host adapter, the SCSI
@@ -1364,6 +1418,7 @@ config SCSI_SYM53C416
 
 config SCSI_DC395x
 	tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI && EXPERIMENTAL
 	---help---
 	  This driver supports PCI SCSI host adapters based on the ASIC
@@ -1379,6 +1434,7 @@ config SCSI_DC395x
 
 config SCSI_DC390T
 	tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	---help---
 	  This driver supports PCI SCSI host adapters based on the Am53C974A
@@ -1395,6 +1451,7 @@ config SCSI_DC390T
 
 config SCSI_T128
 	tristate "Trantor T128/T128F/T228 SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA && SCSI
 	select SCSI_SPI_ATTRS
 	---help---
@@ -1411,6 +1468,7 @@ config SCSI_T128
 
 config SCSI_U14_34F
 	tristate "UltraStor 14F/34F support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ISA && SCSI && ISA_DMA_API
 	---help---
 	  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
@@ -1460,6 +1518,7 @@ config SCSI_U14_34F_MAX_TAGS
 
 config SCSI_ULTRASTOR
 	tristate "UltraStor SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on X86 && ISA && SCSI
 	---help---
 	  This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
@@ -1477,6 +1536,7 @@ config SCSI_ULTRASTOR
 
 config SCSI_NSP32
 	tristate "Workbit NinjaSCSI-32Bi/UDE support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI && !64BIT
 	help
 	  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
@@ -1501,6 +1561,7 @@ config SCSI_DEBUG
 
 config SCSI_MESH
 	tristate "MESH (Power Mac internal SCSI) support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PPC32 && PPC_PMAC && SCSI
 	help
 	  Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
@@ -1555,6 +1616,7 @@ config JAZZ_ESP
 
 config A3000_SCSI
 	tristate "A3000 WD33C93A support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on AMIGA && SCSI
 	help
 	  If you have an Amiga 3000 and have SCSI devices connected to the
@@ -1565,6 +1627,7 @@ config A3000_SCSI
 
 config A2091_SCSI
 	tristate "A2091/A590 WD33C93A support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ZORRO && SCSI
 	help
 	  If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
@@ -1575,6 +1638,7 @@ config A2091_SCSI
 
 config GVP11_SCSI
 	tristate "GVP Series II WD33C93A support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ZORRO && SCSI
 	---help---
 	  If you have a Great Valley Products Series II SCSI controller,
@@ -1588,6 +1652,7 @@ config GVP11_SCSI
 
 config CYBERSTORM_SCSI
 	tristate "CyberStorm SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ZORRO && SCSI
 	help
 	  If you have an Amiga with an original (MkI) Phase5 Cyberstorm
@@ -1596,6 +1661,7 @@ config CYBERSTORM_SCSI
 
 config CYBERSTORMII_SCSI
 	tristate "CyberStorm Mk II SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ZORRO && SCSI
 	help
 	  If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
@@ -1604,6 +1670,7 @@ config CYBERSTORMII_SCSI
 
 config BLZ2060_SCSI
 	tristate "Blizzard 2060 SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ZORRO && SCSI
 	help
 	  If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
@@ -1612,6 +1679,7 @@ config BLZ2060_SCSI
 
 config BLZ1230_SCSI
 	tristate "Blizzard 1230IV/1260 SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ZORRO && SCSI
 	help
 	  If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
@@ -1620,6 +1688,7 @@ config BLZ1230_SCSI
 
 config FASTLANE_SCSI
 	tristate "Fastlane SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ZORRO && SCSI
 	help
 	  If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
@@ -1627,6 +1696,7 @@ config FASTLANE_SCSI
 
 config SCSI_A4000T
 	tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on AMIGA && SCSI && EXPERIMENTAL
 	select SCSI_SPI_ATTRS
 	help
@@ -1638,6 +1708,7 @@ config SCSI_A4000T
 
 config SCSI_ZORRO7XX
 	tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ZORRO && SCSI && EXPERIMENTAL
 	select SCSI_SPI_ATTRS
 	help
@@ -1654,6 +1725,7 @@ config SCSI_ZORRO7XX
 
 config OKTAGON_SCSI
 	tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ZORRO && SCSI && EXPERIMENTAL
 	help
 	  If you have the BSC Oktagon SCSI disk controller for the Amiga, say
@@ -1663,6 +1735,7 @@ config OKTAGON_SCSI
 
 config ATARI_SCSI
 	tristate "Atari native SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ATARI && SCSI
 	select SCSI_SPI_ATTRS
 	---help---
@@ -1715,6 +1788,7 @@ config MAC_SCSI
 
 config SCSI_MAC_ESP
 	tristate "Macintosh NCR53c9[46] SCSI"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on MAC && SCSI
 	help
 	  This is the NCR 53c9x SCSI controller found on most of the 68040
@@ -1735,6 +1809,7 @@ config MVME147_SCSI
 
 config MVME16x_SCSI
 	tristate "NCR53C710 SCSI driver for MVME16x"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on MVME16x && SCSI
 	select SCSI_SPI_ATTRS
 	help
@@ -1744,6 +1819,7 @@ config MVME16x_SCSI
 
 config BVME6000_SCSI
 	tristate "NCR53C710 SCSI driver for BVME6000"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on BVME6000 && SCSI
 	select SCSI_SPI_ATTRS
 	help
@@ -1753,6 +1829,7 @@ config BVME6000_SCSI
 
 config SUN3_SCSI
 	tristate "Sun3 NCR5380 SCSI"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on SUN3 && SCSI
 	select SCSI_SPI_ATTRS
 	help
@@ -1771,6 +1848,7 @@ config SUN3X_ESP
 
 config SCSI_SUNESP
 	tristate "Sparc ESP Scsi Driver"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on SBUS && SCSI
 	select SCSI_SPI_ATTRS
 	help
@@ -1782,6 +1860,7 @@ config SCSI_SUNESP
 
 config ZFCP
 	tristate "FCP host bus adapter driver for IBM eServer zSeries"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on S390 && QDIO && SCSI
 	select SCSI_FC_ATTRS
 	help
@@ -1796,6 +1875,7 @@ config ZFCP
 
 config SCSI_SRP
 	tristate "SCSI RDMA Protocol helper library"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on SCSI && PCI
 	select SCSI_TGT
 	help
Index: linux-2.6.23-rc1-misc/drivers/scsi/aic7xxx/Kconfig.aic79xx
===================================================================
--- linux-2.6.23-rc1-misc.orig/drivers/scsi/aic7xxx/Kconfig.aic79xx
+++ linux-2.6.23-rc1-misc/drivers/scsi/aic7xxx/Kconfig.aic79xx
@@ -4,6 +4,7 @@
 #
 config SCSI_AIC79XX
 	tristate "Adaptec AIC79xx U320 support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	select SCSI_SPI_ATTRS
 	help
Index: linux-2.6.23-rc1-misc/drivers/scsi/aic7xxx/Kconfig.aic7xxx
===================================================================
--- linux-2.6.23-rc1-misc.orig/drivers/scsi/aic7xxx/Kconfig.aic7xxx
+++ linux-2.6.23-rc1-misc/drivers/scsi/aic7xxx/Kconfig.aic7xxx
@@ -4,6 +4,7 @@
 #
 config SCSI_AIC7XXX
 	tristate "Adaptec AIC7xxx Fast -> U160 support (New Driver)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on (PCI || EISA) && SCSI
 	select SCSI_SPI_ATTRS
 	---help---
Index: linux-2.6.23-rc1-misc/drivers/scsi/aic94xx/Kconfig
===================================================================
--- linux-2.6.23-rc1-misc.orig/drivers/scsi/aic94xx/Kconfig
+++ linux-2.6.23-rc1-misc/drivers/scsi/aic94xx/Kconfig
@@ -26,6 +26,7 @@
 
 config SCSI_AIC94XX
 	tristate "Adaptec AIC94xx SAS/SATA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI
 	select SCSI_SAS_LIBSAS
 	select FW_LOADER
Index: linux-2.6.23-rc1-misc/drivers/scsi/arm/Kconfig
===================================================================
--- linux-2.6.23-rc1-misc.orig/drivers/scsi/arm/Kconfig
+++ linux-2.6.23-rc1-misc/drivers/scsi/arm/Kconfig
@@ -3,6 +3,7 @@
 #
 config SCSI_ACORNSCSI_3
 	tristate "Acorn SCSI card (aka30) support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ARCH_ACORN && SCSI && BROKEN
 	select SCSI_SPI_ATTRS
 	help
@@ -32,6 +33,7 @@ config SCSI_ACORNSCSI_SYNC
 
 config SCSI_ARXESCSI
 	tristate "ARXE SCSI support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ARCH_ACORN && SCSI
 	help
 	  Around 1991, Arxe Systems Limited released a high density floppy
@@ -44,6 +46,7 @@ config SCSI_ARXESCSI
 
 config SCSI_CUMANA_2
 	tristate "CumanaSCSI II support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ARCH_ACORN && SCSI
 	help
 	  This enables support for the Cumana SCSI II card. If you have an
@@ -51,6 +54,7 @@ config SCSI_CUMANA_2
 
 config SCSI_EESOXSCSI
 	tristate "EESOX support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ARCH_ACORN && SCSI
 	help
 	  This enables support for the EESOX SCSI card. If you have an Acorn
@@ -58,6 +62,7 @@ config SCSI_EESOXSCSI
 
 config SCSI_POWERTECSCSI
 	tristate "PowerTec support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ARCH_ACORN && SCSI
 	help
 	  This enables support for the Powertec SCSI card on Acorn systems. If
@@ -68,6 +73,7 @@ comment "The following drivers are not f
 
 config SCSI_CUMANA_1
 	tristate "CumanaSCSI I support (EXPERIMENTAL)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ARCH_ACORN && EXPERIMENTAL && SCSI
 	select SCSI_SPI_ATTRS
 	help
@@ -76,6 +82,7 @@ config SCSI_CUMANA_1
 
 config SCSI_ECOSCSI
 	tristate "EcoScsi support (EXPERIMENTAL)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on ARCH_ACORN && EXPERIMENTAL && (ARCH_ARC || ARCH_A5K) && SCSI
 	select SCSI_SPI_ATTRS
 	help
Index: linux-2.6.23-rc1-misc/drivers/scsi/megaraid/Kconfig.megaraid
===================================================================
--- linux-2.6.23-rc1-misc.orig/drivers/scsi/megaraid/Kconfig.megaraid
+++ linux-2.6.23-rc1-misc/drivers/scsi/megaraid/Kconfig.megaraid
@@ -6,6 +6,7 @@ config MEGARAID_NEWGEN
 
 config MEGARAID_MM
 	tristate "LSI Logic Management Module (New Driver)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI && MEGARAID_NEWGEN
 	help
 	Management Module provides ioctl, sysfs support for LSI Logic
@@ -16,6 +17,7 @@ config MEGARAID_MM
 
 config MEGARAID_MAILBOX
 	tristate "LSI Logic MegaRAID Driver (New Driver)"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI && MEGARAID_MM
 	help
 	List of supported controllers
@@ -77,6 +79,7 @@ config MEGARAID_LEGACY
 
 config MEGARAID_SAS
 	tristate "LSI Logic MegaRAID SAS RAID Module"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	help
 	Module for LSI Logic's SAS based RAID controllers.
Index: linux-2.6.23-rc1-misc/drivers/scsi/pcmcia/Kconfig
===================================================================
--- linux-2.6.23-rc1-misc.orig/drivers/scsi/pcmcia/Kconfig
+++ linux-2.6.23-rc1-misc/drivers/scsi/pcmcia/Kconfig
@@ -10,6 +10,7 @@ if SCSI_LOWLEVEL_PCMCIA && SCSI && PCMCI
 
 config PCMCIA_AHA152X
 	tristate "Adaptec AHA152X PCMCIA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on !64BIT
 	select SCSI_SPI_ATTRS
 	help
@@ -21,6 +22,7 @@ config PCMCIA_AHA152X
 
 config PCMCIA_FDOMAIN
 	tristate "Future Domain PCMCIA support"
+	select BLK_DEV_SD if !EMBEDDED
 	help
 	  Say Y here if you intend to attach this type of PCMCIA SCSI host
 	  adapter to your computer.
@@ -30,6 +32,7 @@ config PCMCIA_FDOMAIN
 
 config PCMCIA_NINJA_SCSI
 	tristate "NinjaSCSI-3 / NinjaSCSI-32Bi (16bit) PCMCIA support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on !64BIT
 	help
 	  If you intend to attach this type of PCMCIA SCSI host adapter to
@@ -64,6 +67,7 @@ config PCMCIA_NINJA_SCSI
 
 config PCMCIA_QLOGIC
 	tristate "Qlogic PCMCIA support"
+	select BLK_DEV_SD if !EMBEDDED
 	help
 	  Say Y here if you intend to attach this type of PCMCIA SCSI host
 	  adapter to your computer.
@@ -73,6 +77,7 @@ config PCMCIA_QLOGIC
 
 config PCMCIA_SYM53C500
 	tristate "Symbios 53c500 PCMCIA support"
+	select BLK_DEV_SD if !EMBEDDED
 	help
 	  Say Y here if you have a New Media Bus Toaster or other PCMCIA
 	  SCSI adapter based on the Symbios 53c500 controller.
Index: linux-2.6.23-rc1-misc/drivers/scsi/qla2xxx/Kconfig
===================================================================
--- linux-2.6.23-rc1-misc.orig/drivers/scsi/qla2xxx/Kconfig
+++ linux-2.6.23-rc1-misc/drivers/scsi/qla2xxx/Kconfig
@@ -1,5 +1,6 @@
 config SCSI_QLA_FC
 	tristate "QLogic QLA2XXX Fibre Channel Support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI
 	select SCSI_FC_ATTRS
 	select FW_LOADER
Index: linux-2.6.23-rc1-misc/drivers/scsi/qla4xxx/Kconfig
===================================================================
--- linux-2.6.23-rc1-misc.orig/drivers/scsi/qla4xxx/Kconfig
+++ linux-2.6.23-rc1-misc/drivers/scsi/qla4xxx/Kconfig
@@ -1,5 +1,6 @@
 config SCSI_QLA_ISCSI
 	tristate "QLogic ISP4XXX host adapter family support"
+	select BLK_DEV_SD if !EMBEDDED
 	depends on PCI && SCSI && NET
 	select SCSI_ISCSI_ATTRS
 	---help---

Re: sata & scsi suggestion for make menuconfig

[Randy Dunlap]

On 08 Sep 2007 18:07:00 +0200 Andi Kleen wrote:

> Folkert van Heusden <folkert@vanheusden.com> writes:
> 
> > Hi,
> > 
> > Maybe it is a nice enhancement for make menuconfig to more explicitly
> > give a pop-up or so when someone selects for example a sata controller
> > while no 'scsi-disk' support was selected?
> 
> This has also bitten me one or two times. A reasonable way would
> be to just select SD automatically for !EMBEDDED
> 
> Here's a patch:
> 
> -Andi
> 
> Select BLK_DEV_SD for all SCSI/libata drivers
> 
> This avoid a common user mistake.

I'd say that someone needs to use a vendor kernel, or at least
begin with a vendor .config file...


> Signed-off-by: Andi Kleen <ak@suse.de>

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

Re: sata & scsi suggestion for make menuconfig

[Matthew Wilcox]

On Sat, Sep 08, 2007 at 09:50:08AM -0700, Randy Dunlap wrote:
> On 08 Sep 2007 18:07:00 +0200 Andi Kleen wrote:
> > This has also bitten me one or two times. A reasonable way would
> > be to just select SD automatically for !EMBEDDED
> 
> I'd say that someone needs to use a vendor kernel, or at least
> begin with a vendor .config file...

That's not entirely fair ... if you're switching over from a config
you've been dragging around for years which uses IDE rather than ATA,
it's far from obvious which config options you need to change.  I think
Andi's patch is a good one.  It might also be good to select SR (at
least my wife's laptop has the cd-rom on SATA).

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

Re: sata & scsi suggestion for make menuconfig

[Andi Kleen]

> I'd say that someone needs to use a vendor kernel, or at least
> begin with a vendor .config file...

Vendor kernels tend to compile forever and require initrds. For 
just testing a kernel quickly compiling only a few drivers in
is much more convenient.

Also when you've been using CONFIG_IDE before it is not completely
obvious you need BLK_SD for your hard disk.

-Andi

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

Andi Kleen wrote:
> when you've been using CONFIG_IDE before it is not completely
> obvious you need BLK_SD for your hard disk.

Switching to different drivers without reading the help text?
Tough.
-- 
Stefan Richter
-=====-=-=== =--= -=---
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Andi Kleen]

On Sat, Sep 08, 2007 at 08:30:06PM +0200, Stefan Richter wrote:
> Andi Kleen wrote:
> > when you've been using CONFIG_IDE before it is not completely
> > obvious you need BLK_SD for your hard disk.
> 
> Switching to different drivers without reading the help text?
> Tough.

The individual driver descriptions don't say BLK_SD needs to be selected.

Besides if all descriptions said that the computer could as well
do it for the user automatically. After all it's a stupid repetive
task and computers are much better at those than humans.

-Andi

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

Andi Kleen wrote:
> On Sat, Sep 08, 2007 at 08:30:06PM +0200, Stefan Richter wrote:
>> Andi Kleen wrote:
>>> when you've been using CONFIG_IDE before it is not completely
>>> obvious you need BLK_SD for your hard disk.
>> Switching to different drivers without reading the help text?
>> Tough.
> 
> The individual driver descriptions don't say BLK_SD needs to be selected.

At least the help to CONFIG_ATA says so.

> Besides if all descriptions said that

We certainly don't want (too much) redundancy in help texts.

> the computer could as well
> do it for the user automatically. After all it's a stupid repetive
> task and computers are much better at those than humans.

In your patch, it is not the computer who finds out that the user wants
BLK_SD.  It is you who predetermined that the user wants it.
-- 
Stefan Richter
-=====-=-=== =--= -=---
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[James Bottomley]

On Sat, 2007-09-08 at 18:07 +0200, Andi Kleen wrote:
> Folkert van Heusden <folkert@vanheusden.com> writes:
> 
> > Hi,
> > 
> > Maybe it is a nice enhancement for make menuconfig to more explicitly
> > give a pop-up or so when someone selects for example a sata controller
> > while no 'scsi-disk' support was selected?
> 
> This has also bitten me one or two times. A reasonable way would
> be to just select SD automatically for !EMBEDDED
> 
> Here's a patch:
> 
> -Andi
> 
> Select BLK_DEV_SD for all SCSI/libata drivers
> 
> This avoid a common user mistake.

I can see where you're coming from, but logically, this is wrong.
There's a huge slew of enterprise machines that only have DVD on SATA.
On the other hand, all of these machines will have SCSI disk devices on
various other transports, so no harm is done, it's just an inelegant
solution.

James

Re: sata & scsi suggestion for make menuconfig

[Andi Kleen]

> I can see where you're coming from, but logically, this is wrong.
> There's a huge slew of enterprise machines that only have DVD on SATA.

... and enterprise systems don't really care about a few KB more of code.
In fact you definitely want to have SATA compiled in in case you need
to recover the machine later when the SAN is down.

> On the other hand, all of these machines will have SCSI disk devices on
> various other transports, so no harm is done, it's just an inelegant
> solution.

Do you know of a better one?

-Andi

Re: sata & scsi suggestion for make menuconfig

[Jeff Garzik]

Andi Kleen wrote:
>> I can see where you're coming from, but logically, this is wrong.
>> There's a huge slew of enterprise machines that only have DVD on SATA.
> 
> ... and enterprise systems don't really care about a few KB more of code.
> In fact you definitely want to have SATA compiled in in case you need
> to recover the machine later when the SAN is down.
> 
>> On the other hand, all of these machines will have SCSI disk devices on
>> various other transports, so no harm is done, it's just an inelegant
>> solution.
> 
> Do you know of a better one?

Let's step back a moment and consider the actual scale and impact of the 
problem at hand.

The vast majority of users are consumers of pre-compiled kernels, built 
by People With Clue(tm), who figured this stuff out as soon as it was 
introduced.

The current setup expresses the dependencies as they exist -- OPTIONAL 
extras, and that is a problem once a year or so, when someone builds 
their own kernel but must learn this fact anew.

There is simply no compelling need at all to change things from the 
current setup.

Our Kconfig system is for people who already know the kernel, not Aunt 
Tillie.

	Jeff

Re: sata & scsi suggestion for make menuconfig

[Andi Kleen]

> The current setup expresses the dependencies as they exist -- OPTIONAL 
> extras, and that is a problem once a year or so, when someone builds 

Disk support over SCSI/SATA is hardly an "optional extra". It's more the 99+%
case.

> their own kernel but must learn this fact anew.

When it costs 10000 people half an hour to learn and correct this it 
wasted 5000 hours of previous livetime.

Besides there is no good reason to have ever learned this imho.

-Andi

Re: sata & scsi suggestion for make menuconfig

[James Bottomley]

On Sun, 2007-09-09 at 23:22 +0200, Andi Kleen wrote:
> > The current setup expresses the dependencies as they exist -- OPTIONAL 
> > extras, and that is a problem once a year or so, when someone builds 
> 
> Disk support over SCSI/SATA is hardly an "optional extra". It's more the 99+%
> case.

Using that argument, there's an equal case for always requiring SCSI to
be built for every kernel, since very few people can boot a system
without a disk.  However, the 1% case is the embedded flash booting
community plus a few others, so we allow SCSI to be optional for our 1%
who don't want it.

At base, the Kconfig system is designed to give the greatest flexibility
with the fewest foot shooting opportunities.  However, we do tend to err
on the side of flexibility if there's a conflict between the two design
goals.

> > their own kernel but must learn this fact anew.
> 
> When it costs 10000 people half an hour to learn and correct this it 
> wasted 5000 hours of previous livetime.
>
> Besides there is no good reason to have ever learned this imho.

The process of becoming an expert in the kernel build system naturally
involves making mistakes and learning from them, so this is probably
time reasonably well spent.

James

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

James Bottomley wrote:
> On Sun, 2007-09-09 at 23:22 +0200, Andi Kleen wrote:
>> When it costs 10000 people half an hour to learn and correct this it 
>> wasted 5000 hours of previous livetime.
>>
>> Besides there is no good reason to have ever learned this imho.
> 
> The process of becoming an expert in the kernel build system naturally
> involves making mistakes and learning from them, so this is probably
> time reasonably well spent.

Nevertheless we should try to arrange the menus in a way that makes
sense to as many people as possible.  The difficulty is, different
environments call for different menu layouts, as your previous example
of SATA DVD-only boxes demonstrates.

However, liberal usage of 'select' is not the ultimate solution to
create menus that work for more people.  Just one problem with select is
that it works behind the back of the people configuring kernels (unless
they use an UI with debug options turned on) --- they have less control,
they are less informed.  ATA already 'select's SCSI.  What do we gain
from hiding the fact that Linux' SCSI option is not just for those
50-wire ribbons (which people still think SCSI stands for) but is a very
central Linux subsystem for even more than what complies to the SCSI
family of standards?

'select' should really be limited to switch on small library-like code
without further dependencies or requirements.  SCSI, together with its
upper layer options, is not of this kind of library.

We should think about order and grouping of prompts and the labels of
prompts (there were already suggestions in this discussion) before we
resort to 'select' --- or even worse, select options unconditionally
which are not always necessary to be enabled.

A pro pos grouping of options --- consider how options for another
central subsystem are laid out:

	Networking
		Networking options
			...
			TCP/IP networking
			...
		...

	Device Drivers
		...
		Network device support
			...
			Ethernet (10 or 100MBit)
			...
		...

This also happens to reflect the layout of sources in directories, and
the current SCSI menu layout is close to source layout too --- but it
doesn't have to be that way.
-- 
Stefan Richter
-=====-=-=== =--= -=-=-
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Rene Herman]

On 09/10/2007 08:38 AM, Stefan Richter wrote:

> Nevertheless we should try to arrange the menus in a way that makes
> sense to as many people as possible.  The difficulty is, different
> environments call for different menu layouts, as your previous example
> of SATA DVD-only boxes demonstrates.
> 
> However, liberal usage of 'select' is not the ultimate solution to
> create menus that work for more people.  Just one problem with select is
> that it works behind the back of the people configuring kernels (unless
> they use an UI with debug options turned on) --- they have less control,
> they are less informed.  ATA already 'select's SCSI.  What do we gain
> from hiding the fact that Linux' SCSI option is not just for those
> 50-wire ribbons (which people still think SCSI stands for) but is a very
> central Linux subsystem for even more than what complies to the SCSI
> family of standards?
> 
> 'select' should really be limited to switch on small library-like code
> without further dependencies or requirements.  SCSI, together with its
> upper layer options, is not of this kind of library.
> 
> We should think about order and grouping of prompts and the labels of
> prompts (there were already suggestions in this discussion) before we
> resort to 'select' --- or even worse, select options unconditionally
> which are not always necessary to be enabled.
> 
> A pro pos grouping of options --- consider how options for another
> central subsystem are laid out:
> 
> 	Networking
> 		Networking options
> 			...
> 			TCP/IP networking
> 			...
> 		...
> 
> 	Device Drivers
> 		...
> 		Network device support
> 			...
> 			Ethernet (10 or 100MBit)
> 			...
> 		...
> 
> This also happens to reflect the layout of sources in directories, and
> the current SCSI menu layout is close to source layout too --- but it
> doesn't have to be that way.

If someone's keen on really restructuring these things -- in this analogy:

Storage
	Storage Options
		...
		Disk
		Optical
		...
	...

Device Drivers
	...
	Storage Support
		...
		IDE
		PATA
		SATA
		SCSI
		USB
		FW
		...
	...

(sound is an example where both in the menus and the tree everything is kept 
under one top-level sound/ directory, not sound/ and drivers/sound/ as for 
networking -- opinions may vary which one's better I guess).

This is just config menus -- on a source code level, it would also make 
sense at least at some point to introduce "storage/" alongside net/ and 
sound/ and move things around I guess.

Rene.

Re: sata & scsi suggestion for make menuconfig

[Bauke Jan Douma]

Andi Kleen wrote on 09-09-07 23:22:

> 
> When it costs 10000 people half an hour to learn and correct this it 
> wasted 5000 hours of previous livetime.
          ^^^^^            ^       ^

Poor me. Here I am -- still waiting for my 15 minutes of fame in /this/ life...

;-)

bjd

Re: sata & scsi suggestion for make menuconfig

[Adrian Bunk]

On Sun, Sep 09, 2007 at 05:11:44PM -0400, Jeff Garzik wrote:
> Andi Kleen wrote:
>>> I can see where you're coming from, but logically, this is wrong.
>>> There's a huge slew of enterprise machines that only have DVD on SATA.
>> ... and enterprise systems don't really care about a few KB more of code.
>> In fact you definitely want to have SATA compiled in in case you need
>> to recover the machine later when the SAN is down.
>>> On the other hand, all of these machines will have SCSI disk devices on
>>> various other transports, so no harm is done, it's just an inelegant
>>> solution.
>> Do you know of a better one?
>
> Let's step back a moment and consider the actual scale and impact of the 
> problem at hand.
>
> The vast majority of users are consumers of pre-compiled kernels, built by 
> People With Clue(tm), who figured this stuff out as soon as it was 
> introduced.

We are talking about a patch to kconfig, and the users using 
pre-compiled kernels are not kconfig users.

> The current setup expresses the dependencies as they exist -- OPTIONAL 
> extras, and that is a problem once a year or so, when someone builds their 
> own kernel but must learn this fact anew.
>
> There is simply no compelling need at all to change things from the current 
> setup.
>
> Our Kconfig system is for people who already know the kernel, not Aunt 
> Tillie.

Couldn't we just remove kconfig and assume that all "people who already 
know the kernel" anyway prefer to edit their .config using vi?  ;-)

In my experience, the vast majority of kconfig users are not the few 
people working on distribution kernels, most of the kconfig userbase 
could be better described by the use case "sysadmin who knows about the 
hardware in his machine and which filesystems he uses".

And there must have been a reason why a leading kernel developer has 
written a complete book covering only configuration and building of the
kernel - the target audience of this book are most likely not "people 
who already know the kernel".

> 	Jeff

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

Adrian Bunk wrote:
> On Sun, Sep 09, 2007 at 05:11:44PM -0400, Jeff Garzik wrote:
>> Let's step back a moment and consider the actual scale and impact of the 
>> problem at hand.
>>
>> The vast majority of users are consumers of pre-compiled kernels, built by 
>> People With Clue(tm), who figured this stuff out as soon as it was 
>> introduced.
[...]
> In my experience, the vast majority of kconfig users are not the few 
> people working on distribution kernels, most of the kconfig userbase 
> could be better described by the use case "sysadmin who knows about the 
> hardware in his machine and which filesystems he uses".

The patch which is discussed here is specifically targeted towards users
who are convinced that they can migrate to different drivers without
reading Kconfig help texts.
-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Adrian Bunk]

On Fri, Sep 14, 2007 at 04:54:07PM +0200, Stefan Richter wrote:
> Adrian Bunk wrote:
> > On Sun, Sep 09, 2007 at 05:11:44PM -0400, Jeff Garzik wrote:
> >> Let's step back a moment and consider the actual scale and impact of the 
> >> problem at hand.
> >>
> >> The vast majority of users are consumers of pre-compiled kernels, built by 
> >> People With Clue(tm), who figured this stuff out as soon as it was 
> >> introduced.
> [...]
> > In my experience, the vast majority of kconfig users are not the few 
> > people working on distribution kernels, most of the kconfig userbase 
> > could be better described by the use case "sysadmin who knows about the 
> > hardware in his machine and which filesystems he uses".
> 
> The patch which is discussed here is specifically targeted towards users
> who are convinced that they can migrate to different drivers without
> reading Kconfig help texts.

Nothing about the patch is only about migration.

The same applies if you configure a kernel from scratch.

Do "make menuconfig" with the .config you are normally using, count the 
number of options that are visible, and ask yourself whether we can 
really expect users to read the help texts for every single option shown.

People mostly read help texts for options where they don't understand 
what this option is about - and "Serial ATA" therefore is an option that 
is likely to get enabled without the user looking at the help text.

> Stefan Richter

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

Adrian Bunk wrote:
> On Fri, Sep 14, 2007 at 04:54:07PM +0200, Stefan Richter wrote:
>> The patch which is discussed here is specifically targeted towards users
>> who are convinced that they can migrate to different drivers without
>> reading Kconfig help texts.
> 
> Nothing about the patch is only about migration.
> 
> The same applies if you configure a kernel from scratch.
> 
> Do "make menuconfig" with the .config you are normally using, count the 
> number of options that are visible, and ask yourself whether we can 
> really expect users to read the help texts for every single option shown.
> 
> People mostly read help texts for options where they don't understand 
> what this option is about - and "Serial ATA" therefore is an option that 
> is likely to get enabled without the user looking at the help text.

If you create .config from scratch, then you can get away without
reading help texts if you have a target with minimal hardware and
protocols requirements and you know all the subsystems involved.

In all other cases, you theoretically need to read all help texts (minus
the ones that don't appear because you deselect entire subsystems).  In
practice, this takes too much time, hence you take an existing .config
(yours or somebody else's) and go from there.

Whenever one enables an option for the first time, it would IMO be
foolish to ignore its help text.
-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

[PATCH] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[Stefan Richter]

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---

Applicable to 2.6.23-rc6 and to scsi-misc.

 drivers/scsi/Kconfig |   32 ++++++++++++++++++++------------
 1 file changed, 20 insertions(+), 12 deletions(-)

Index: linux-2.6.23-rc6/drivers/scsi/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig
+++ linux-2.6.23-rc6/drivers/scsi/Kconfig
@@ -12,23 +12,31 @@ config SCSI
 	depends on BLOCK
 	select SCSI_DMA if HAS_DMA
 	---help---
-	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
-	  any other SCSI device under Linux, say Y and make sure that you know
-	  the name of your SCSI host adapter (the card inside your computer
-	  that "speaks" the SCSI protocol, also called SCSI controller),
-	  because you will be asked for it.
-
-	  You also need to say Y here if you have a device which speaks
-	  the SCSI protocol.  Examples of this include the parallel port
-	  version of the IOMEGA ZIP drive, USB storage devices, Fibre
-	  Channel, FireWire storage and the IDE-SCSI emulation driver.
+	  This option enables core support for SCSI protocols.
+	  You need it
+	  - for classic parallel SCSI hardware,
+	  - for newer SCSI transports such as Fibre Channel, FireWire storage,
+	    or iSCSI,
+	  - for non-SCSI hardware which speaks SCSI protocols, such as USB
+	    storage devices or the parallel port version of Iomega Zip drive,
+	  - for non-SCSI hardware whose drivers translate from and to SCSI
+	    protocols, like the IDE-SCSI emulation driver and most notably
+	    for all SATA drivers.
 
 	  To compile this driver as a module, choose M here and read
 	  <file:Documentation/scsi/scsi.txt>.
 	  The module will be called scsi_mod.
 
 	  However, do not compile this as a module if your root file system
-	  (the one containing the directory /) is located on a SCSI device.
+	  (the one containing the directory /) is located on a SCSI device
+	  or on a device whose driver represents it as SCSI device, as
+	  indicated above.  Choose Y in this case, or set up an initrd.
+
+	  Subsequent options in this menu enable specific SCSI command set
+	  support for harddisks, CD/DVD-ROM/R/W, tapes etc..  This menu also
+	  presents options for specific SCSI controllers, while options for
+	  some other SCSI transports and all non-SCSI controllers are located
+	  in other menus (SATA, USB, FireWire etc.).
 
 config SCSI_DMA
 	bool
@@ -120,7 +128,7 @@ config BLK_DEV_SR
 	tristate "SCSI CDROM support"
 	depends on SCSI
 	---help---
-	  If you want to use a SCSI or FireWire CD-ROM under Linux,
+	  If you want to use a SCSI, SATA, USB or FireWire CD-ROM or DVD-ROM,
 	  say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
 	  <http://www.tldp.org/docs.html#howto>. Also make sure to say
 	  Y or M to "ISO 9660 CD-ROM file system support" later.

-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

Re: [PATCH] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[Jeff Garzik]

Stefan Richter wrote:
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
> ---
> 
> Applicable to 2.6.23-rc6 and to scsi-misc.
> 
>  drivers/scsi/Kconfig |   32 ++++++++++++++++++++------------
>  1 file changed, 20 insertions(+), 12 deletions(-)

ACK

[RFC PATCH] SCSI: split Kconfig menu into two

[Stefan Richter]

The SCSI core and SCSI high-level drivers play a central role not just
for the whole lot of different SCSI Architecture types of hardware and
protocols, but also for subsystems which drive non SCSI hardware,
especially libata.

Hence the options pertaining to SCSI core and high-level are separated
out into an own top-level menu outside the "Device Drivers" submenu, and
some prompts are reworded.

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---

Applies after patch "SCSI: update Kconfig help text to indicate SCSI
core's widespread usage", http://lkml.org/lkml/2007/9/14/168.  These two
patches could very well be collapsed into one.


 arch/alpha/Kconfig            |    2 
 arch/arm/Kconfig              |    2 
 arch/avr32/Kconfig            |    2 
 arch/blackfin/Kconfig         |    2 
 arch/cris/Kconfig             |    2 
 arch/frv/Kconfig              |    2 
 arch/i386/Kconfig             |    2 
 arch/ia64/Kconfig             |    2 
 arch/m32r/Kconfig             |    2 
 arch/m68k/Kconfig             |    2 
 arch/m68knommu/Kconfig        |    2 
 arch/mips/Kconfig             |    2 
 arch/parisc/Kconfig           |    2 
 arch/powerpc/Kconfig          |    2 
 arch/ppc/Kconfig              |    2 
 arch/s390/Kconfig             |    2 
 arch/sh/Kconfig               |    2 
 arch/sh64/Kconfig             |    2 
 arch/sparc/Kconfig            |    2 
 arch/sparc64/Kconfig          |    2 
 arch/um/Kconfig               |    2 
 arch/v850/Kconfig             |    2 
 arch/x86_64/Kconfig           |    4 
 arch/xtensa/Kconfig           |    2 
 drivers/Kconfig               |    2 
 drivers/scsi/Kconfig          | 1589 ----------------------------------
 drivers/scsi/Kconfig.lowlevel | 1578 +++++++++++++++++++++++++++++++++
 27 files changed, 1635 insertions(+), 1584 deletions(-)

Index: linux-2.6.23-rc6/arch/alpha/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/alpha/Kconfig
+++ linux-2.6.23-rc6/arch/alpha/Kconfig
@@ -650,6 +650,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/arm/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/arm/Kconfig
+++ linux-2.6.23-rc6/arch/arm/Kconfig
@@ -1003,6 +1003,8 @@ endif
 
 source "drivers/scsi/Kconfig"
 
+source "drivers/scsi/Kconfig.lowlevel"
+
 source "drivers/ata/Kconfig"
 
 source "drivers/md/Kconfig"
Index: linux-2.6.23-rc6/arch/avr32/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/avr32/Kconfig
+++ linux-2.6.23-rc6/arch/avr32/Kconfig
@@ -227,6 +227,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/blackfin/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/blackfin/Kconfig
+++ linux-2.6.23-rc6/arch/blackfin/Kconfig
@@ -910,6 +910,8 @@ endif
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/cris/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/cris/Kconfig
+++ linux-2.6.23-rc6/arch/cris/Kconfig
@@ -170,6 +170,8 @@ source "drivers/ide/Kconfig"
 
 source "drivers/scsi/Kconfig"
 
+source "drivers/scsi/Kconfig.lowlevel"
+
 source "drivers/ieee1394/Kconfig"
 
 source "drivers/message/i2o/Kconfig"
Index: linux-2.6.23-rc6/arch/frv/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/frv/Kconfig
+++ linux-2.6.23-rc6/arch/frv/Kconfig
@@ -371,6 +371,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/i386/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/i386/Kconfig
+++ linux-2.6.23-rc6/arch/i386/Kconfig
@@ -1224,6 +1224,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/ia64/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/ia64/Kconfig
+++ linux-2.6.23-rc6/arch/ia64/Kconfig
@@ -536,6 +536,8 @@ endif
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 config MSPEC
Index: linux-2.6.23-rc6/arch/m32r/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/m32r/Kconfig
+++ linux-2.6.23-rc6/arch/m32r/Kconfig
@@ -422,6 +422,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/m68k/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/m68k/Kconfig
+++ linux-2.6.23-rc6/arch/m68k/Kconfig
@@ -470,6 +470,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 menu "Character devices"
Index: linux-2.6.23-rc6/arch/m68knommu/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/m68knommu/Kconfig
+++ linux-2.6.23-rc6/arch/m68knommu/Kconfig
@@ -692,6 +692,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/mips/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/mips/Kconfig
+++ linux-2.6.23-rc6/arch/mips/Kconfig
@@ -1912,6 +1912,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/parisc/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/parisc/Kconfig
+++ linux-2.6.23-rc6/arch/parisc/Kconfig
@@ -263,6 +263,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/powerpc/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/powerpc/Kconfig
+++ linux-2.6.23-rc6/arch/powerpc/Kconfig
@@ -624,6 +624,8 @@ endif
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/ppc/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/ppc/Kconfig
+++ linux-2.6.23-rc6/arch/ppc/Kconfig
@@ -1423,6 +1423,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/s390/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/s390/Kconfig
+++ linux-2.6.23-rc6/arch/s390/Kconfig
@@ -525,6 +525,8 @@ config PCMCIA
 config CCW
 	def_bool y
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/sh/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/sh/Kconfig
+++ linux-2.6.23-rc6/arch/sh/Kconfig
@@ -727,6 +727,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/sh64/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/sh64/Kconfig
+++ linux-2.6.23-rc6/arch/sh64/Kconfig
@@ -281,6 +281,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/arch/sparc/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/sparc/Kconfig
+++ linux-2.6.23-rc6/arch/sparc/Kconfig
@@ -264,6 +264,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 if !SUN4
Index: linux-2.6.23-rc6/arch/sparc64/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/sparc64/Kconfig
+++ linux-2.6.23-rc6/arch/sparc64/Kconfig
@@ -452,6 +452,8 @@ config CMDLINE
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "drivers/sbus/char/Kconfig"
Index: linux-2.6.23-rc6/arch/x86_64/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/x86_64/Kconfig
+++ linux-2.6.23-rc6/arch/x86_64/Kconfig
@@ -777,7 +777,9 @@ endmenu
 
 source "net/Kconfig"
 
-source drivers/Kconfig
+source "drivers/scsi/Kconfig"
+
+source "drivers/Kconfig"
 
 source "drivers/firmware/Kconfig"
 
Index: linux-2.6.23-rc6/arch/um/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/um/Kconfig
+++ linux-2.6.23-rc6/arch/um/Kconfig
@@ -324,6 +324,8 @@ source "lib/Kconfig"
 
 source "drivers/scsi/Kconfig"
 
+source "drivers/scsi/Kconfig.lowlevel"
+
 source "drivers/md/Kconfig"
 
 if BROKEN
Index: linux-2.6.23-rc6/arch/v850/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/v850/Kconfig
+++ linux-2.6.23-rc6/arch/v850/Kconfig
@@ -294,6 +294,8 @@ source "drivers/ide/Kconfig"
 
 source "drivers/scsi/Kconfig"
 
+source "drivers/scsi/Kconfig.lowlevel"
+
 endmenu
 
 #############################################################################
Index: linux-2.6.23-rc6/arch/xtensa/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/arch/xtensa/Kconfig
+++ linux-2.6.23-rc6/arch/xtensa/Kconfig
@@ -230,6 +230,8 @@ endmenu
 
 source "net/Kconfig"
 
+source "drivers/scsi/Kconfig"
+
 source "drivers/Kconfig"
 
 source "fs/Kconfig"
Index: linux-2.6.23-rc6/drivers/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/drivers/Kconfig
+++ linux-2.6.23-rc6/drivers/Kconfig
@@ -22,7 +22,7 @@ source "drivers/misc/Kconfig"
 
 source "drivers/ide/Kconfig"
 
-source "drivers/scsi/Kconfig"
+source "drivers/scsi/Kconfig.lowlevel"
 
 source "drivers/ata/Kconfig"
 
Index: linux-2.6.23-rc6/drivers/scsi/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig
+++ linux-2.6.23-rc6/drivers/scsi/Kconfig
@@ -1,14 +1,7 @@
-menu "SCSI device support"
-
-config RAID_ATTRS
-	tristate "RAID Transport Class"
-	default n
-	depends on BLOCK
-	---help---
-	  Provides RAID
+menu "Storage (core and SCSI commands)"
 
 config SCSI
-	tristate "SCSI device support"
+	tristate "Storage support (core and SCSI commands)"
 	depends on BLOCK
 	select SCSI_DMA if HAS_DMA
 	---help---
@@ -42,13 +35,6 @@ config SCSI_DMA
 	bool
 	default n
 
-config SCSI_TGT
-	tristate "SCSI target support"
-	depends on SCSI && EXPERIMENTAL
-	---help---
-	  If you want to use SCSI target mode drivers enable this option.
-	  If you choose M, the module will be called scsi_tgt.
-
 config SCSI_NETLINK
 	bool
 	default	n
@@ -65,11 +51,11 @@ config SCSI_PROC_FS
 
 	  If unsure say Y.
 
-comment "SCSI support type (disk, tape, CD-ROM)"
+comment "SCSI command set drivers (disk, tape, CD-ROM)"
 	depends on SCSI
 
 config BLK_DEV_SD
-	tristate "SCSI disk support"
+	tristate "Harddisks and other Direct access devices"
 	depends on SCSI
 	---help---
 	  If you want to use SCSI hard disks, Fibre Channel disks,
@@ -90,7 +76,7 @@ config BLK_DEV_SD
 	  (below) as a module either.
 
 config CHR_DEV_ST
-	tristate "SCSI tape support"
+	tristate "Tape drives"
 	depends on SCSI
 	---help---
 	  If you want to use a SCSI tape drive under Linux, say Y and read the
@@ -125,7 +111,7 @@ config CHR_DEV_OSST
 	  <file:Documentation/scsi/scsi.txt>. The module will be called osst.
 
 config BLK_DEV_SR
-	tristate "SCSI CDROM support"
+	tristate "CD-ROMs, DVD-ROMs"
 	depends on SCSI
 	---help---
 	  If you want to use a SCSI, SATA, USB or FireWire CD-ROM or DVD-ROM,
@@ -261,1565 +247,4 @@ config SCSI_WAIT_SCAN
 	depends on SCSI
 	depends on MODULES
 
-menu "SCSI Transports"
-	depends on SCSI
-
-config SCSI_SPI_ATTRS
-	tristate "Parallel SCSI (SPI) Transport Attributes"
-	depends on SCSI
-	help
-	  If you wish to export transport-specific information about
-	  each attached SCSI device to sysfs, say Y.  Otherwise, say N.
-
-config SCSI_FC_ATTRS
-	tristate "FiberChannel Transport Attributes"
-	depends on SCSI
-	select SCSI_NETLINK
-	help
-	  If you wish to export transport-specific information about
-	  each attached FiberChannel device to sysfs, say Y.
-	  Otherwise, say N.
-
-config SCSI_ISCSI_ATTRS
-	tristate "iSCSI Transport Attributes"
-	depends on SCSI && NET
-	help
-	  If you wish to export transport-specific information about
-	  each attached iSCSI device to sysfs, say Y.
-	  Otherwise, say N.
-
-config SCSI_SAS_ATTRS
-	tristate "SAS Transport Attributes"
-	depends on SCSI && BLK_DEV_BSG
-	help
-	  If you wish to export transport-specific information about
-	  each attached SAS device to sysfs, say Y.
-
-source "drivers/scsi/libsas/Kconfig"
-
-endmenu
-
-menuconfig SCSI_LOWLEVEL
-	bool "SCSI low-level drivers"
-	depends on SCSI!=n
-	default y
-
-if SCSI_LOWLEVEL
-
-config ISCSI_TCP
-	tristate "iSCSI Initiator over TCP/IP"
-	depends on SCSI && INET
-	select CRYPTO
-	select CRYPTO_MD5
-	select CRYPTO_CRC32C
-	select SCSI_ISCSI_ATTRS
-	help
-	 The iSCSI Driver provides a host with the ability to access storage
-	 through an IP network. The driver uses the iSCSI protocol to transport
-	 SCSI requests and responses over a TCP/IP network between the host
-	 (the "initiator") and "targets".  Architecturally, the iSCSI driver
-	 combines with the host's TCP/IP stack, network drivers, and Network
-	 Interface Card (NIC) to provide the same functions as a SCSI or a
-	 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
-
-	 To compile this driver as a module, choose M here: the
-	 module will be called iscsi_tcp.
-
-	 The userspace component needed to initialize the driver, documentation,
-	 and sample configuration files can be found here:
-
-	 http://linux-iscsi.sf.net
-
-config SGIWD93_SCSI
-	tristate "SGI WD93C93 SCSI Driver"
-	depends on SGI_IP22 && SCSI
-  	help
-	  If you have a Western Digital WD93 SCSI controller on
-	  an SGI MIPS system, say Y.  Otherwise, say N.
-
-config SCSI_DECNCR
-	tristate "DEC NCR53C94 Scsi Driver"
-	depends on MACH_DECSTATION && SCSI && TC
-	help
-	  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
-	  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
-
-config SCSI_DECSII
-	tristate "DEC SII Scsi Driver"
-	depends on MACH_DECSTATION && SCSI && 32BIT
-
-config BLK_DEV_3W_XXXX_RAID
-	tristate "3ware 5/6/7/8xxx ATA-RAID support"
-	depends on PCI && SCSI
-	help
-	  3ware is the only hardware ATA-Raid product in Linux to date.
-	  This card is 2,4, or 8 channel master mode support only.
-	  SCSI support required!!!
-
-	  <http://www.3ware.com/>
-
-	  Please read the comments at the top of
-	  <file:drivers/scsi/3w-xxxx.c>.
-
-config SCSI_3W_9XXX
-	tristate "3ware 9xxx SATA-RAID support"
-	depends on PCI && SCSI
-	help
-	  This driver supports the 9000 series 3ware SATA-RAID cards.
-
-	  <http://www.amcc.com>
-
-	  Please read the comments at the top of
-	  <file:drivers/scsi/3w-9xxx.c>.
-
-config SCSI_7000FASST
-	tristate "7000FASST SCSI support"
-	depends on ISA && SCSI && ISA_DMA_API
-	select CHECK_SIGNATURE
-	help
-	  This driver supports the Western Digital 7000 SCSI host adapter
-	  family.  Some information is in the source:
-	  <file:drivers/scsi/wd7000.c>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called wd7000.
-
-config SCSI_ACARD
-	tristate "ACARD SCSI support"
-	depends on PCI && SCSI
-	help
-	  This driver supports the ACARD SCSI host adapter.
-	  Support Chip <ATP870 ATP876 ATP880 ATP885>
-	  To compile this driver as a module, choose M here: the
-	  module will be called atp870u.
-
-config SCSI_AHA152X
-	tristate "Adaptec AHA152X/2825 support"
-	depends on ISA && SCSI && !64BIT
-	select SCSI_SPI_ATTRS
-	select CHECK_SIGNATURE
-	---help---
-	  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
-	  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
-	  must be manually specified in this case.
-
-	  It is explained in section 3.3 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>. You might also want to
-	  read the file <file:Documentation/scsi/aha152x.txt>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called aha152x.
-
-config SCSI_AHA1542
-	tristate "Adaptec AHA1542 support"
-	depends on ISA && SCSI && ISA_DMA_API
-	---help---
-	  This is support for a SCSI host adapter.  It is explained in section
-	  3.4 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
-	  purchased by Adaptec, and some former Trantor products are being
-	  sold under the Adaptec name.  If it doesn't work out of the box, you
-	  may have to change some settings in <file:drivers/scsi/aha1542.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called aha1542.
-
-config SCSI_AHA1740
-	tristate "Adaptec AHA1740 support"
-	depends on EISA && SCSI
-	---help---
-	  This is support for a SCSI host adapter.  It is explained in section
-	  3.5 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/aha1740.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called aha1740.
-
-config SCSI_AACRAID
-	tristate "Adaptec AACRAID support"
-	depends on SCSI && PCI
-	help
-	  This driver supports a variety of Dell, HP, Adaptec, IBM and
-	  ICP storage products. For a list of supported products, refer
-	  to <file:Documentation/scsi/aacraid.txt>.
-
-	  To compile this driver as a module, choose M here: the module
-	  will be called aacraid.
-
-
-source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
-
-config SCSI_AIC7XXX_OLD
-	tristate "Adaptec AIC7xxx support (old driver)"
-	depends on (ISA || EISA || PCI ) && SCSI
-	help
-	  WARNING This driver is an older aic7xxx driver and is no longer
-	  under active development.  Adaptec, Inc. is writing a new driver to
-	  take the place of this one, and it is recommended that whenever
-	  possible, people should use the new Adaptec written driver instead
-	  of this one.  This driver will eventually be phased out entirely.
-
-	  This is support for the various aic7xxx based Adaptec SCSI
-	  controllers. These include the 274x EISA cards; 284x VLB cards;
-	  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
-	  motherboard based SCSI controllers from Adaptec. It does not support
-	  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
-	  support them. It does not support the 2920 cards from Adaptec that
-	  use the Future Domain SCSI controller chip. For those cards, you
-	  need the "Future Domain 16xx SCSI support" driver.
-
-	  In general, if the controller is based on an Adaptec SCSI controller
-	  chip from the aic777x series or the aic78xx series, this driver
-	  should work. The only exception is the 7810 which is specifically
-	  not supported (that's the RAID controller chip on the AAA-13x
-	  cards).
-
-	  Note that the AHA2920 SCSI host adapter is *not* supported by this
-	  driver; choose "Future Domain 16xx SCSI support" instead if you have
-	  one of those.
-
-	  Information on the configuration options for this controller can be
-	  found by checking the help file for each of the available
-	  configuration options. You should read
-	  <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
-	  contacting the maintainer with any questions.  The SCSI-HOWTO,
-	  available from <http://www.tldp.org/docs.html#howto>, can also
-	  be of great help.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called aic7xxx_old.
-
-source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
-source "drivers/scsi/aic94xx/Kconfig"
-
-# All the I2O code and drivers do not seem to be 64bit safe.
-config SCSI_DPT_I2O
-	tristate "Adaptec I2O RAID support "
-	depends on !64BIT && SCSI && PCI && VIRT_TO_BUS
-	help
-	  This driver supports all of Adaptec's I2O based RAID controllers as 
-	  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
-	  driver by Deanna Bonds.  See <file:Documentation/scsi/dpti.txt>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called dpt_i2o.
-
-config SCSI_ADVANSYS
-	tristate "AdvanSys SCSI support"
-	depends on SCSI
-	depends on ISA || EISA || PCI
-	depends on BROKEN || X86_32
-	help
-	  This is a driver for all SCSI host adapters manufactured by
-	  AdvanSys. It is documented in the kernel source in
-	  <file:drivers/scsi/advansys.c>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called advansys.
-
-config SCSI_IN2000
-	tristate "Always IN2000 SCSI support"
-	depends on ISA && SCSI
-	help
-	  This is support for an ISA bus SCSI host adapter.  You'll find more
-	  information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
-	  out of the box, you may have to change the jumpers for IRQ or
-	  address selection.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called in2000.
-
-config SCSI_ARCMSR
-	tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
-	depends on PCI && SCSI
-	help
-	  This driver supports all of ARECA's SATA RAID controller cards.
-	  This is an ARECA-maintained driver by Erich Chen.
-	  If you have any problems, please mail to: < erich@areca.com.tw >
-	  Areca supports Linux RAID config tools.
-
-	  < http://www.areca.com.tw >
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called arcmsr (modprobe arcmsr).
-
-source "drivers/scsi/megaraid/Kconfig.megaraid"
-
-config SCSI_HPTIOP
-	tristate "HighPoint RocketRAID 3xxx Controller support"
-	depends on SCSI && PCI
-	help
-	  This option enables support for HighPoint RocketRAID 3xxx
-	  controllers.
-
-	  To compile this driver as a module, choose M here; the module
-	  will be called hptiop. If unsure, say N.
-
-config SCSI_BUSLOGIC
-	tristate "BusLogic SCSI support"
-	depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
-	---help---
-	  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
-	  Adapters. Consult the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>, and the files
-	  <file:Documentation/scsi/BusLogic.txt> and
-	  <file:Documentation/scsi/FlashPoint.txt> for more information.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called BusLogic.
-
-config SCSI_OMIT_FLASHPOINT
-	bool "Omit FlashPoint support"
-	depends on SCSI_BUSLOGIC
-	help
-	  This option allows you to omit the FlashPoint support from the
-	  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
-	  substantial, so users of MultiMaster Host Adapters may wish to omit
-	  it.
-
-config SCSI_DMX3191D
-	tristate "DMX3191D SCSI support"
-	depends on PCI && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is support for Domex DMX3191D SCSI Host Adapters.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called dmx3191d.
-
-config SCSI_DTC3280
-	tristate "DTC3180/3280 SCSI support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	select CHECK_SIGNATURE
-	help
-	  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
-	  the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>, and the file
-	  <file:Documentation/scsi/dtc3x80.txt>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called dtc.
-
-config SCSI_EATA
-	tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
-	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
-	---help---
-	  This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
-	  ISA and all EISA I/O addresses are probed looking for the "EATA"
-	  signature. The addresses of all the PCI SCSI controllers reported
-          by the PCI subsystem are probed as well.
-
-	  You want to read the start of <file:drivers/scsi/eata.c> and the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called eata.
-
-config SCSI_EATA_TAGGED_QUEUE
-	bool "enable tagged command queueing"
-	depends on SCSI_EATA
-	help
-	  This is a feature of SCSI-2 which improves performance: the host
-	  adapter can send several SCSI commands to a device's queue even if
-	  previous commands haven't finished yet.
-	  This is equivalent to the "eata=tc:y" boot option.
-
-config SCSI_EATA_LINKED_COMMANDS
-	bool "enable elevator sorting"
-	depends on SCSI_EATA
-	help
-	  This option enables elevator sorting for all probed SCSI disks and
-	  CD-ROMs. It definitely reduces the average seek distance when doing
-	  random seeks, but this does not necessarily result in a noticeable
-	  performance improvement: your mileage may vary...
-	  This is equivalent to the "eata=lc:y" boot option.
-
-config SCSI_EATA_MAX_TAGS
-	int "maximum number of queued commands"
-	depends on SCSI_EATA
-	default "16"
-	help
-	  This specifies how many SCSI commands can be maximally queued for
-	  each probed SCSI device. You should reduce the default value of 16
-	  only if you have disks with buggy or limited tagged command support.
-	  Minimum is 2 and maximum is 62. This value is also the window size
-	  used by the elevator sorting option above. The effective value used
-	  by the driver for each probed SCSI device is reported at boot time.
-	  This is equivalent to the "eata=mq:8" boot option.
-
-config SCSI_EATA_PIO
-	tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
-	depends on (ISA || EISA || PCI) && SCSI && BROKEN
-	---help---
-	  This driver supports all EATA-PIO protocol compliant SCSI Host
-	  Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
-	  host adapters could also use this driver but are discouraged from
-	  doing so, since this driver only supports hard disks and lacks
-	  numerous features.  You might want to have a look at the SCSI-HOWTO,
-	  available from <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called eata_pio.
-
-config SCSI_FUTURE_DOMAIN
-	tristate "Future Domain 16xx SCSI/AHA-2920A support"
-	depends on (ISA || PCI) && SCSI
-	select CHECK_SIGNATURE
-	---help---
-	  This is support for Future Domain's 16-bit SCSI host adapters
-	  (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
-	  other adapters based on the Future Domain chipsets (Quantum
-	  ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
-	  It is explained in section 3.7 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
-	  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
-	  controller support"). This Future Domain driver works with the older
-	  Adaptec AHA-2920A boards with a Future Domain chip on them.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called fdomain.
-
-config SCSI_FD_MCS
-	tristate "Future Domain MCS-600/700 SCSI support"
-	depends on MCA_LEGACY && SCSI
-	---help---
-	  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
-	  Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
-	  is identical to the MCS 700 and hence also supported by this driver.
-	  This driver also supports the Reply SB16/SCSI card (the SCSI part).
-	  It supports multiple adapters in the same system.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called fd_mcs.
-
-config SCSI_GDTH
-	tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
-	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
-	---help---
-	  Formerly called GDT SCSI Disk Array Controller Support.
-
-	  This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 
-	  manufactured by Intel Corporation/ICP vortex GmbH. It is documented
-	  in the kernel source in <file:drivers/scsi/gdth.c> and
-	  <file:drivers/scsi/gdth.h.>
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called gdth.
-
-config SCSI_GENERIC_NCR5380
-	tristate "Generic NCR5380/53c400 SCSI PIO support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This is a driver for the old NCR 53c80 series of SCSI controllers
-	  on boards using PIO. Most boards such as the Trantor T130 fit this
-	  category, along with a large number of ISA 8bit controllers shipped
-	  for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
-	  you should select the specific driver for that card rather than
-	  generic 5380 support.
-
-	  It is explained in section 3.8 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/g_NCR5380.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called g_NCR5380.
-
-config SCSI_GENERIC_NCR5380_MMIO
-	tristate "Generic NCR5380/53c400 SCSI MMIO support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This is a driver for the old NCR 53c80 series of SCSI controllers
-	  on boards using memory mapped I/O. 
-	  It is explained in section 3.8 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/g_NCR5380.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called g_NCR5380_mmio.
-
-config SCSI_GENERIC_NCR53C400
-	bool "Enable NCR53c400 extensions"
-	depends on SCSI_GENERIC_NCR5380
-	help
-	  This enables certain optimizations for the NCR53c400 SCSI cards.
-	  You might as well try it out.  Note that this driver will only probe
-	  for the Trantor T130B in its default configuration; you might have
-	  to pass a command line option to the kernel at boot time if it does
-	  not detect your card.  See the file
-	  <file:Documentation/scsi/g_NCR5380.txt> for details.
-
-config SCSI_IBMMCA
-	tristate "IBMMCA SCSI support"
-	depends on MCA && SCSI
-	---help---
-	  This is support for the IBM SCSI adapter found in many of the PS/2
-	  series computers.  These machines have an MCA bus, so you need to
-	  answer Y to "MCA support" as well and read
-	  <file:Documentation/mca.txt>.
-
-	  If the adapter isn't found during boot (a common problem for models
-	  56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
-	  option, where <pun> is the id of the SCSI subsystem (usually 7, but
-	  if that doesn't work check your reference diskette).  Owners of
-	  model 95 with a LED-matrix-display can in addition activate some
-	  activity info like under OS/2, but more informative, by setting
-	  'ibmmcascsi=display' as an additional kernel parameter.  Try "man
-	  bootparam" or see the documentation of your boot loader about how to
-	  pass options to the kernel.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ibmmca.
-
-config IBMMCA_SCSI_ORDER_STANDARD
-	bool "Standard SCSI-order"
-	depends on SCSI_IBMMCA
-	---help---
-	  In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
-	  are assigned to the drive letters, starting with the lowest SCSI-id
-	  (physical number -- pun) to be drive C:, as seen from DOS and
-	  similar operating systems. When looking into papers describing the
-	  ANSI-SCSI-standard, this assignment of drives appears to be wrong.
-	  The SCSI-standard follows a hardware-hierarchy which says that id 7
-	  has the highest priority and id 0 the lowest. Therefore, the host
-	  adapters are still today everywhere placed as SCSI-id 7 by default.
-	  In the SCSI-standard, the drive letters express the priority of the
-	  disk. C: should be the hard disk, or a partition on it, with the
-	  highest priority. This must therefore be the disk with the highest
-	  SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
-	  original definition of the SCSI-standard as also industrial- and
-	  process-control-machines, like VME-CPUs running under realtime-OSes
-	  (e.g. LynxOS, OS9) do.
-
-	  If you like to run Linux on your MCA-machine with the same
-	  assignment of hard disks as seen from e.g. DOS or OS/2 on your
-	  machine, which is in addition conformant to the SCSI-standard, you
-	  must say Y here. This is also necessary for MCA-Linux users who want
-	  to keep downward compatibility to older releases of the
-	  IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
-	  June 1997).
-
-	  If you like to have the lowest SCSI-id assigned as drive C:, as
-	  modern SCSI-BIOSes do, which does not conform to the standard, but
-	  is widespread and common in the PC-world of today, you must say N
-	  here. If unsure, say Y.
-
-config IBMMCA_SCSI_DEV_RESET
-	bool "Reset SCSI-devices at boottime"
-	depends on SCSI_IBMMCA
-	---help---
-	  By default, SCSI-devices are reset when the machine is powered on.
-	  However, some devices exist, like special-control-devices,
-	  SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
-	  not reset when switched on. If you say Y here, each device connected
-	  to your SCSI-bus will be issued a reset-command after it has been
-	  probed, while the kernel is booting. This may cause problems with
-	  more modern devices, like hard disks, which do not appreciate these
-	  reset commands, and can cause your system to hang. So say Y only if
-	  you know that one of your older devices needs it; N is the safe
-	  answer.
-
-config SCSI_IPS
-	tristate "IBM ServeRAID support"
-	depends on PCI && SCSI
-	---help---
-	  This is support for the IBM ServeRAID hardware RAID controllers.
-	  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
-	  for more information.  If this driver does not work correctly
-	  without modification please contact the author by email at
-	  <ipslinux@adaptec.com>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ips.
-
-config SCSI_IBMVSCSI
-	tristate "IBM Virtual SCSI support"
-	depends on PPC_PSERIES || PPC_ISERIES
-	help
-	  This is the IBM POWER Virtual SCSI Client
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ibmvscsic.
-
-config SCSI_IBMVSCSIS
-	tristate "IBM Virtual SCSI Server support"
-	depends on PPC_PSERIES && SCSI_TGT && SCSI_SRP
-	help
-	  This is the SRP target driver for IBM pSeries virtual environments.
-
-	  The userspace component needed to initialize the driver and
-	  documentation can be found:
-
-	  http://stgt.berlios.de/
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ibmvstgt.
-
-config SCSI_INITIO
-	tristate "Initio 9100U(W) support"
-	depends on PCI && SCSI
-	help
-	  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
-	  read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called initio.
-
-config SCSI_INIA100
-	tristate "Initio INI-A100U2W support"
-	depends on PCI && SCSI
-	help
-	  This is support for the Initio INI-A100U2W SCSI host adapter.
-	  Please read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called a100u2w.
-
-config SCSI_PPA
-	tristate "IOMEGA parallel port (ppa - older drives)"
-	depends on SCSI && PARPORT_PC
-	---help---
-	  This driver supports older versions of IOMEGA's parallel port ZIP
-	  drive (a 100 MB removable media device).
-
-	  Note that you can say N here if you have the SCSI version of the ZIP
-	  drive: it will be supported automatically if you said Y to the
-	  generic "SCSI disk support", above.
-
-	  If you have the ZIP Plus drive or a more recent parallel port ZIP
-	  drive (if the supplied cable with the drive is labeled "AutoDetect")
-	  then you should say N here and Y to "IOMEGA parallel port (imm -
-	  newer drives)", below.
-
-	  For more information about this driver and how to use it you should
-	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
-	  the SCSI-HOWTO, which is available from
-	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
-	  you will still be able to use the parallel port for other tasks,
-	  such as a printer; it is safe to compile both drivers into the
-	  kernel.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ppa.
-
-config SCSI_IMM
-	tristate "IOMEGA parallel port (imm - newer drives)"
-	depends on SCSI && PARPORT_PC
-	---help---
-	  This driver supports newer versions of IOMEGA's parallel port ZIP
-	  drive (a 100 MB removable media device).
-
-	  Note that you can say N here if you have the SCSI version of the ZIP
-	  drive: it will be supported automatically if you said Y to the
-	  generic "SCSI disk support", above.
-
-	  If you have the ZIP Plus drive or a more recent parallel port ZIP
-	  drive (if the supplied cable with the drive is labeled "AutoDetect")
-	  then you should say Y here; if you have an older ZIP drive, say N
-	  here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
-
-	  For more information about this driver and how to use it you should
-	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
-	  the SCSI-HOWTO, which is available from
-	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
-	  you will still be able to use the parallel port for other tasks,
-	  such as a printer; it is safe to compile both drivers into the
-	  kernel.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called imm.
-
-config SCSI_IZIP_EPP16
-	bool "ppa/imm option - Use slow (but safe) EPP-16"
-	depends on SCSI_PPA || SCSI_IMM
-	---help---
-	  EPP (Enhanced Parallel Port) is a standard for parallel ports which
-	  allows them to act as expansion buses that can handle up to 64
-	  peripheral devices.
-
-	  Some parallel port chipsets are slower than their motherboard, and
-	  so we have to control the state of the chipset's FIFO queue every
-	  now and then to avoid data loss. This will be done if you say Y
-	  here.
-
-	  Generally, saying Y is the safe option and slows things down a bit.
-
-config SCSI_IZIP_SLOW_CTR
-	bool "ppa/imm option - Assume slow parport control register"
-	depends on SCSI_PPA || SCSI_IMM
-	help
-	  Some parallel ports are known to have excessive delays between
-	  changing the parallel port control register and good data being
-	  available on the parallel port data/status register. This option
-	  forces a small delay (1.0 usec to be exact) after changing the
-	  control register to let things settle out. Enabling this option may
-	  result in a big drop in performance but some very old parallel ports
-	  (found in 386 vintage machines) will not work properly.
-
-	  Generally, saying N is fine.
-
-config SCSI_NCR53C406A
-	tristate "NCR53c406a SCSI support"
-	depends on ISA && SCSI
-	help
-	  This is support for the NCR53c406a SCSI host adapter.  For user
-	  configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
-	  in the kernel source.  Also read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called NCR53c406.
-
-config SCSI_NCR_D700
-	tristate "NCR Dual 700 MCA SCSI support"
-	depends on MCA && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is a driver for the MicroChannel Dual 700 card produced by
-	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
-	  tries to negotiate sync and uses tag command queueing.
-
-	  Unless you have an NCR manufactured machine, the chances are that
-	  you do not have this SCSI card, so say N.
-
-config SCSI_LASI700
-	tristate "HP Lasi SCSI support for 53c700/710"
-	depends on GSC && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is a driver for the SCSI controller in the Lasi chip found in
-	  many PA-RISC workstations & servers.  If you do not know whether you
-	  have a Lasi chip, it is safe to say "Y" here.
-
-config SCSI_SNI_53C710
-	tristate "SNI RM SCSI support for 53c710"
-	depends on SNI_RM && SCSI
-	select SCSI_SPI_ATTRS
-	select 53C700_LE_ON_BE
-	help
-	  This is a driver for the onboard SCSI controller found in older
-	  SNI RM workstations & servers.
-
-config 53C700_LE_ON_BE
-	bool
-	depends on SCSI_LASI700
-	default y
-
-config SCSI_STEX
-	tristate "Promise SuperTrak EX Series support"
-	depends on PCI && SCSI
-	---help---
-	  This driver supports Promise SuperTrak EX series storage controllers.
-
-	  Promise provides Linux RAID configuration utility for these
-	  controllers. Please visit <http://www.promise.com> to download.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called stex.
-
-config 53C700_BE_BUS
-	bool
-	depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
-	default y
-
-config SCSI_SYM53C8XX_2
-	tristate "SYM53C8XX Version 2 SCSI support"
-	depends on PCI && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This driver supports the whole NCR53C8XX/SYM53C8XX family of
-	  PCI-SCSI controllers.  It also supports the subset of LSI53C10XX
-	  Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
-	  language.  It does not support LSI53C10XX Ultra-320 PCI-X SCSI
-	  controllers; you need to use the Fusion MPT driver for that.
-
-	  Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
-	  information.
-
-config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
-	int "DMA addressing mode"
-	depends on SCSI_SYM53C8XX_2
-	default "1"
-	---help---
-	  This option only applies to PCI-SCSI chips that are PCI DAC
-	  capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
-
-	  When set to 0, the driver will program the chip to only perform
-	  32-bit DMA.  When set to 1, the chip will be able to perform DMA
-	  to addresses up to 1TB.  When set to 2, the driver supports the
-	  full 64-bit DMA address range, but can only address 16 segments
-	  of 4 GB each.  This limits the total addressable range to 64 GB.
-
-	  Most machines with less than 4GB of memory should use a setting
-	  of 0 for best performance.  If your machine has 4GB of memory
-	  or more, you should set this option to 1 (the default).
-
-	  The still experimental value 2 (64 bit DMA addressing with 16
-	  x 4GB segments limitation) can be used on systems that require
-	  PCI address bits past bit 39 to be set for the addressing of
-	  memory using PCI DAC cycles.
-
-config SCSI_SYM53C8XX_DEFAULT_TAGS
-	int "Default tagged command queue depth"
-	depends on SCSI_SYM53C8XX_2
-	default "16"
-	help
-	  This is the default value of the command queue depth the
-	  driver will announce to the generic SCSI layer for devices
-	  that support tagged command queueing. This value can be changed
-	  from the boot command line.  This is a soft limit that cannot
-	  exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
-
-config SCSI_SYM53C8XX_MAX_TAGS
-	int "Maximum number of queued commands"
-	depends on SCSI_SYM53C8XX_2
-	default "64"
-	help
-	  This option allows you to specify the maximum number of commands
-	  that can be queued to any device, when tagged command queuing is
-	  possible. The driver supports up to 256 queued commands per device.
-	  This value is used as a compiled-in hard limit.
-
-config SCSI_SYM53C8XX_MMIO
-	bool "Use memory mapped IO"
-	depends on SCSI_SYM53C8XX_2
-	default y
-	help
-	  Memory mapped IO is faster than Port IO.  Most people should
-	  answer Y here, but some machines may have problems.  If you have
-	  to answer N here, please report the problem to the maintainer.
-
-config SCSI_IPR
-	tristate "IBM Power Linux RAID adapter support"
-	depends on PCI && SCSI && ATA
-	select FW_LOADER
-	---help---
-	  This driver supports the IBM Power Linux family RAID adapters.
-	  This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
-	  as IBM iSeries 5702, 5703, 5709, and 570A.
-
-config SCSI_IPR_TRACE
-	bool "enable driver internal trace"
-	depends on SCSI_IPR
-	default y
-	help
-	  If you say Y here, the driver will trace all commands issued
-	  to the adapter. Performance impact is minimal. Trace can be
-	  dumped using /sys/bus/class/scsi_host/hostXX/trace.
-
-config SCSI_IPR_DUMP
-	bool "enable adapter dump support"
-	depends on SCSI_IPR
-	default y
-	help
-	  If you say Y here, the driver will support adapter crash dump.
-	  If you enable this support, the iprdump daemon can be used
-	  to capture adapter failure analysis information.
-
-config SCSI_ZALON
-	tristate "Zalon SCSI support"
-	depends on GSC && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  The Zalon is a GSC/HSC bus interface chip that sits between the
-	  PA-RISC processor and the NCR 53c720 SCSI controller on C100,
-	  C110, J200, J210 and some D, K & R-class machines.  It's also
-	  used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
-	  Say Y here if you have one of these machines or cards.
-
-config SCSI_NCR_Q720
-	tristate "NCR Quad 720 MCA SCSI support"
-	depends on MCA && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is a driver for the MicroChannel Quad 720 card produced by
-	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
-	  tries to negotiate sync and uses tag command queueing.
-
-	  Unless you have an NCR manufactured machine, the chances are that
-	  you do not have this SCSI card, so say N.
-
-config SCSI_NCR53C8XX_DEFAULT_TAGS
-	int "default tagged command queue depth"
-	depends on SCSI_ZALON || SCSI_NCR_Q720
-	default "8"
-	---help---
-	  "Tagged command queuing" is a feature of SCSI-2 which improves
-	  performance: the host adapter can send several SCSI commands to a
-	  device's queue even if previous commands haven't finished yet.
-	  Because the device is intelligent, it can optimize its operations
-	  (like head positioning) based on its own request queue. Some SCSI
-	  devices don't implement this properly; if you want to disable this
-	  feature, enter 0 or 1 here (it doesn't matter which).
-
-	  The default value is 8 and should be supported by most hard disks.
-	  This value can be overridden from the boot command line using the
-	  'tags' option as follows (example):
-	  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
-	  4, set queue depth to 16 for target 2 and target 3 on controller 0
-	  and set queue depth to 10 for target 0 / lun 2 on controller 1.
-
-	  The normal answer therefore is to go with the default 8 and to use
-	  a boot command line option for devices that need to use a different
-	  command queue depth.
-
-	  There is no safe option other than using good SCSI devices.
-
-config SCSI_NCR53C8XX_MAX_TAGS
-	int "maximum number of queued commands"
-	depends on SCSI_ZALON || SCSI_NCR_Q720
-	default "32"
-	---help---
-	  This option allows you to specify the maximum number of commands
-	  that can be queued to any device, when tagged command queuing is
-	  possible. The default value is 32. Minimum is 2, maximum is 64.
-	  Modern hard disks are able to support 64 tags and even more, but
-	  do not seem to be faster when more than 32 tags are being used.
-
-	  So, the normal answer here is to go with the default value 32 unless
-	  you are using very large hard disks with large cache (>= 1 MB) that
-	  are able to take advantage of more than 32 tagged commands.
-
-	  There is no safe option and the default answer is recommended.
-
-config SCSI_NCR53C8XX_SYNC
-	int "synchronous transfers frequency in MHz"
-	depends on SCSI_ZALON || SCSI_NCR_Q720
-	default "20"
-	---help---
-	  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
-	  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
-	  are respectively the maximum data transfer rates in mega-transfers
-	  per second for each class.  For example, a FAST-20 Wide 16 device is
-	  able to transfer data at 20 million 16 bit packets per second for a
-	  total rate of 40 MB/s.
-
-	  You may specify 0 if you want to only use asynchronous data
-	  transfers. This is the safest and slowest option. Otherwise, specify
-	  a value between 5 and 80, depending on the capability of your SCSI
-	  controller.  The higher the number, the faster the data transfer.
-	  Note that 80 should normally be ok since the driver decreases the
-	  value automatically according to the controller's capabilities.
-
-	  Your answer to this question is ignored for controllers with NVRAM,
-	  since the driver will get this information from the user set-up.  It
-	  also can be overridden using a boot setup option, as follows
-	  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
-	  for FAST-20 synchronous data transfer (20 mega-transfers per
-	  second).
-
-	  The normal answer therefore is not to go with the default but to
-	  select the maximum value 80 allowing the driver to use the maximum
-	  value supported by each controller. If this causes problems with
-	  your SCSI devices, you should come back and decrease the value.
-
-	  There is no safe option other than using good cabling, right
-	  terminations and SCSI conformant devices.
-
-config SCSI_NCR53C8XX_NO_DISCONNECT
-	bool "not allow targets to disconnect"
-	depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
-	help
-	  This option is only provided for safety if you suspect some SCSI
-	  device of yours to not support properly the target-disconnect
-	  feature. In that case, you would say Y here. In general however, to
-	  not allow targets to disconnect is not reasonable if there is more
-	  than 1 device on a SCSI bus. The normal answer therefore is N.
-
-config SCSI_MCA_53C9X
-	tristate "NCR MCA 53C9x SCSI support"
-	depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
-	help
-	  Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
-	  controller based on the NCR 53C94.  This driver will allow use of
-	  the controller on the 3550, and very possibly others.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mca_53c9x.
-
-config SCSI_PAS16
-	tristate "PAS16 SCSI support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This is support for a SCSI host adapter.  It is explained in section
-	  3.10 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/pas16.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called pas16.
-
-config SCSI_PSI240I
-	tristate "PSI240i support"
-	depends on ISA && SCSI
-	help
-	  This is support for the PSI240i EIDE interface card which acts as a
-	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called psi240i.
-
-config SCSI_QLOGIC_FAS
-	tristate "Qlogic FAS SCSI support"
-	depends on ISA && SCSI
-	---help---
-	  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
-	  FastSCSI! cards as well as any other card based on the FASXX chip
-	  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
-
-	  This driver does NOT support the PCI versions of these cards. The
-	  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
-	  SCSI support"), below.
-
-	  Information about this driver is contained in
-	  <file:Documentation/scsi/qlogicfas.txt>.  You should also read the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called qlogicfas.
-
-config SCSI_QLOGIC_FC_FIRMWARE
-	bool "Include loadable firmware in driver"
-	depends on SCSI_QLOGIC_FC
-  	help
-	  Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
-	  expanded LUN addressing and FcTape (FCP-2) support, in the
-	  qlogicfc driver. This is required on some platforms.
-
-config SCSI_QLOGIC_1280
-	tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
-	depends on PCI && SCSI
-	help
-	  Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called qla1280.
-
-config SCSI_QLOGICPTI
-	tristate "PTI Qlogic, ISP Driver"
-	depends on SBUS && SCSI
-	help
-	  This driver supports SBUS SCSI controllers from PTI or QLogic. These
-	  controllers are known under Solaris as qpti and in the openprom as
-	  PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
-	  driven by a different driver.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called qlogicpti.
-
-source "drivers/scsi/qla2xxx/Kconfig"
-source "drivers/scsi/qla4xxx/Kconfig"
-
-config SCSI_LPFC
-	tristate "Emulex LightPulse Fibre Channel Support"
-	depends on PCI && SCSI
-	select SCSI_FC_ATTRS
-	help
-          This lpfc driver supports the Emulex LightPulse
-          Family of Fibre Channel PCI host adapters.
-
-config SCSI_SEAGATE
-	tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
-	depends on X86 && ISA && SCSI
-	select CHECK_SIGNATURE
-	---help---
-	  These are 8-bit SCSI controllers; the ST-01 is also supported by
-	  this driver.  It is explained in section 3.9 of the SCSI-HOWTO,
-	  available from <http://www.tldp.org/docs.html#howto>.  If it
-	  doesn't work out of the box, you may have to change some macros at
-	  compiletime, which are described in <file:drivers/scsi/seagate.c>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called seagate.
-
-# definitely looks not 64bit safe:
-config SCSI_SIM710
-	tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
-	depends on (EISA || MCA) && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This driver for NCR53c710 based SCSI host adapters.
-
-	  It currently supports Compaq EISA cards and NCR MCA cards
-
-config SCSI_SYM53C416
-	tristate "Symbios 53c416 SCSI support"
-	depends on ISA && SCSI
-	---help---
-	  This is support for the sym53c416 SCSI host adapter, the SCSI
-	  adapter that comes with some HP scanners. This driver requires that
-	  the sym53c416 is configured first using some sort of PnP
-	  configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
-	  are using isapnp then you need to compile this driver as a module
-	  and then load it using insmod after isapnp has run. The parameters
-	  of the configured card(s) should be passed to the driver. The format
-	  is:
-
-	  insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called sym53c416.
-
-config SCSI_DC395x
-	tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
-	depends on PCI && SCSI && EXPERIMENTAL
-	---help---
-	  This driver supports PCI SCSI host adapters based on the ASIC
-	  TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
-
-	  This driver works, but is still in experimental status. So better
-	  have a bootable disk and a backup in case of emergency.
-
-	  Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called dc395x.
-
-config SCSI_DC390T
-	tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
-	depends on PCI && SCSI
-	---help---
-	  This driver supports PCI SCSI host adapters based on the Am53C974A
-	  chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
-	  PCscsi/PCnet (Am53/79C974) solutions.
-
-	  Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
-
-	  Note that this driver does NOT support Tekram DC390W/U/F, which are
-	  based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called tmscsim.
-
-config SCSI_T128
-	tristate "Trantor T128/T128F/T228 SCSI support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	select CHECK_SIGNATURE
-	---help---
-	  This is support for a SCSI host adapter. It is explained in section
-	  3.11 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
-	  Adaptec, and some former Trantor products are being sold under the
-	  Adaptec name.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called t128.
-
-config SCSI_U14_34F
-	tristate "UltraStor 14F/34F support"
-	depends on ISA && SCSI && ISA_DMA_API
-	---help---
-	  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
-	  The source at <file:drivers/scsi/u14-34f.c> contains some
-	  information about this hardware.  If the driver doesn't work out of
-	  the box, you may have to change some settings in
-	  <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  Note that there is also
-	  another driver for the same hardware: "UltraStor SCSI support",
-	  below.  You should say Y to both only if you want 24F support as
-	  well.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called u14-34f.
-
-config SCSI_U14_34F_TAGGED_QUEUE
-	bool "enable tagged command queueing"
-	depends on SCSI_U14_34F
-	help
-	  This is a feature of SCSI-2 which improves performance: the host
-	  adapter can send several SCSI commands to a device's queue even if
-	  previous commands haven't finished yet.
-	  This is equivalent to the "u14-34f=tc:y" boot option.
-
-config SCSI_U14_34F_LINKED_COMMANDS
-	bool "enable elevator sorting"
-	depends on SCSI_U14_34F
-	help
-	  This option enables elevator sorting for all probed SCSI disks and
-	  CD-ROMs. It definitely reduces the average seek distance when doing
-	  random seeks, but this does not necessarily result in a noticeable
-	  performance improvement: your mileage may vary...
-	  This is equivalent to the "u14-34f=lc:y" boot option.
-
-config SCSI_U14_34F_MAX_TAGS
-	int "maximum number of queued commands"
-	depends on SCSI_U14_34F
-	default "8"
-	help
-	  This specifies how many SCSI commands can be maximally queued for
-	  each probed SCSI device. You should reduce the default value of 8
-	  only if you have disks with buggy or limited tagged command support.
-	  Minimum is 2 and maximum is 14. This value is also the window size
-	  used by the elevator sorting option above. The effective value used
-	  by the driver for each probed SCSI device is reported at boot time.
-	  This is equivalent to the "u14-34f=mq:8" boot option.
-
-config SCSI_ULTRASTOR
-	tristate "UltraStor SCSI support"
-	depends on X86 && ISA && SCSI
-	---help---
-	  This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
-	  adapter family.  This driver is explained in section 3.12 of the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/ultrastor.h>.
-
-	  Note that there is also another driver for the same hardware:
-	  "UltraStor 14F/34F support", above.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ultrastor.
-
-config SCSI_NSP32
-	tristate "Workbit NinjaSCSI-32Bi/UDE support"
-	depends on PCI && SCSI && !64BIT
-	help
-	  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
-	  SCSI host adapter. Please read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called nsp32.
-
-config SCSI_DEBUG
-	tristate "SCSI debugging host simulator"
-	depends on SCSI
-	help
-	  This is a host adapter simulator that can simulate multiple hosts
-	  each with multiple dummy SCSI devices (disks). It defaults to one
-	  host adapter with one dummy SCSI disk. Each dummy disk uses kernel
-	  RAM as storage (i.e. it is a ramdisk). To save space when multiple
-	  dummy disks are simulated, they share the same kernel RAM for 
-	  their storage. See <http://www.torque.net/sg/sdebug.html> for more
-	  information. This driver is primarily of use to those testing the
-	  SCSI and block subsystems. If unsure, say N.
-
-config SCSI_MESH
-	tristate "MESH (Power Mac internal SCSI) support"
-	depends on PPC32 && PPC_PMAC && SCSI
-	help
-	  Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
-	  SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
-	  other Power Macintoshes do). Say Y to include support for this SCSI
-	  adaptor.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mesh.
-
-config SCSI_MESH_SYNC_RATE
-	int "maximum synchronous transfer rate (MB/s) (0 = async)"
-	depends on SCSI_MESH
-	default "5"
-	help
-	  On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
-	  drives a bus which is entirely internal to the machine (such as the
-	  7500, 7600, 8500, etc.), the MESH is capable of synchronous
-	  operation at up to 10 MB/s. On machines where the SCSI bus
-	  controlled by the MESH can have external devices connected, it is
-	  usually rated at 5 MB/s. 5 is a safe value here unless you know the
-	  MESH SCSI bus is internal only; in that case you can say 10. Say 0
-	  to disable synchronous operation.
-
-config SCSI_MESH_RESET_DELAY_MS
-	int "initial bus reset delay (ms) (0 = no reset)"
-	depends on SCSI_MESH
-	default "4000"
-
-config SCSI_MAC53C94
-	tristate "53C94 (Power Mac external SCSI) support"
-	depends on PPC32 && PPC_PMAC && SCSI
-	help
-	  On Power Macintoshes (and clones) with two SCSI buses, the external
-	  SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
-	  machines which only have one SCSI bus, such as the 7200, also use
-	  the 53C94. Say Y to include support for the 53C94.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mac53c94.
-
-source "drivers/scsi/arm/Kconfig"
-
-config JAZZ_ESP
-	bool "MIPS JAZZ FAS216 SCSI support"
-	depends on MACH_JAZZ && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is the driver for the onboard SCSI host adapter of MIPS Magnum
-	  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
-	  systems.
-
-config A3000_SCSI
-	tristate "A3000 WD33C93A support"
-	depends on AMIGA && SCSI
-	help
-	  If you have an Amiga 3000 and have SCSI devices connected to the
-	  built-in SCSI controller, say Y. Otherwise, say N.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called a3000.
-
-config A2091_SCSI
-	tristate "A2091/A590 WD33C93A support"
-	depends on ZORRO && SCSI
-	help
-	  If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
-	  say N.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called a2091.
-
-config GVP11_SCSI
-	tristate "GVP Series II WD33C93A support"
-	depends on ZORRO && SCSI
-	---help---
-	  If you have a Great Valley Products Series II SCSI controller,
-	  answer Y. Also say Y if you have a later model of GVP SCSI
-	  controller (such as the GVP A4008 or a Combo board). Otherwise,
-	  answer N. This driver does NOT work for the T-Rex series of
-	  accelerators from TekMagic and GVP-M.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called gvp11.
-
-config CYBERSTORM_SCSI
-	tristate "CyberStorm SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have an Amiga with an original (MkI) Phase5 Cyberstorm
-	  accelerator board and the optional Cyberstorm SCSI controller,
-	  answer Y. Otherwise, say N.
-
-config CYBERSTORMII_SCSI
-	tristate "CyberStorm Mk II SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
-	  and the optional Cyberstorm SCSI controller, say Y. Otherwise,
-	  answer N.
-
-config BLZ2060_SCSI
-	tristate "Blizzard 2060 SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
-	  and want to use the onboard SCSI controller, say Y. Otherwise,
-	  answer N.
-
-config BLZ1230_SCSI
-	tristate "Blizzard 1230IV/1260 SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
-	  1260 accelerator, and the optional SCSI module, say Y. Otherwise,
-	  say N.
-
-config FASTLANE_SCSI
-	tristate "Fastlane SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
-	  one in the near future, say Y to this question. Otherwise, say N.
-
-config SCSI_A4000T
-	tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
-	depends on AMIGA && SCSI && EXPERIMENTAL
-	select SCSI_SPI_ATTRS
-	help
-	  If you have an Amiga 4000T and have SCSI devices connected to the
-	  built-in SCSI controller, say Y. Otherwise, say N.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called a4000t.
-
-config SCSI_ZORRO7XX
-	tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
-	depends on ZORRO && SCSI && EXPERIMENTAL
-	select SCSI_SPI_ATTRS
-	help
-	  Support for various NCR53c710-based SCSI controllers on Zorro
-	  expansion boards for the Amiga.
-	  This includes:
-	    - the Amiga 4091 Zorro III SCSI-2 controller,
-	    - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
-	      (info at
-	      <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
-	    - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
-	      accelerator card for the Amiga 1200,
-	    - the SCSI controller on the GVP Turbo 040/060 accelerator.
-
-config OKTAGON_SCSI
-	tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
-	depends on ZORRO && SCSI && EXPERIMENTAL
-	help
-	  If you have the BSC Oktagon SCSI disk controller for the Amiga, say
-	  Y to this question.  If you're in doubt about whether you have one,
-	  see the picture at
-	  <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
-
-config ATARI_SCSI
-	tristate "Atari native SCSI support"
-	depends on ATARI && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  If you have an Atari with built-in NCR5380 SCSI controller (TT,
-	  Falcon, ...) say Y to get it supported. Of course also, if you have
-	  a compatible SCSI controller (e.g. for Medusa).
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called atari_scsi.
-
-	  This driver supports both styles of NCR integration into the
-	  system: the TT style (separate DMA), and the Falcon style (via
-	  ST-DMA, replacing ACSI).  It does NOT support other schemes, like
-	  in the Hades (without DMA).
-
-config ATARI_SCSI_TOSHIBA_DELAY
-	bool "Long delays for Toshiba CD-ROMs"
-	depends on ATARI_SCSI
-	help
-	  This option increases the delay after a SCSI arbitration to
-	  accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
-	  use a Toshiba CD-ROM drive; otherwise, the option is not needed and
-	  would impact performance a bit, so say N.
-
-config ATARI_SCSI_RESET_BOOT
-	bool "Reset SCSI-devices at boottime"
-	depends on ATARI_SCSI
-	help
-	  Reset the devices on your Atari whenever it boots.  This makes the
-	  boot process fractionally longer but may assist recovery from errors
-	  that leave the devices with SCSI operations partway completed.
-
-config TT_DMA_EMUL
-	bool "Hades SCSI DMA emulator"
-	depends on ATARI_SCSI && HADES
-	help
-	  This option enables code which emulates the TT SCSI DMA chip on the
-	  Hades. This increases the SCSI transfer rates at least ten times
-	  compared to PIO transfers.
-
-config MAC_SCSI
-	bool "Macintosh NCR5380 SCSI"
-	depends on MAC && SCSI=y
-	select SCSI_SPI_ATTRS
-	help
-	  This is the NCR 5380 SCSI controller included on most of the 68030
-	  based Macintoshes.  If you have one of these say Y and read the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-config SCSI_MAC_ESP
-	tristate "Macintosh NCR53c9[46] SCSI"
-	depends on MAC && SCSI
-	help
-	  This is the NCR 53c9x SCSI controller found on most of the 68040
-	  based Macintoshes.  If you have one of these say Y and read the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mac_esp.
-
-config MVME147_SCSI
-	bool "WD33C93 SCSI driver for MVME147"
-	depends on MVME147 && SCSI=y
-	select SCSI_SPI_ATTRS
-	help
-	  Support for the on-board SCSI controller on the Motorola MVME147
-	  single-board computer.
-
-config MVME16x_SCSI
-	tristate "NCR53C710 SCSI driver for MVME16x"
-	depends on MVME16x && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
-	  SCSI controller chip.  Almost everyone using one of these boards
-	  will want to say Y to this question.
-
-config BVME6000_SCSI
-	tristate "NCR53C710 SCSI driver for BVME6000"
-	depends on BVME6000 && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
-	  SCSI controller chip.  Almost everyone using one of these boards
-	  will want to say Y to this question.
-
-config SUN3_SCSI
-	tristate "Sun3 NCR5380 SCSI"
-	depends on SUN3 && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This option will enable support for the OBIO (onboard io) NCR5380
-	  SCSI controller found in the Sun 3/50 and 3/60, as well as for
-	  "Sun3" type VME scsi controllers also based on the NCR5380.
-	  General Linux information on the Sun 3 series (now discontinued)
-	  is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
-
-config SUN3X_ESP
-	bool "Sun3x ESP SCSI"
-	depends on SUN3X && SCSI=y
-	help
-	  The ESP was an on-board SCSI controller used on Sun 3/80
-	  machines.  Say Y here to compile in support for it.
-
-config SCSI_SUNESP
-	tristate "Sparc ESP Scsi Driver"
-	depends on SBUS && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is the driver for the Sun ESP SCSI host adapter. The ESP
-	  chipset is present in most SPARC SBUS-based computers.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called esp.
-
-config ZFCP
-	tristate "FCP host bus adapter driver for IBM eServer zSeries"
-	depends on S390 && QDIO && SCSI
-	select SCSI_FC_ATTRS
-	help
-          If you want to access SCSI devices attached to your IBM eServer
-          zSeries by means of Fibre Channel interfaces say Y.
-          For details please refer to the documentation provided by IBM at
-          <http://oss.software.ibm.com/developerworks/opensource/linux390>
-
-          This driver is also available as a module. This module will be
-          called zfcp. If you want to compile it as a module, say M here
-          and read <file:Documentation/kbuild/modules.txt>.
-
-config SCSI_SRP
-	tristate "SCSI RDMA Protocol helper library"
-	depends on SCSI && PCI
-	select SCSI_TGT
-	help
-	  If you wish to use SRP target drivers, say Y.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called libsrp.
-
-endif # SCSI_LOWLEVEL
-
-source "drivers/scsi/pcmcia/Kconfig"
-
-endmenu
+endmenu # Storage (core and SCSI commands)
Index: linux-2.6.23-rc6/drivers/scsi/Kconfig.lowlevel
===================================================================
--- /dev/null
+++ linux-2.6.23-rc6/drivers/scsi/Kconfig.lowlevel
@@ -0,0 +1,1578 @@
+menu "SCSI device support"
+
+config RAID_ATTRS
+	tristate "RAID Transport Class"
+	default n
+	depends on BLOCK
+	---help---
+	  Provides RAID
+
+config SCSI_TGT
+	tristate "SCSI target support"
+	depends on SCSI && EXPERIMENTAL
+	---help---
+	  If you want to use SCSI target mode drivers enable this option.
+	  If you choose M, the module will be called scsi_tgt.
+
+menu "SCSI Transports"
+	depends on SCSI
+
+config SCSI_SPI_ATTRS
+	tristate "Parallel SCSI (SPI) Transport Attributes"
+	depends on SCSI
+	help
+	  If you wish to export transport-specific information about
+	  each attached SCSI device to sysfs, say Y.  Otherwise, say N.
+
+config SCSI_FC_ATTRS
+	tristate "FiberChannel Transport Attributes"
+	depends on SCSI
+	select SCSI_NETLINK
+	help
+	  If you wish to export transport-specific information about
+	  each attached FiberChannel device to sysfs, say Y.
+	  Otherwise, say N.
+
+config SCSI_ISCSI_ATTRS
+	tristate "iSCSI Transport Attributes"
+	depends on SCSI && NET
+	help
+	  If you wish to export transport-specific information about
+	  each attached iSCSI device to sysfs, say Y.
+	  Otherwise, say N.
+
+config SCSI_SAS_ATTRS
+	tristate "SAS Transport Attributes"
+	depends on SCSI && BLK_DEV_BSG
+	help
+	  If you wish to export transport-specific information about
+	  each attached SAS device to sysfs, say Y.
+
+source "drivers/scsi/libsas/Kconfig"
+
+endmenu
+
+menuconfig SCSI_LOWLEVEL
+	bool "SCSI low-level drivers"
+	depends on SCSI!=n
+	default y
+
+if SCSI_LOWLEVEL
+
+config ISCSI_TCP
+	tristate "iSCSI Initiator over TCP/IP"
+	depends on SCSI && INET
+	select CRYPTO
+	select CRYPTO_MD5
+	select CRYPTO_CRC32C
+	select SCSI_ISCSI_ATTRS
+	help
+	 The iSCSI Driver provides a host with the ability to access storage
+	 through an IP network. The driver uses the iSCSI protocol to transport
+	 SCSI requests and responses over a TCP/IP network between the host
+	 (the "initiator") and "targets".  Architecturally, the iSCSI driver
+	 combines with the host's TCP/IP stack, network drivers, and Network
+	 Interface Card (NIC) to provide the same functions as a SCSI or a
+	 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
+
+	 To compile this driver as a module, choose M here: the
+	 module will be called iscsi_tcp.
+
+	 The userspace component needed to initialize the driver, documentation,
+	 and sample configuration files can be found here:
+
+	 http://linux-iscsi.sf.net
+
+config SGIWD93_SCSI
+	tristate "SGI WD93C93 SCSI Driver"
+	depends on SGI_IP22 && SCSI
+  	help
+	  If you have a Western Digital WD93 SCSI controller on
+	  an SGI MIPS system, say Y.  Otherwise, say N.
+
+config SCSI_DECNCR
+	tristate "DEC NCR53C94 Scsi Driver"
+	depends on MACH_DECSTATION && SCSI && TC
+	help
+	  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
+	  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
+
+config SCSI_DECSII
+	tristate "DEC SII Scsi Driver"
+	depends on MACH_DECSTATION && SCSI && 32BIT
+
+config BLK_DEV_3W_XXXX_RAID
+	tristate "3ware 5/6/7/8xxx ATA-RAID support"
+	depends on PCI && SCSI
+	help
+	  3ware is the only hardware ATA-Raid product in Linux to date.
+	  This card is 2,4, or 8 channel master mode support only.
+	  SCSI support required!!!
+
+	  <http://www.3ware.com/>
+
+	  Please read the comments at the top of
+	  <file:drivers/scsi/3w-xxxx.c>.
+
+config SCSI_3W_9XXX
+	tristate "3ware 9xxx SATA-RAID support"
+	depends on PCI && SCSI
+	help
+	  This driver supports the 9000 series 3ware SATA-RAID cards.
+
+	  <http://www.amcc.com>
+
+	  Please read the comments at the top of
+	  <file:drivers/scsi/3w-9xxx.c>.
+
+config SCSI_7000FASST
+	tristate "7000FASST SCSI support"
+	depends on ISA && SCSI && ISA_DMA_API
+	select CHECK_SIGNATURE
+	help
+	  This driver supports the Western Digital 7000 SCSI host adapter
+	  family.  Some information is in the source:
+	  <file:drivers/scsi/wd7000.c>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called wd7000.
+
+config SCSI_ACARD
+	tristate "ACARD SCSI support"
+	depends on PCI && SCSI
+	help
+	  This driver supports the ACARD SCSI host adapter.
+	  Support Chip <ATP870 ATP876 ATP880 ATP885>
+	  To compile this driver as a module, choose M here: the
+	  module will be called atp870u.
+
+config SCSI_AHA152X
+	tristate "Adaptec AHA152X/2825 support"
+	depends on ISA && SCSI && !64BIT
+	select SCSI_SPI_ATTRS
+	select CHECK_SIGNATURE
+	---help---
+	  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
+	  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
+	  must be manually specified in this case.
+
+	  It is explained in section 3.3 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>. You might also want to
+	  read the file <file:Documentation/scsi/aha152x.txt>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called aha152x.
+
+config SCSI_AHA1542
+	tristate "Adaptec AHA1542 support"
+	depends on ISA && SCSI && ISA_DMA_API
+	---help---
+	  This is support for a SCSI host adapter.  It is explained in section
+	  3.4 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
+	  purchased by Adaptec, and some former Trantor products are being
+	  sold under the Adaptec name.  If it doesn't work out of the box, you
+	  may have to change some settings in <file:drivers/scsi/aha1542.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called aha1542.
+
+config SCSI_AHA1740
+	tristate "Adaptec AHA1740 support"
+	depends on EISA && SCSI
+	---help---
+	  This is support for a SCSI host adapter.  It is explained in section
+	  3.5 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/aha1740.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called aha1740.
+
+config SCSI_AACRAID
+	tristate "Adaptec AACRAID support"
+	depends on SCSI && PCI
+	help
+	  This driver supports a variety of Dell, HP, Adaptec, IBM and
+	  ICP storage products. For a list of supported products, refer
+	  to <file:Documentation/scsi/aacraid.txt>.
+
+	  To compile this driver as a module, choose M here: the module
+	  will be called aacraid.
+
+
+source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
+
+config SCSI_AIC7XXX_OLD
+	tristate "Adaptec AIC7xxx support (old driver)"
+	depends on (ISA || EISA || PCI ) && SCSI
+	help
+	  WARNING This driver is an older aic7xxx driver and is no longer
+	  under active development.  Adaptec, Inc. is writing a new driver to
+	  take the place of this one, and it is recommended that whenever
+	  possible, people should use the new Adaptec written driver instead
+	  of this one.  This driver will eventually be phased out entirely.
+
+	  This is support for the various aic7xxx based Adaptec SCSI
+	  controllers. These include the 274x EISA cards; 284x VLB cards;
+	  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
+	  motherboard based SCSI controllers from Adaptec. It does not support
+	  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
+	  support them. It does not support the 2920 cards from Adaptec that
+	  use the Future Domain SCSI controller chip. For those cards, you
+	  need the "Future Domain 16xx SCSI support" driver.
+
+	  In general, if the controller is based on an Adaptec SCSI controller
+	  chip from the aic777x series or the aic78xx series, this driver
+	  should work. The only exception is the 7810 which is specifically
+	  not supported (that's the RAID controller chip on the AAA-13x
+	  cards).
+
+	  Note that the AHA2920 SCSI host adapter is *not* supported by this
+	  driver; choose "Future Domain 16xx SCSI support" instead if you have
+	  one of those.
+
+	  Information on the configuration options for this controller can be
+	  found by checking the help file for each of the available
+	  configuration options. You should read
+	  <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
+	  contacting the maintainer with any questions.  The SCSI-HOWTO,
+	  available from <http://www.tldp.org/docs.html#howto>, can also
+	  be of great help.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called aic7xxx_old.
+
+source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
+source "drivers/scsi/aic94xx/Kconfig"
+
+# All the I2O code and drivers do not seem to be 64bit safe.
+config SCSI_DPT_I2O
+	tristate "Adaptec I2O RAID support "
+	depends on !64BIT && SCSI && PCI && VIRT_TO_BUS
+	help
+	  This driver supports all of Adaptec's I2O based RAID controllers as 
+	  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
+	  driver by Deanna Bonds.  See <file:Documentation/scsi/dpti.txt>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called dpt_i2o.
+
+config SCSI_ADVANSYS
+	tristate "AdvanSys SCSI support"
+	depends on SCSI
+	depends on ISA || EISA || PCI
+	depends on BROKEN || X86_32
+	help
+	  This is a driver for all SCSI host adapters manufactured by
+	  AdvanSys. It is documented in the kernel source in
+	  <file:drivers/scsi/advansys.c>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called advansys.
+
+config SCSI_IN2000
+	tristate "Always IN2000 SCSI support"
+	depends on ISA && SCSI
+	help
+	  This is support for an ISA bus SCSI host adapter.  You'll find more
+	  information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
+	  out of the box, you may have to change the jumpers for IRQ or
+	  address selection.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called in2000.
+
+config SCSI_ARCMSR
+	tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
+	depends on PCI && SCSI
+	help
+	  This driver supports all of ARECA's SATA RAID controller cards.
+	  This is an ARECA-maintained driver by Erich Chen.
+	  If you have any problems, please mail to: < erich@areca.com.tw >
+	  Areca supports Linux RAID config tools.
+
+	  < http://www.areca.com.tw >
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called arcmsr (modprobe arcmsr).
+
+source "drivers/scsi/megaraid/Kconfig.megaraid"
+
+config SCSI_HPTIOP
+	tristate "HighPoint RocketRAID 3xxx Controller support"
+	depends on SCSI && PCI
+	help
+	  This option enables support for HighPoint RocketRAID 3xxx
+	  controllers.
+
+	  To compile this driver as a module, choose M here; the module
+	  will be called hptiop. If unsure, say N.
+
+config SCSI_BUSLOGIC
+	tristate "BusLogic SCSI support"
+	depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
+	---help---
+	  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
+	  Adapters. Consult the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>, and the files
+	  <file:Documentation/scsi/BusLogic.txt> and
+	  <file:Documentation/scsi/FlashPoint.txt> for more information.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called BusLogic.
+
+config SCSI_OMIT_FLASHPOINT
+	bool "Omit FlashPoint support"
+	depends on SCSI_BUSLOGIC
+	help
+	  This option allows you to omit the FlashPoint support from the
+	  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
+	  substantial, so users of MultiMaster Host Adapters may wish to omit
+	  it.
+
+config SCSI_DMX3191D
+	tristate "DMX3191D SCSI support"
+	depends on PCI && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is support for Domex DMX3191D SCSI Host Adapters.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called dmx3191d.
+
+config SCSI_DTC3280
+	tristate "DTC3180/3280 SCSI support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	select CHECK_SIGNATURE
+	help
+	  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
+	  the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>, and the file
+	  <file:Documentation/scsi/dtc3x80.txt>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called dtc.
+
+config SCSI_EATA
+	tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
+	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
+	---help---
+	  This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
+	  ISA and all EISA I/O addresses are probed looking for the "EATA"
+	  signature. The addresses of all the PCI SCSI controllers reported
+          by the PCI subsystem are probed as well.
+
+	  You want to read the start of <file:drivers/scsi/eata.c> and the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called eata.
+
+config SCSI_EATA_TAGGED_QUEUE
+	bool "enable tagged command queueing"
+	depends on SCSI_EATA
+	help
+	  This is a feature of SCSI-2 which improves performance: the host
+	  adapter can send several SCSI commands to a device's queue even if
+	  previous commands haven't finished yet.
+	  This is equivalent to the "eata=tc:y" boot option.
+
+config SCSI_EATA_LINKED_COMMANDS
+	bool "enable elevator sorting"
+	depends on SCSI_EATA
+	help
+	  This option enables elevator sorting for all probed SCSI disks and
+	  CD-ROMs. It definitely reduces the average seek distance when doing
+	  random seeks, but this does not necessarily result in a noticeable
+	  performance improvement: your mileage may vary...
+	  This is equivalent to the "eata=lc:y" boot option.
+
+config SCSI_EATA_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on SCSI_EATA
+	default "16"
+	help
+	  This specifies how many SCSI commands can be maximally queued for
+	  each probed SCSI device. You should reduce the default value of 16
+	  only if you have disks with buggy or limited tagged command support.
+	  Minimum is 2 and maximum is 62. This value is also the window size
+	  used by the elevator sorting option above. The effective value used
+	  by the driver for each probed SCSI device is reported at boot time.
+	  This is equivalent to the "eata=mq:8" boot option.
+
+config SCSI_EATA_PIO
+	tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
+	depends on (ISA || EISA || PCI) && SCSI && BROKEN
+	---help---
+	  This driver supports all EATA-PIO protocol compliant SCSI Host
+	  Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
+	  host adapters could also use this driver but are discouraged from
+	  doing so, since this driver only supports hard disks and lacks
+	  numerous features.  You might want to have a look at the SCSI-HOWTO,
+	  available from <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called eata_pio.
+
+config SCSI_FUTURE_DOMAIN
+	tristate "Future Domain 16xx SCSI/AHA-2920A support"
+	depends on (ISA || PCI) && SCSI
+	select CHECK_SIGNATURE
+	---help---
+	  This is support for Future Domain's 16-bit SCSI host adapters
+	  (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
+	  other adapters based on the Future Domain chipsets (Quantum
+	  ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
+	  It is explained in section 3.7 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
+	  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
+	  controller support"). This Future Domain driver works with the older
+	  Adaptec AHA-2920A boards with a Future Domain chip on them.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called fdomain.
+
+config SCSI_FD_MCS
+	tristate "Future Domain MCS-600/700 SCSI support"
+	depends on MCA_LEGACY && SCSI
+	---help---
+	  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
+	  Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
+	  is identical to the MCS 700 and hence also supported by this driver.
+	  This driver also supports the Reply SB16/SCSI card (the SCSI part).
+	  It supports multiple adapters in the same system.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called fd_mcs.
+
+config SCSI_GDTH
+	tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
+	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
+	---help---
+	  Formerly called GDT SCSI Disk Array Controller Support.
+
+	  This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 
+	  manufactured by Intel Corporation/ICP vortex GmbH. It is documented
+	  in the kernel source in <file:drivers/scsi/gdth.c> and
+	  <file:drivers/scsi/gdth.h.>
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called gdth.
+
+config SCSI_GENERIC_NCR5380
+	tristate "Generic NCR5380/53c400 SCSI PIO support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This is a driver for the old NCR 53c80 series of SCSI controllers
+	  on boards using PIO. Most boards such as the Trantor T130 fit this
+	  category, along with a large number of ISA 8bit controllers shipped
+	  for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
+	  you should select the specific driver for that card rather than
+	  generic 5380 support.
+
+	  It is explained in section 3.8 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/g_NCR5380.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called g_NCR5380.
+
+config SCSI_GENERIC_NCR5380_MMIO
+	tristate "Generic NCR5380/53c400 SCSI MMIO support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This is a driver for the old NCR 53c80 series of SCSI controllers
+	  on boards using memory mapped I/O. 
+	  It is explained in section 3.8 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/g_NCR5380.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called g_NCR5380_mmio.
+
+config SCSI_GENERIC_NCR53C400
+	bool "Enable NCR53c400 extensions"
+	depends on SCSI_GENERIC_NCR5380
+	help
+	  This enables certain optimizations for the NCR53c400 SCSI cards.
+	  You might as well try it out.  Note that this driver will only probe
+	  for the Trantor T130B in its default configuration; you might have
+	  to pass a command line option to the kernel at boot time if it does
+	  not detect your card.  See the file
+	  <file:Documentation/scsi/g_NCR5380.txt> for details.
+
+config SCSI_IBMMCA
+	tristate "IBMMCA SCSI support"
+	depends on MCA && SCSI
+	---help---
+	  This is support for the IBM SCSI adapter found in many of the PS/2
+	  series computers.  These machines have an MCA bus, so you need to
+	  answer Y to "MCA support" as well and read
+	  <file:Documentation/mca.txt>.
+
+	  If the adapter isn't found during boot (a common problem for models
+	  56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
+	  option, where <pun> is the id of the SCSI subsystem (usually 7, but
+	  if that doesn't work check your reference diskette).  Owners of
+	  model 95 with a LED-matrix-display can in addition activate some
+	  activity info like under OS/2, but more informative, by setting
+	  'ibmmcascsi=display' as an additional kernel parameter.  Try "man
+	  bootparam" or see the documentation of your boot loader about how to
+	  pass options to the kernel.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ibmmca.
+
+config IBMMCA_SCSI_ORDER_STANDARD
+	bool "Standard SCSI-order"
+	depends on SCSI_IBMMCA
+	---help---
+	  In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
+	  are assigned to the drive letters, starting with the lowest SCSI-id
+	  (physical number -- pun) to be drive C:, as seen from DOS and
+	  similar operating systems. When looking into papers describing the
+	  ANSI-SCSI-standard, this assignment of drives appears to be wrong.
+	  The SCSI-standard follows a hardware-hierarchy which says that id 7
+	  has the highest priority and id 0 the lowest. Therefore, the host
+	  adapters are still today everywhere placed as SCSI-id 7 by default.
+	  In the SCSI-standard, the drive letters express the priority of the
+	  disk. C: should be the hard disk, or a partition on it, with the
+	  highest priority. This must therefore be the disk with the highest
+	  SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
+	  original definition of the SCSI-standard as also industrial- and
+	  process-control-machines, like VME-CPUs running under realtime-OSes
+	  (e.g. LynxOS, OS9) do.
+
+	  If you like to run Linux on your MCA-machine with the same
+	  assignment of hard disks as seen from e.g. DOS or OS/2 on your
+	  machine, which is in addition conformant to the SCSI-standard, you
+	  must say Y here. This is also necessary for MCA-Linux users who want
+	  to keep downward compatibility to older releases of the
+	  IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
+	  June 1997).
+
+	  If you like to have the lowest SCSI-id assigned as drive C:, as
+	  modern SCSI-BIOSes do, which does not conform to the standard, but
+	  is widespread and common in the PC-world of today, you must say N
+	  here. If unsure, say Y.
+
+config IBMMCA_SCSI_DEV_RESET
+	bool "Reset SCSI-devices at boottime"
+	depends on SCSI_IBMMCA
+	---help---
+	  By default, SCSI-devices are reset when the machine is powered on.
+	  However, some devices exist, like special-control-devices,
+	  SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
+	  not reset when switched on. If you say Y here, each device connected
+	  to your SCSI-bus will be issued a reset-command after it has been
+	  probed, while the kernel is booting. This may cause problems with
+	  more modern devices, like hard disks, which do not appreciate these
+	  reset commands, and can cause your system to hang. So say Y only if
+	  you know that one of your older devices needs it; N is the safe
+	  answer.
+
+config SCSI_IPS
+	tristate "IBM ServeRAID support"
+	depends on PCI && SCSI
+	---help---
+	  This is support for the IBM ServeRAID hardware RAID controllers.
+	  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
+	  for more information.  If this driver does not work correctly
+	  without modification please contact the author by email at
+	  <ipslinux@adaptec.com>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ips.
+
+config SCSI_IBMVSCSI
+	tristate "IBM Virtual SCSI support"
+	depends on PPC_PSERIES || PPC_ISERIES
+	help
+	  This is the IBM POWER Virtual SCSI Client
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ibmvscsic.
+
+config SCSI_IBMVSCSIS
+	tristate "IBM Virtual SCSI Server support"
+	depends on PPC_PSERIES && SCSI_TGT && SCSI_SRP
+	help
+	  This is the SRP target driver for IBM pSeries virtual environments.
+
+	  The userspace component needed to initialize the driver and
+	  documentation can be found:
+
+	  http://stgt.berlios.de/
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ibmvstgt.
+
+config SCSI_INITIO
+	tristate "Initio 9100U(W) support"
+	depends on PCI && SCSI
+	help
+	  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
+	  read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called initio.
+
+config SCSI_INIA100
+	tristate "Initio INI-A100U2W support"
+	depends on PCI && SCSI
+	help
+	  This is support for the Initio INI-A100U2W SCSI host adapter.
+	  Please read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called a100u2w.
+
+config SCSI_PPA
+	tristate "IOMEGA parallel port (ppa - older drives)"
+	depends on SCSI && PARPORT_PC
+	---help---
+	  This driver supports older versions of IOMEGA's parallel port ZIP
+	  drive (a 100 MB removable media device).
+
+	  Note that you can say N here if you have the SCSI version of the ZIP
+	  drive: it will be supported automatically if you said Y to the
+	  generic "SCSI disk support", above.
+
+	  If you have the ZIP Plus drive or a more recent parallel port ZIP
+	  drive (if the supplied cable with the drive is labeled "AutoDetect")
+	  then you should say N here and Y to "IOMEGA parallel port (imm -
+	  newer drives)", below.
+
+	  For more information about this driver and how to use it you should
+	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
+	  the SCSI-HOWTO, which is available from
+	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
+	  you will still be able to use the parallel port for other tasks,
+	  such as a printer; it is safe to compile both drivers into the
+	  kernel.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ppa.
+
+config SCSI_IMM
+	tristate "IOMEGA parallel port (imm - newer drives)"
+	depends on SCSI && PARPORT_PC
+	---help---
+	  This driver supports newer versions of IOMEGA's parallel port ZIP
+	  drive (a 100 MB removable media device).
+
+	  Note that you can say N here if you have the SCSI version of the ZIP
+	  drive: it will be supported automatically if you said Y to the
+	  generic "SCSI disk support", above.
+
+	  If you have the ZIP Plus drive or a more recent parallel port ZIP
+	  drive (if the supplied cable with the drive is labeled "AutoDetect")
+	  then you should say Y here; if you have an older ZIP drive, say N
+	  here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
+
+	  For more information about this driver and how to use it you should
+	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
+	  the SCSI-HOWTO, which is available from
+	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
+	  you will still be able to use the parallel port for other tasks,
+	  such as a printer; it is safe to compile both drivers into the
+	  kernel.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called imm.
+
+config SCSI_IZIP_EPP16
+	bool "ppa/imm option - Use slow (but safe) EPP-16"
+	depends on SCSI_PPA || SCSI_IMM
+	---help---
+	  EPP (Enhanced Parallel Port) is a standard for parallel ports which
+	  allows them to act as expansion buses that can handle up to 64
+	  peripheral devices.
+
+	  Some parallel port chipsets are slower than their motherboard, and
+	  so we have to control the state of the chipset's FIFO queue every
+	  now and then to avoid data loss. This will be done if you say Y
+	  here.
+
+	  Generally, saying Y is the safe option and slows things down a bit.
+
+config SCSI_IZIP_SLOW_CTR
+	bool "ppa/imm option - Assume slow parport control register"
+	depends on SCSI_PPA || SCSI_IMM
+	help
+	  Some parallel ports are known to have excessive delays between
+	  changing the parallel port control register and good data being
+	  available on the parallel port data/status register. This option
+	  forces a small delay (1.0 usec to be exact) after changing the
+	  control register to let things settle out. Enabling this option may
+	  result in a big drop in performance but some very old parallel ports
+	  (found in 386 vintage machines) will not work properly.
+
+	  Generally, saying N is fine.
+
+config SCSI_NCR53C406A
+	tristate "NCR53c406a SCSI support"
+	depends on ISA && SCSI
+	help
+	  This is support for the NCR53c406a SCSI host adapter.  For user
+	  configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
+	  in the kernel source.  Also read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called NCR53c406.
+
+config SCSI_NCR_D700
+	tristate "NCR Dual 700 MCA SCSI support"
+	depends on MCA && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is a driver for the MicroChannel Dual 700 card produced by
+	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
+	  tries to negotiate sync and uses tag command queueing.
+
+	  Unless you have an NCR manufactured machine, the chances are that
+	  you do not have this SCSI card, so say N.
+
+config SCSI_LASI700
+	tristate "HP Lasi SCSI support for 53c700/710"
+	depends on GSC && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is a driver for the SCSI controller in the Lasi chip found in
+	  many PA-RISC workstations & servers.  If you do not know whether you
+	  have a Lasi chip, it is safe to say "Y" here.
+
+config SCSI_SNI_53C710
+	tristate "SNI RM SCSI support for 53c710"
+	depends on SNI_RM && SCSI
+	select SCSI_SPI_ATTRS
+	select 53C700_LE_ON_BE
+	help
+	  This is a driver for the onboard SCSI controller found in older
+	  SNI RM workstations & servers.
+
+config 53C700_LE_ON_BE
+	bool
+	depends on SCSI_LASI700
+	default y
+
+config SCSI_STEX
+	tristate "Promise SuperTrak EX Series support"
+	depends on PCI && SCSI
+	---help---
+	  This driver supports Promise SuperTrak EX series storage controllers.
+
+	  Promise provides Linux RAID configuration utility for these
+	  controllers. Please visit <http://www.promise.com> to download.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called stex.
+
+config 53C700_BE_BUS
+	bool
+	depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
+	default y
+
+config SCSI_SYM53C8XX_2
+	tristate "SYM53C8XX Version 2 SCSI support"
+	depends on PCI && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This driver supports the whole NCR53C8XX/SYM53C8XX family of
+	  PCI-SCSI controllers.  It also supports the subset of LSI53C10XX
+	  Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
+	  language.  It does not support LSI53C10XX Ultra-320 PCI-X SCSI
+	  controllers; you need to use the Fusion MPT driver for that.
+
+	  Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
+	  information.
+
+config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
+	int "DMA addressing mode"
+	depends on SCSI_SYM53C8XX_2
+	default "1"
+	---help---
+	  This option only applies to PCI-SCSI chips that are PCI DAC
+	  capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
+
+	  When set to 0, the driver will program the chip to only perform
+	  32-bit DMA.  When set to 1, the chip will be able to perform DMA
+	  to addresses up to 1TB.  When set to 2, the driver supports the
+	  full 64-bit DMA address range, but can only address 16 segments
+	  of 4 GB each.  This limits the total addressable range to 64 GB.
+
+	  Most machines with less than 4GB of memory should use a setting
+	  of 0 for best performance.  If your machine has 4GB of memory
+	  or more, you should set this option to 1 (the default).
+
+	  The still experimental value 2 (64 bit DMA addressing with 16
+	  x 4GB segments limitation) can be used on systems that require
+	  PCI address bits past bit 39 to be set for the addressing of
+	  memory using PCI DAC cycles.
+
+config SCSI_SYM53C8XX_DEFAULT_TAGS
+	int "Default tagged command queue depth"
+	depends on SCSI_SYM53C8XX_2
+	default "16"
+	help
+	  This is the default value of the command queue depth the
+	  driver will announce to the generic SCSI layer for devices
+	  that support tagged command queueing. This value can be changed
+	  from the boot command line.  This is a soft limit that cannot
+	  exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
+
+config SCSI_SYM53C8XX_MAX_TAGS
+	int "Maximum number of queued commands"
+	depends on SCSI_SYM53C8XX_2
+	default "64"
+	help
+	  This option allows you to specify the maximum number of commands
+	  that can be queued to any device, when tagged command queuing is
+	  possible. The driver supports up to 256 queued commands per device.
+	  This value is used as a compiled-in hard limit.
+
+config SCSI_SYM53C8XX_MMIO
+	bool "Use memory mapped IO"
+	depends on SCSI_SYM53C8XX_2
+	default y
+	help
+	  Memory mapped IO is faster than Port IO.  Most people should
+	  answer Y here, but some machines may have problems.  If you have
+	  to answer N here, please report the problem to the maintainer.
+
+config SCSI_IPR
+	tristate "IBM Power Linux RAID adapter support"
+	depends on PCI && SCSI && ATA
+	select FW_LOADER
+	---help---
+	  This driver supports the IBM Power Linux family RAID adapters.
+	  This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
+	  as IBM iSeries 5702, 5703, 5709, and 570A.
+
+config SCSI_IPR_TRACE
+	bool "enable driver internal trace"
+	depends on SCSI_IPR
+	default y
+	help
+	  If you say Y here, the driver will trace all commands issued
+	  to the adapter. Performance impact is minimal. Trace can be
+	  dumped using /sys/bus/class/scsi_host/hostXX/trace.
+
+config SCSI_IPR_DUMP
+	bool "enable adapter dump support"
+	depends on SCSI_IPR
+	default y
+	help
+	  If you say Y here, the driver will support adapter crash dump.
+	  If you enable this support, the iprdump daemon can be used
+	  to capture adapter failure analysis information.
+
+config SCSI_ZALON
+	tristate "Zalon SCSI support"
+	depends on GSC && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  The Zalon is a GSC/HSC bus interface chip that sits between the
+	  PA-RISC processor and the NCR 53c720 SCSI controller on C100,
+	  C110, J200, J210 and some D, K & R-class machines.  It's also
+	  used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
+	  Say Y here if you have one of these machines or cards.
+
+config SCSI_NCR_Q720
+	tristate "NCR Quad 720 MCA SCSI support"
+	depends on MCA && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is a driver for the MicroChannel Quad 720 card produced by
+	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
+	  tries to negotiate sync and uses tag command queueing.
+
+	  Unless you have an NCR manufactured machine, the chances are that
+	  you do not have this SCSI card, so say N.
+
+config SCSI_NCR53C8XX_DEFAULT_TAGS
+	int "default tagged command queue depth"
+	depends on SCSI_ZALON || SCSI_NCR_Q720
+	default "8"
+	---help---
+	  "Tagged command queuing" is a feature of SCSI-2 which improves
+	  performance: the host adapter can send several SCSI commands to a
+	  device's queue even if previous commands haven't finished yet.
+	  Because the device is intelligent, it can optimize its operations
+	  (like head positioning) based on its own request queue. Some SCSI
+	  devices don't implement this properly; if you want to disable this
+	  feature, enter 0 or 1 here (it doesn't matter which).
+
+	  The default value is 8 and should be supported by most hard disks.
+	  This value can be overridden from the boot command line using the
+	  'tags' option as follows (example):
+	  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
+	  4, set queue depth to 16 for target 2 and target 3 on controller 0
+	  and set queue depth to 10 for target 0 / lun 2 on controller 1.
+
+	  The normal answer therefore is to go with the default 8 and to use
+	  a boot command line option for devices that need to use a different
+	  command queue depth.
+
+	  There is no safe option other than using good SCSI devices.
+
+config SCSI_NCR53C8XX_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on SCSI_ZALON || SCSI_NCR_Q720
+	default "32"
+	---help---
+	  This option allows you to specify the maximum number of commands
+	  that can be queued to any device, when tagged command queuing is
+	  possible. The default value is 32. Minimum is 2, maximum is 64.
+	  Modern hard disks are able to support 64 tags and even more, but
+	  do not seem to be faster when more than 32 tags are being used.
+
+	  So, the normal answer here is to go with the default value 32 unless
+	  you are using very large hard disks with large cache (>= 1 MB) that
+	  are able to take advantage of more than 32 tagged commands.
+
+	  There is no safe option and the default answer is recommended.
+
+config SCSI_NCR53C8XX_SYNC
+	int "synchronous transfers frequency in MHz"
+	depends on SCSI_ZALON || SCSI_NCR_Q720
+	default "20"
+	---help---
+	  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
+	  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
+	  are respectively the maximum data transfer rates in mega-transfers
+	  per second for each class.  For example, a FAST-20 Wide 16 device is
+	  able to transfer data at 20 million 16 bit packets per second for a
+	  total rate of 40 MB/s.
+
+	  You may specify 0 if you want to only use asynchronous data
+	  transfers. This is the safest and slowest option. Otherwise, specify
+	  a value between 5 and 80, depending on the capability of your SCSI
+	  controller.  The higher the number, the faster the data transfer.
+	  Note that 80 should normally be ok since the driver decreases the
+	  value automatically according to the controller's capabilities.
+
+	  Your answer to this question is ignored for controllers with NVRAM,
+	  since the driver will get this information from the user set-up.  It
+	  also can be overridden using a boot setup option, as follows
+	  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
+	  for FAST-20 synchronous data transfer (20 mega-transfers per
+	  second).
+
+	  The normal answer therefore is not to go with the default but to
+	  select the maximum value 80 allowing the driver to use the maximum
+	  value supported by each controller. If this causes problems with
+	  your SCSI devices, you should come back and decrease the value.
+
+	  There is no safe option other than using good cabling, right
+	  terminations and SCSI conformant devices.
+
+config SCSI_NCR53C8XX_NO_DISCONNECT
+	bool "not allow targets to disconnect"
+	depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
+	help
+	  This option is only provided for safety if you suspect some SCSI
+	  device of yours to not support properly the target-disconnect
+	  feature. In that case, you would say Y here. In general however, to
+	  not allow targets to disconnect is not reasonable if there is more
+	  than 1 device on a SCSI bus. The normal answer therefore is N.
+
+config SCSI_MCA_53C9X
+	tristate "NCR MCA 53C9x SCSI support"
+	depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
+	help
+	  Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
+	  controller based on the NCR 53C94.  This driver will allow use of
+	  the controller on the 3550, and very possibly others.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mca_53c9x.
+
+config SCSI_PAS16
+	tristate "PAS16 SCSI support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This is support for a SCSI host adapter.  It is explained in section
+	  3.10 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/pas16.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called pas16.
+
+config SCSI_PSI240I
+	tristate "PSI240i support"
+	depends on ISA && SCSI
+	help
+	  This is support for the PSI240i EIDE interface card which acts as a
+	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called psi240i.
+
+config SCSI_QLOGIC_FAS
+	tristate "Qlogic FAS SCSI support"
+	depends on ISA && SCSI
+	---help---
+	  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
+	  FastSCSI! cards as well as any other card based on the FASXX chip
+	  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
+
+	  This driver does NOT support the PCI versions of these cards. The
+	  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
+	  SCSI support"), below.
+
+	  Information about this driver is contained in
+	  <file:Documentation/scsi/qlogicfas.txt>.  You should also read the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called qlogicfas.
+
+config SCSI_QLOGIC_FC_FIRMWARE
+	bool "Include loadable firmware in driver"
+	depends on SCSI_QLOGIC_FC
+  	help
+	  Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
+	  expanded LUN addressing and FcTape (FCP-2) support, in the
+	  qlogicfc driver. This is required on some platforms.
+
+config SCSI_QLOGIC_1280
+	tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
+	depends on PCI && SCSI
+	help
+	  Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called qla1280.
+
+config SCSI_QLOGICPTI
+	tristate "PTI Qlogic, ISP Driver"
+	depends on SBUS && SCSI
+	help
+	  This driver supports SBUS SCSI controllers from PTI or QLogic. These
+	  controllers are known under Solaris as qpti and in the openprom as
+	  PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
+	  driven by a different driver.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called qlogicpti.
+
+source "drivers/scsi/qla2xxx/Kconfig"
+source "drivers/scsi/qla4xxx/Kconfig"
+
+config SCSI_LPFC
+	tristate "Emulex LightPulse Fibre Channel Support"
+	depends on PCI && SCSI
+	select SCSI_FC_ATTRS
+	help
+          This lpfc driver supports the Emulex LightPulse
+          Family of Fibre Channel PCI host adapters.
+
+config SCSI_SEAGATE
+	tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
+	depends on X86 && ISA && SCSI
+	select CHECK_SIGNATURE
+	---help---
+	  These are 8-bit SCSI controllers; the ST-01 is also supported by
+	  this driver.  It is explained in section 3.9 of the SCSI-HOWTO,
+	  available from <http://www.tldp.org/docs.html#howto>.  If it
+	  doesn't work out of the box, you may have to change some macros at
+	  compiletime, which are described in <file:drivers/scsi/seagate.c>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called seagate.
+
+# definitely looks not 64bit safe:
+config SCSI_SIM710
+	tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
+	depends on (EISA || MCA) && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This driver for NCR53c710 based SCSI host adapters.
+
+	  It currently supports Compaq EISA cards and NCR MCA cards
+
+config SCSI_SYM53C416
+	tristate "Symbios 53c416 SCSI support"
+	depends on ISA && SCSI
+	---help---
+	  This is support for the sym53c416 SCSI host adapter, the SCSI
+	  adapter that comes with some HP scanners. This driver requires that
+	  the sym53c416 is configured first using some sort of PnP
+	  configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
+	  are using isapnp then you need to compile this driver as a module
+	  and then load it using insmod after isapnp has run. The parameters
+	  of the configured card(s) should be passed to the driver. The format
+	  is:
+
+	  insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called sym53c416.
+
+config SCSI_DC395x
+	tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
+	depends on PCI && SCSI && EXPERIMENTAL
+	---help---
+	  This driver supports PCI SCSI host adapters based on the ASIC
+	  TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
+
+	  This driver works, but is still in experimental status. So better
+	  have a bootable disk and a backup in case of emergency.
+
+	  Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called dc395x.
+
+config SCSI_DC390T
+	tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
+	depends on PCI && SCSI
+	---help---
+	  This driver supports PCI SCSI host adapters based on the Am53C974A
+	  chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
+	  PCscsi/PCnet (Am53/79C974) solutions.
+
+	  Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
+
+	  Note that this driver does NOT support Tekram DC390W/U/F, which are
+	  based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called tmscsim.
+
+config SCSI_T128
+	tristate "Trantor T128/T128F/T228 SCSI support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	select CHECK_SIGNATURE
+	---help---
+	  This is support for a SCSI host adapter. It is explained in section
+	  3.11 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
+	  Adaptec, and some former Trantor products are being sold under the
+	  Adaptec name.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called t128.
+
+config SCSI_U14_34F
+	tristate "UltraStor 14F/34F support"
+	depends on ISA && SCSI && ISA_DMA_API
+	---help---
+	  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
+	  The source at <file:drivers/scsi/u14-34f.c> contains some
+	  information about this hardware.  If the driver doesn't work out of
+	  the box, you may have to change some settings in
+	  <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  Note that there is also
+	  another driver for the same hardware: "UltraStor SCSI support",
+	  below.  You should say Y to both only if you want 24F support as
+	  well.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called u14-34f.
+
+config SCSI_U14_34F_TAGGED_QUEUE
+	bool "enable tagged command queueing"
+	depends on SCSI_U14_34F
+	help
+	  This is a feature of SCSI-2 which improves performance: the host
+	  adapter can send several SCSI commands to a device's queue even if
+	  previous commands haven't finished yet.
+	  This is equivalent to the "u14-34f=tc:y" boot option.
+
+config SCSI_U14_34F_LINKED_COMMANDS
+	bool "enable elevator sorting"
+	depends on SCSI_U14_34F
+	help
+	  This option enables elevator sorting for all probed SCSI disks and
+	  CD-ROMs. It definitely reduces the average seek distance when doing
+	  random seeks, but this does not necessarily result in a noticeable
+	  performance improvement: your mileage may vary...
+	  This is equivalent to the "u14-34f=lc:y" boot option.
+
+config SCSI_U14_34F_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on SCSI_U14_34F
+	default "8"
+	help
+	  This specifies how many SCSI commands can be maximally queued for
+	  each probed SCSI device. You should reduce the default value of 8
+	  only if you have disks with buggy or limited tagged command support.
+	  Minimum is 2 and maximum is 14. This value is also the window size
+	  used by the elevator sorting option above. The effective value used
+	  by the driver for each probed SCSI device is reported at boot time.
+	  This is equivalent to the "u14-34f=mq:8" boot option.
+
+config SCSI_ULTRASTOR
+	tristate "UltraStor SCSI support"
+	depends on X86 && ISA && SCSI
+	---help---
+	  This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
+	  adapter family.  This driver is explained in section 3.12 of the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/ultrastor.h>.
+
+	  Note that there is also another driver for the same hardware:
+	  "UltraStor 14F/34F support", above.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ultrastor.
+
+config SCSI_NSP32
+	tristate "Workbit NinjaSCSI-32Bi/UDE support"
+	depends on PCI && SCSI && !64BIT
+	help
+	  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
+	  SCSI host adapter. Please read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called nsp32.
+
+config SCSI_DEBUG
+	tristate "SCSI debugging host simulator"
+	depends on SCSI
+	help
+	  This is a host adapter simulator that can simulate multiple hosts
+	  each with multiple dummy SCSI devices (disks). It defaults to one
+	  host adapter with one dummy SCSI disk. Each dummy disk uses kernel
+	  RAM as storage (i.e. it is a ramdisk). To save space when multiple
+	  dummy disks are simulated, they share the same kernel RAM for 
+	  their storage. See <http://www.torque.net/sg/sdebug.html> for more
+	  information. This driver is primarily of use to those testing the
+	  SCSI and block subsystems. If unsure, say N.
+
+config SCSI_MESH
+	tristate "MESH (Power Mac internal SCSI) support"
+	depends on PPC32 && PPC_PMAC && SCSI
+	help
+	  Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
+	  SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
+	  other Power Macintoshes do). Say Y to include support for this SCSI
+	  adaptor.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mesh.
+
+config SCSI_MESH_SYNC_RATE
+	int "maximum synchronous transfer rate (MB/s) (0 = async)"
+	depends on SCSI_MESH
+	default "5"
+	help
+	  On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
+	  drives a bus which is entirely internal to the machine (such as the
+	  7500, 7600, 8500, etc.), the MESH is capable of synchronous
+	  operation at up to 10 MB/s. On machines where the SCSI bus
+	  controlled by the MESH can have external devices connected, it is
+	  usually rated at 5 MB/s. 5 is a safe value here unless you know the
+	  MESH SCSI bus is internal only; in that case you can say 10. Say 0
+	  to disable synchronous operation.
+
+config SCSI_MESH_RESET_DELAY_MS
+	int "initial bus reset delay (ms) (0 = no reset)"
+	depends on SCSI_MESH
+	default "4000"
+
+config SCSI_MAC53C94
+	tristate "53C94 (Power Mac external SCSI) support"
+	depends on PPC32 && PPC_PMAC && SCSI
+	help
+	  On Power Macintoshes (and clones) with two SCSI buses, the external
+	  SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
+	  machines which only have one SCSI bus, such as the 7200, also use
+	  the 53C94. Say Y to include support for the 53C94.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mac53c94.
+
+source "drivers/scsi/arm/Kconfig"
+
+config JAZZ_ESP
+	bool "MIPS JAZZ FAS216 SCSI support"
+	depends on MACH_JAZZ && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is the driver for the onboard SCSI host adapter of MIPS Magnum
+	  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
+	  systems.
+
+config A3000_SCSI
+	tristate "A3000 WD33C93A support"
+	depends on AMIGA && SCSI
+	help
+	  If you have an Amiga 3000 and have SCSI devices connected to the
+	  built-in SCSI controller, say Y. Otherwise, say N.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called a3000.
+
+config A2091_SCSI
+	tristate "A2091/A590 WD33C93A support"
+	depends on ZORRO && SCSI
+	help
+	  If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
+	  say N.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called a2091.
+
+config GVP11_SCSI
+	tristate "GVP Series II WD33C93A support"
+	depends on ZORRO && SCSI
+	---help---
+	  If you have a Great Valley Products Series II SCSI controller,
+	  answer Y. Also say Y if you have a later model of GVP SCSI
+	  controller (such as the GVP A4008 or a Combo board). Otherwise,
+	  answer N. This driver does NOT work for the T-Rex series of
+	  accelerators from TekMagic and GVP-M.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called gvp11.
+
+config CYBERSTORM_SCSI
+	tristate "CyberStorm SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga with an original (MkI) Phase5 Cyberstorm
+	  accelerator board and the optional Cyberstorm SCSI controller,
+	  answer Y. Otherwise, say N.
+
+config CYBERSTORMII_SCSI
+	tristate "CyberStorm Mk II SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
+	  and the optional Cyberstorm SCSI controller, say Y. Otherwise,
+	  answer N.
+
+config BLZ2060_SCSI
+	tristate "Blizzard 2060 SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
+	  and want to use the onboard SCSI controller, say Y. Otherwise,
+	  answer N.
+
+config BLZ1230_SCSI
+	tristate "Blizzard 1230IV/1260 SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
+	  1260 accelerator, and the optional SCSI module, say Y. Otherwise,
+	  say N.
+
+config FASTLANE_SCSI
+	tristate "Fastlane SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
+	  one in the near future, say Y to this question. Otherwise, say N.
+
+config SCSI_A4000T
+	tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
+	depends on AMIGA && SCSI && EXPERIMENTAL
+	select SCSI_SPI_ATTRS
+	help
+	  If you have an Amiga 4000T and have SCSI devices connected to the
+	  built-in SCSI controller, say Y. Otherwise, say N.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called a4000t.
+
+config SCSI_ZORRO7XX
+	tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
+	depends on ZORRO && SCSI && EXPERIMENTAL
+	select SCSI_SPI_ATTRS
+	help
+	  Support for various NCR53c710-based SCSI controllers on Zorro
+	  expansion boards for the Amiga.
+	  This includes:
+	    - the Amiga 4091 Zorro III SCSI-2 controller,
+	    - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
+	      (info at
+	      <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
+	    - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
+	      accelerator card for the Amiga 1200,
+	    - the SCSI controller on the GVP Turbo 040/060 accelerator.
+
+config OKTAGON_SCSI
+	tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
+	depends on ZORRO && SCSI && EXPERIMENTAL
+	help
+	  If you have the BSC Oktagon SCSI disk controller for the Amiga, say
+	  Y to this question.  If you're in doubt about whether you have one,
+	  see the picture at
+	  <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
+
+config ATARI_SCSI
+	tristate "Atari native SCSI support"
+	depends on ATARI && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  If you have an Atari with built-in NCR5380 SCSI controller (TT,
+	  Falcon, ...) say Y to get it supported. Of course also, if you have
+	  a compatible SCSI controller (e.g. for Medusa).
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called atari_scsi.
+
+	  This driver supports both styles of NCR integration into the
+	  system: the TT style (separate DMA), and the Falcon style (via
+	  ST-DMA, replacing ACSI).  It does NOT support other schemes, like
+	  in the Hades (without DMA).
+
+config ATARI_SCSI_TOSHIBA_DELAY
+	bool "Long delays for Toshiba CD-ROMs"
+	depends on ATARI_SCSI
+	help
+	  This option increases the delay after a SCSI arbitration to
+	  accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
+	  use a Toshiba CD-ROM drive; otherwise, the option is not needed and
+	  would impact performance a bit, so say N.
+
+config ATARI_SCSI_RESET_BOOT
+	bool "Reset SCSI-devices at boottime"
+	depends on ATARI_SCSI
+	help
+	  Reset the devices on your Atari whenever it boots.  This makes the
+	  boot process fractionally longer but may assist recovery from errors
+	  that leave the devices with SCSI operations partway completed.
+
+config TT_DMA_EMUL
+	bool "Hades SCSI DMA emulator"
+	depends on ATARI_SCSI && HADES
+	help
+	  This option enables code which emulates the TT SCSI DMA chip on the
+	  Hades. This increases the SCSI transfer rates at least ten times
+	  compared to PIO transfers.
+
+config MAC_SCSI
+	bool "Macintosh NCR5380 SCSI"
+	depends on MAC && SCSI=y
+	select SCSI_SPI_ATTRS
+	help
+	  This is the NCR 5380 SCSI controller included on most of the 68030
+	  based Macintoshes.  If you have one of these say Y and read the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+config SCSI_MAC_ESP
+	tristate "Macintosh NCR53c9[46] SCSI"
+	depends on MAC && SCSI
+	help
+	  This is the NCR 53c9x SCSI controller found on most of the 68040
+	  based Macintoshes.  If you have one of these say Y and read the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mac_esp.
+
+config MVME147_SCSI
+	bool "WD33C93 SCSI driver for MVME147"
+	depends on MVME147 && SCSI=y
+	select SCSI_SPI_ATTRS
+	help
+	  Support for the on-board SCSI controller on the Motorola MVME147
+	  single-board computer.
+
+config MVME16x_SCSI
+	tristate "NCR53C710 SCSI driver for MVME16x"
+	depends on MVME16x && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
+	  SCSI controller chip.  Almost everyone using one of these boards
+	  will want to say Y to this question.
+
+config BVME6000_SCSI
+	tristate "NCR53C710 SCSI driver for BVME6000"
+	depends on BVME6000 && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
+	  SCSI controller chip.  Almost everyone using one of these boards
+	  will want to say Y to this question.
+
+config SUN3_SCSI
+	tristate "Sun3 NCR5380 SCSI"
+	depends on SUN3 && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This option will enable support for the OBIO (onboard io) NCR5380
+	  SCSI controller found in the Sun 3/50 and 3/60, as well as for
+	  "Sun3" type VME scsi controllers also based on the NCR5380.
+	  General Linux information on the Sun 3 series (now discontinued)
+	  is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
+
+config SUN3X_ESP
+	bool "Sun3x ESP SCSI"
+	depends on SUN3X && SCSI=y
+	help
+	  The ESP was an on-board SCSI controller used on Sun 3/80
+	  machines.  Say Y here to compile in support for it.
+
+config SCSI_SUNESP
+	tristate "Sparc ESP Scsi Driver"
+	depends on SBUS && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is the driver for the Sun ESP SCSI host adapter. The ESP
+	  chipset is present in most SPARC SBUS-based computers.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called esp.
+
+config ZFCP
+	tristate "FCP host bus adapter driver for IBM eServer zSeries"
+	depends on S390 && QDIO && SCSI
+	select SCSI_FC_ATTRS
+	help
+          If you want to access SCSI devices attached to your IBM eServer
+          zSeries by means of Fibre Channel interfaces say Y.
+          For details please refer to the documentation provided by IBM at
+          <http://oss.software.ibm.com/developerworks/opensource/linux390>
+
+          This driver is also available as a module. This module will be
+          called zfcp. If you want to compile it as a module, say M here
+          and read <file:Documentation/kbuild/modules.txt>.
+
+config SCSI_SRP
+	tristate "SCSI RDMA Protocol helper library"
+	depends on SCSI && PCI
+	select SCSI_TGT
+	help
+	  If you wish to use SRP target drivers, say Y.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called libsrp.
+
+endif # SCSI_LOWLEVEL
+
+source "drivers/scsi/pcmcia/Kconfig"
+
+endmenu

-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

[PATCH] SCSI: trailing whitespace in Kconfig

[Stefan Richter]

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---

Applies after patch "SCSI: split Kconfig menu into two".
I didn't want to change whitespace in the portions that this patch
moved from drivers/scsi/Kconfig to drivers/scsi/Kconfig.lowlevel,
hence produced this follow-up.


 drivers/scsi/Kconfig.lowlevel |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

Index: linux-2.6.23-rc6/drivers/scsi/Kconfig.lowlevel
===================================================================
--- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig.lowlevel
+++ linux-2.6.23-rc6/drivers/scsi/Kconfig.lowlevel
@@ -252,7 +252,7 @@ config SCSI_DPT_I2O
 	tristate "Adaptec I2O RAID support "
 	depends on !64BIT && SCSI && PCI && VIRT_TO_BUS
 	help
-	  This driver supports all of Adaptec's I2O based RAID controllers as 
+	  This driver supports all of Adaptec's I2O based RAID controllers as
 	  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
 	  driver by Deanna Bonds.  See <file:Documentation/scsi/dpti.txt>.
 
@@ -457,7 +457,7 @@ config SCSI_GDTH
 	---help---
 	  Formerly called GDT SCSI Disk Array Controller Support.
 
-	  This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 
+	  This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
 	  manufactured by Intel Corporation/ICP vortex GmbH. It is documented
 	  in the kernel source in <file:drivers/scsi/gdth.c> and
 	  <file:drivers/scsi/gdth.h.>
@@ -491,7 +491,7 @@ config SCSI_GENERIC_NCR5380_MMIO
 	select SCSI_SPI_ATTRS
 	---help---
 	  This is a driver for the old NCR 53c80 series of SCSI controllers
-	  on boards using memory mapped I/O. 
+	  on boards using memory mapped I/O.
 	  It is explained in section 3.8 of the SCSI-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
 	  of the box, you may have to change some settings in
@@ -1261,7 +1261,7 @@ config SCSI_DEBUG
 	  each with multiple dummy SCSI devices (disks). It defaults to one
 	  host adapter with one dummy SCSI disk. Each dummy disk uses kernel
 	  RAM as storage (i.e. it is a ramdisk). To save space when multiple
-	  dummy disks are simulated, they share the same kernel RAM for 
+	  dummy disks are simulated, they share the same kernel RAM for
 	  their storage. See <http://www.torque.net/sg/sdebug.html> for more
 	  information. This driver is primarily of use to those testing the
 	  SCSI and block subsystems. If unsure, say N.

-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Sam Ravnborg]

Hi Stefan.

Such a patch really calls for some minimal unifacation among
the architectures.

> 
>  arch/alpha/Kconfig            |    2 
>  arch/arm/Kconfig              |    2 
>  arch/avr32/Kconfig            |    2 
>  arch/blackfin/Kconfig         |    2 
>  arch/cris/Kconfig             |    2 
>  arch/frv/Kconfig              |    2 
>  arch/i386/Kconfig             |    2 
>  arch/ia64/Kconfig             |    2 
>  arch/m32r/Kconfig             |    2 
>  arch/m68k/Kconfig             |    2 
>  arch/m68knommu/Kconfig        |    2 
>  arch/mips/Kconfig             |    2 
>  arch/parisc/Kconfig           |    2 
>  arch/powerpc/Kconfig          |    2 
>  arch/ppc/Kconfig              |    2 
>  arch/s390/Kconfig             |    2 
>  arch/sh/Kconfig               |    2 
>  arch/sh64/Kconfig             |    2 
>  arch/sparc/Kconfig            |    2 
>  arch/sparc64/Kconfig          |    2 
>  arch/um/Kconfig               |    2 
>  arch/v850/Kconfig             |    2 
>  arch/x86_64/Kconfig           |    4 
>  arch/xtensa/Kconfig           |    2 


Exactly the same change for all architectures.
IT would be good to introduce a common file that contains
some of the shared stuff from the different architectures.
We could start out simple with:

arch/Kconfig.arch:

source "net/Kconfig"
source "drivers/Kconfig"
source "fs/Kconfig"
source "security/Kconfig"
source "crypto/Kconfig"
source "lib/Kconfig"


And then source it in all relevant arch Kconfig files.
It is not all that can use it but most do.
A trivial task but one small step towards unification between
the architectures on the Kconfig level.

	Sam

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Adrian Bunk]

On Fri, Sep 14, 2007 at 09:00:33PM +0200, Sam Ravnborg wrote:
> Hi Stefan.
> 
> Such a patch really calls for some minimal unifacation among
> the architectures.
> 
> > 
> >  arch/alpha/Kconfig            |    2 
> >  arch/arm/Kconfig              |    2 
> >  arch/avr32/Kconfig            |    2 
> >  arch/blackfin/Kconfig         |    2 
> >  arch/cris/Kconfig             |    2 
> >  arch/frv/Kconfig              |    2 
> >  arch/i386/Kconfig             |    2 
> >  arch/ia64/Kconfig             |    2 
> >  arch/m32r/Kconfig             |    2 
> >  arch/m68k/Kconfig             |    2 
> >  arch/m68knommu/Kconfig        |    2 
> >  arch/mips/Kconfig             |    2 
> >  arch/parisc/Kconfig           |    2 
> >  arch/powerpc/Kconfig          |    2 
> >  arch/ppc/Kconfig              |    2 
> >  arch/s390/Kconfig             |    2 
> >  arch/sh/Kconfig               |    2 
> >  arch/sh64/Kconfig             |    2 
> >  arch/sparc/Kconfig            |    2 
> >  arch/sparc64/Kconfig          |    2 
> >  arch/um/Kconfig               |    2 
> >  arch/v850/Kconfig             |    2 
> >  arch/x86_64/Kconfig           |    4 
> >  arch/xtensa/Kconfig           |    2 
> 
> 
> Exactly the same change for all architectures.
> IT would be good to introduce a common file that contains
> some of the shared stuff from the different architectures.
> We could start out simple with:
> 
> arch/Kconfig.arch:
>...

Stefan simply shouldn't move it out of drivers/Kconfig.

> 	Sam

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Stefan Richter]

On 14 Sep, Adrian Bunk wrote:
> On Fri, Sep 14, 2007 at 09:00:33PM +0200, Sam Ravnborg wrote:
>> Hi Stefan.
>> 
>> Such a patch really calls for some minimal unifacation among
>> the architectures.
>> 
>> > 
>> >  arch/alpha/Kconfig            |    2 
>> >  arch/arm/Kconfig              |    2 
>> >  arch/avr32/Kconfig            |    2 
>> >  arch/blackfin/Kconfig         |    2 
>> >  arch/cris/Kconfig             |    2 
>> >  arch/frv/Kconfig              |    2 
>> >  arch/i386/Kconfig             |    2 
>> >  arch/ia64/Kconfig             |    2 
>> >  arch/m32r/Kconfig             |    2 
>> >  arch/m68k/Kconfig             |    2 
>> >  arch/m68knommu/Kconfig        |    2 
>> >  arch/mips/Kconfig             |    2 
>> >  arch/parisc/Kconfig           |    2 
>> >  arch/powerpc/Kconfig          |    2 
>> >  arch/ppc/Kconfig              |    2 
>> >  arch/s390/Kconfig             |    2 
>> >  arch/sh/Kconfig               |    2 
>> >  arch/sh64/Kconfig             |    2 
>> >  arch/sparc/Kconfig            |    2 
>> >  arch/sparc64/Kconfig          |    2 
>> >  arch/um/Kconfig               |    2 
>> >  arch/v850/Kconfig             |    2 
>> >  arch/x86_64/Kconfig           |    4 
>> >  arch/xtensa/Kconfig           |    2 
>> 
>> 
>> Exactly the same change for all architectures.
>> IT would be good to introduce a common file that contains
>> some of the shared stuff from the different architectures.
>> We could start out simple with:
>> 
>> arch/Kconfig.arch:
>>...

Yes, that would be good.  But Adrian has a point too.

> Stefan simply shouldn't move it out of drivers/Kconfig.


From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: SCSI: split Kconfig menu into two

The SCSI core and SCSI high-level drivers play a central role not just
for the whole lot of different SCSI Architecture types of hardware and
protocols, but also for subsystems which drive non SCSI hardware,
especially libata.

Hence the options pertaining to SCSI core and high-level are separated
out into an own top-level menu outside the "Device Drivers" submenu, and
some prompts are reworded.

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---
 drivers/Kconfig               |    4 
 drivers/scsi/Kconfig          | 1589 ----------------------------------
 drivers/scsi/Kconfig.lowlevel | 1578 +++++++++++++++++++++++++++++++++
 3 files changed, 1588 insertions(+), 1583 deletions(-)

Index: linux-2.6.23-rc6/drivers/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/drivers/Kconfig
+++ linux-2.6.23-rc6/drivers/Kconfig
@@ -1,5 +1,7 @@
 # drivers/Kconfig
 
+source "drivers/scsi/Kconfig"
+
 menu "Device Drivers"
 
 source "drivers/base/Kconfig"
@@ -22,7 +24,7 @@ source "drivers/misc/Kconfig"
 
 source "drivers/ide/Kconfig"
 
-source "drivers/scsi/Kconfig"
+source "drivers/scsi/Kconfig.lowlevel"
 
 source "drivers/ata/Kconfig"
 
Index: linux-2.6.23-rc6/drivers/scsi/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig
+++ linux-2.6.23-rc6/drivers/scsi/Kconfig
@@ -1,14 +1,7 @@
-menu "SCSI device support"
-
-config RAID_ATTRS
-	tristate "RAID Transport Class"
-	default n
-	depends on BLOCK
-	---help---
-	  Provides RAID
+menu "Storage (core and SCSI commands)"
 
 config SCSI
-	tristate "SCSI device support"
+	tristate "Storage support (core and SCSI commands)"
 	depends on BLOCK
 	select SCSI_DMA if HAS_DMA
 	---help---
@@ -42,13 +35,6 @@ config SCSI_DMA
 	bool
 	default n
 
-config SCSI_TGT
-	tristate "SCSI target support"
-	depends on SCSI && EXPERIMENTAL
-	---help---
-	  If you want to use SCSI target mode drivers enable this option.
-	  If you choose M, the module will be called scsi_tgt.
-
 config SCSI_NETLINK
 	bool
 	default	n
@@ -65,11 +51,11 @@ config SCSI_PROC_FS
 
 	  If unsure say Y.
 
-comment "SCSI support type (disk, tape, CD-ROM)"
+comment "SCSI command set drivers (disk, tape, CD-ROM)"
 	depends on SCSI
 
 config BLK_DEV_SD
-	tristate "SCSI disk support"
+	tristate "Harddisks and other Direct access devices"
 	depends on SCSI
 	---help---
 	  If you want to use SCSI hard disks, Fibre Channel disks,
@@ -90,7 +76,7 @@ config BLK_DEV_SD
 	  (below) as a module either.
 
 config CHR_DEV_ST
-	tristate "SCSI tape support"
+	tristate "Tape drives"
 	depends on SCSI
 	---help---
 	  If you want to use a SCSI tape drive under Linux, say Y and read the
@@ -125,7 +111,7 @@ config CHR_DEV_OSST
 	  <file:Documentation/scsi/scsi.txt>. The module will be called osst.
 
 config BLK_DEV_SR
-	tristate "SCSI CDROM support"
+	tristate "CD-ROMs, DVD-ROMs"
 	depends on SCSI
 	---help---
 	  If you want to use a SCSI, SATA, USB or FireWire CD-ROM or DVD-ROM,
@@ -261,1565 +247,4 @@ config SCSI_WAIT_SCAN
 	depends on SCSI
 	depends on MODULES
 
-menu "SCSI Transports"
-	depends on SCSI
-
-config SCSI_SPI_ATTRS
-	tristate "Parallel SCSI (SPI) Transport Attributes"
-	depends on SCSI
-	help
-	  If you wish to export transport-specific information about
-	  each attached SCSI device to sysfs, say Y.  Otherwise, say N.
-
-config SCSI_FC_ATTRS
-	tristate "FiberChannel Transport Attributes"
-	depends on SCSI
-	select SCSI_NETLINK
-	help
-	  If you wish to export transport-specific information about
-	  each attached FiberChannel device to sysfs, say Y.
-	  Otherwise, say N.
-
-config SCSI_ISCSI_ATTRS
-	tristate "iSCSI Transport Attributes"
-	depends on SCSI && NET
-	help
-	  If you wish to export transport-specific information about
-	  each attached iSCSI device to sysfs, say Y.
-	  Otherwise, say N.
-
-config SCSI_SAS_ATTRS
-	tristate "SAS Transport Attributes"
-	depends on SCSI && BLK_DEV_BSG
-	help
-	  If you wish to export transport-specific information about
-	  each attached SAS device to sysfs, say Y.
-
-source "drivers/scsi/libsas/Kconfig"
-
-endmenu
-
-menuconfig SCSI_LOWLEVEL
-	bool "SCSI low-level drivers"
-	depends on SCSI!=n
-	default y
-
-if SCSI_LOWLEVEL
-
-config ISCSI_TCP
-	tristate "iSCSI Initiator over TCP/IP"
-	depends on SCSI && INET
-	select CRYPTO
-	select CRYPTO_MD5
-	select CRYPTO_CRC32C
-	select SCSI_ISCSI_ATTRS
-	help
-	 The iSCSI Driver provides a host with the ability to access storage
-	 through an IP network. The driver uses the iSCSI protocol to transport
-	 SCSI requests and responses over a TCP/IP network between the host
-	 (the "initiator") and "targets".  Architecturally, the iSCSI driver
-	 combines with the host's TCP/IP stack, network drivers, and Network
-	 Interface Card (NIC) to provide the same functions as a SCSI or a
-	 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
-
-	 To compile this driver as a module, choose M here: the
-	 module will be called iscsi_tcp.
-
-	 The userspace component needed to initialize the driver, documentation,
-	 and sample configuration files can be found here:
-
-	 http://linux-iscsi.sf.net
-
-config SGIWD93_SCSI
-	tristate "SGI WD93C93 SCSI Driver"
-	depends on SGI_IP22 && SCSI
-  	help
-	  If you have a Western Digital WD93 SCSI controller on
-	  an SGI MIPS system, say Y.  Otherwise, say N.
-
-config SCSI_DECNCR
-	tristate "DEC NCR53C94 Scsi Driver"
-	depends on MACH_DECSTATION && SCSI && TC
-	help
-	  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
-	  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
-
-config SCSI_DECSII
-	tristate "DEC SII Scsi Driver"
-	depends on MACH_DECSTATION && SCSI && 32BIT
-
-config BLK_DEV_3W_XXXX_RAID
-	tristate "3ware 5/6/7/8xxx ATA-RAID support"
-	depends on PCI && SCSI
-	help
-	  3ware is the only hardware ATA-Raid product in Linux to date.
-	  This card is 2,4, or 8 channel master mode support only.
-	  SCSI support required!!!
-
-	  <http://www.3ware.com/>
-
-	  Please read the comments at the top of
-	  <file:drivers/scsi/3w-xxxx.c>.
-
-config SCSI_3W_9XXX
-	tristate "3ware 9xxx SATA-RAID support"
-	depends on PCI && SCSI
-	help
-	  This driver supports the 9000 series 3ware SATA-RAID cards.
-
-	  <http://www.amcc.com>
-
-	  Please read the comments at the top of
-	  <file:drivers/scsi/3w-9xxx.c>.
-
-config SCSI_7000FASST
-	tristate "7000FASST SCSI support"
-	depends on ISA && SCSI && ISA_DMA_API
-	select CHECK_SIGNATURE
-	help
-	  This driver supports the Western Digital 7000 SCSI host adapter
-	  family.  Some information is in the source:
-	  <file:drivers/scsi/wd7000.c>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called wd7000.
-
-config SCSI_ACARD
-	tristate "ACARD SCSI support"
-	depends on PCI && SCSI
-	help
-	  This driver supports the ACARD SCSI host adapter.
-	  Support Chip <ATP870 ATP876 ATP880 ATP885>
-	  To compile this driver as a module, choose M here: the
-	  module will be called atp870u.
-
-config SCSI_AHA152X
-	tristate "Adaptec AHA152X/2825 support"
-	depends on ISA && SCSI && !64BIT
-	select SCSI_SPI_ATTRS
-	select CHECK_SIGNATURE
-	---help---
-	  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
-	  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
-	  must be manually specified in this case.
-
-	  It is explained in section 3.3 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>. You might also want to
-	  read the file <file:Documentation/scsi/aha152x.txt>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called aha152x.
-
-config SCSI_AHA1542
-	tristate "Adaptec AHA1542 support"
-	depends on ISA && SCSI && ISA_DMA_API
-	---help---
-	  This is support for a SCSI host adapter.  It is explained in section
-	  3.4 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
-	  purchased by Adaptec, and some former Trantor products are being
-	  sold under the Adaptec name.  If it doesn't work out of the box, you
-	  may have to change some settings in <file:drivers/scsi/aha1542.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called aha1542.
-
-config SCSI_AHA1740
-	tristate "Adaptec AHA1740 support"
-	depends on EISA && SCSI
-	---help---
-	  This is support for a SCSI host adapter.  It is explained in section
-	  3.5 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/aha1740.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called aha1740.
-
-config SCSI_AACRAID
-	tristate "Adaptec AACRAID support"
-	depends on SCSI && PCI
-	help
-	  This driver supports a variety of Dell, HP, Adaptec, IBM and
-	  ICP storage products. For a list of supported products, refer
-	  to <file:Documentation/scsi/aacraid.txt>.
-
-	  To compile this driver as a module, choose M here: the module
-	  will be called aacraid.
-
-
-source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
-
-config SCSI_AIC7XXX_OLD
-	tristate "Adaptec AIC7xxx support (old driver)"
-	depends on (ISA || EISA || PCI ) && SCSI
-	help
-	  WARNING This driver is an older aic7xxx driver and is no longer
-	  under active development.  Adaptec, Inc. is writing a new driver to
-	  take the place of this one, and it is recommended that whenever
-	  possible, people should use the new Adaptec written driver instead
-	  of this one.  This driver will eventually be phased out entirely.
-
-	  This is support for the various aic7xxx based Adaptec SCSI
-	  controllers. These include the 274x EISA cards; 284x VLB cards;
-	  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
-	  motherboard based SCSI controllers from Adaptec. It does not support
-	  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
-	  support them. It does not support the 2920 cards from Adaptec that
-	  use the Future Domain SCSI controller chip. For those cards, you
-	  need the "Future Domain 16xx SCSI support" driver.
-
-	  In general, if the controller is based on an Adaptec SCSI controller
-	  chip from the aic777x series or the aic78xx series, this driver
-	  should work. The only exception is the 7810 which is specifically
-	  not supported (that's the RAID controller chip on the AAA-13x
-	  cards).
-
-	  Note that the AHA2920 SCSI host adapter is *not* supported by this
-	  driver; choose "Future Domain 16xx SCSI support" instead if you have
-	  one of those.
-
-	  Information on the configuration options for this controller can be
-	  found by checking the help file for each of the available
-	  configuration options. You should read
-	  <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
-	  contacting the maintainer with any questions.  The SCSI-HOWTO,
-	  available from <http://www.tldp.org/docs.html#howto>, can also
-	  be of great help.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called aic7xxx_old.
-
-source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
-source "drivers/scsi/aic94xx/Kconfig"
-
-# All the I2O code and drivers do not seem to be 64bit safe.
-config SCSI_DPT_I2O
-	tristate "Adaptec I2O RAID support "
-	depends on !64BIT && SCSI && PCI && VIRT_TO_BUS
-	help
-	  This driver supports all of Adaptec's I2O based RAID controllers as 
-	  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
-	  driver by Deanna Bonds.  See <file:Documentation/scsi/dpti.txt>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called dpt_i2o.
-
-config SCSI_ADVANSYS
-	tristate "AdvanSys SCSI support"
-	depends on SCSI
-	depends on ISA || EISA || PCI
-	depends on BROKEN || X86_32
-	help
-	  This is a driver for all SCSI host adapters manufactured by
-	  AdvanSys. It is documented in the kernel source in
-	  <file:drivers/scsi/advansys.c>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called advansys.
-
-config SCSI_IN2000
-	tristate "Always IN2000 SCSI support"
-	depends on ISA && SCSI
-	help
-	  This is support for an ISA bus SCSI host adapter.  You'll find more
-	  information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
-	  out of the box, you may have to change the jumpers for IRQ or
-	  address selection.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called in2000.
-
-config SCSI_ARCMSR
-	tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
-	depends on PCI && SCSI
-	help
-	  This driver supports all of ARECA's SATA RAID controller cards.
-	  This is an ARECA-maintained driver by Erich Chen.
-	  If you have any problems, please mail to: < erich@areca.com.tw >
-	  Areca supports Linux RAID config tools.
-
-	  < http://www.areca.com.tw >
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called arcmsr (modprobe arcmsr).
-
-source "drivers/scsi/megaraid/Kconfig.megaraid"
-
-config SCSI_HPTIOP
-	tristate "HighPoint RocketRAID 3xxx Controller support"
-	depends on SCSI && PCI
-	help
-	  This option enables support for HighPoint RocketRAID 3xxx
-	  controllers.
-
-	  To compile this driver as a module, choose M here; the module
-	  will be called hptiop. If unsure, say N.
-
-config SCSI_BUSLOGIC
-	tristate "BusLogic SCSI support"
-	depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
-	---help---
-	  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
-	  Adapters. Consult the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>, and the files
-	  <file:Documentation/scsi/BusLogic.txt> and
-	  <file:Documentation/scsi/FlashPoint.txt> for more information.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called BusLogic.
-
-config SCSI_OMIT_FLASHPOINT
-	bool "Omit FlashPoint support"
-	depends on SCSI_BUSLOGIC
-	help
-	  This option allows you to omit the FlashPoint support from the
-	  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
-	  substantial, so users of MultiMaster Host Adapters may wish to omit
-	  it.
-
-config SCSI_DMX3191D
-	tristate "DMX3191D SCSI support"
-	depends on PCI && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is support for Domex DMX3191D SCSI Host Adapters.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called dmx3191d.
-
-config SCSI_DTC3280
-	tristate "DTC3180/3280 SCSI support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	select CHECK_SIGNATURE
-	help
-	  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
-	  the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>, and the file
-	  <file:Documentation/scsi/dtc3x80.txt>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called dtc.
-
-config SCSI_EATA
-	tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
-	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
-	---help---
-	  This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
-	  ISA and all EISA I/O addresses are probed looking for the "EATA"
-	  signature. The addresses of all the PCI SCSI controllers reported
-          by the PCI subsystem are probed as well.
-
-	  You want to read the start of <file:drivers/scsi/eata.c> and the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called eata.
-
-config SCSI_EATA_TAGGED_QUEUE
-	bool "enable tagged command queueing"
-	depends on SCSI_EATA
-	help
-	  This is a feature of SCSI-2 which improves performance: the host
-	  adapter can send several SCSI commands to a device's queue even if
-	  previous commands haven't finished yet.
-	  This is equivalent to the "eata=tc:y" boot option.
-
-config SCSI_EATA_LINKED_COMMANDS
-	bool "enable elevator sorting"
-	depends on SCSI_EATA
-	help
-	  This option enables elevator sorting for all probed SCSI disks and
-	  CD-ROMs. It definitely reduces the average seek distance when doing
-	  random seeks, but this does not necessarily result in a noticeable
-	  performance improvement: your mileage may vary...
-	  This is equivalent to the "eata=lc:y" boot option.
-
-config SCSI_EATA_MAX_TAGS
-	int "maximum number of queued commands"
-	depends on SCSI_EATA
-	default "16"
-	help
-	  This specifies how many SCSI commands can be maximally queued for
-	  each probed SCSI device. You should reduce the default value of 16
-	  only if you have disks with buggy or limited tagged command support.
-	  Minimum is 2 and maximum is 62. This value is also the window size
-	  used by the elevator sorting option above. The effective value used
-	  by the driver for each probed SCSI device is reported at boot time.
-	  This is equivalent to the "eata=mq:8" boot option.
-
-config SCSI_EATA_PIO
-	tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
-	depends on (ISA || EISA || PCI) && SCSI && BROKEN
-	---help---
-	  This driver supports all EATA-PIO protocol compliant SCSI Host
-	  Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
-	  host adapters could also use this driver but are discouraged from
-	  doing so, since this driver only supports hard disks and lacks
-	  numerous features.  You might want to have a look at the SCSI-HOWTO,
-	  available from <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called eata_pio.
-
-config SCSI_FUTURE_DOMAIN
-	tristate "Future Domain 16xx SCSI/AHA-2920A support"
-	depends on (ISA || PCI) && SCSI
-	select CHECK_SIGNATURE
-	---help---
-	  This is support for Future Domain's 16-bit SCSI host adapters
-	  (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
-	  other adapters based on the Future Domain chipsets (Quantum
-	  ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
-	  It is explained in section 3.7 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
-	  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
-	  controller support"). This Future Domain driver works with the older
-	  Adaptec AHA-2920A boards with a Future Domain chip on them.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called fdomain.
-
-config SCSI_FD_MCS
-	tristate "Future Domain MCS-600/700 SCSI support"
-	depends on MCA_LEGACY && SCSI
-	---help---
-	  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
-	  Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
-	  is identical to the MCS 700 and hence also supported by this driver.
-	  This driver also supports the Reply SB16/SCSI card (the SCSI part).
-	  It supports multiple adapters in the same system.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called fd_mcs.
-
-config SCSI_GDTH
-	tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
-	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
-	---help---
-	  Formerly called GDT SCSI Disk Array Controller Support.
-
-	  This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 
-	  manufactured by Intel Corporation/ICP vortex GmbH. It is documented
-	  in the kernel source in <file:drivers/scsi/gdth.c> and
-	  <file:drivers/scsi/gdth.h.>
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called gdth.
-
-config SCSI_GENERIC_NCR5380
-	tristate "Generic NCR5380/53c400 SCSI PIO support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This is a driver for the old NCR 53c80 series of SCSI controllers
-	  on boards using PIO. Most boards such as the Trantor T130 fit this
-	  category, along with a large number of ISA 8bit controllers shipped
-	  for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
-	  you should select the specific driver for that card rather than
-	  generic 5380 support.
-
-	  It is explained in section 3.8 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/g_NCR5380.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called g_NCR5380.
-
-config SCSI_GENERIC_NCR5380_MMIO
-	tristate "Generic NCR5380/53c400 SCSI MMIO support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This is a driver for the old NCR 53c80 series of SCSI controllers
-	  on boards using memory mapped I/O. 
-	  It is explained in section 3.8 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/g_NCR5380.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called g_NCR5380_mmio.
-
-config SCSI_GENERIC_NCR53C400
-	bool "Enable NCR53c400 extensions"
-	depends on SCSI_GENERIC_NCR5380
-	help
-	  This enables certain optimizations for the NCR53c400 SCSI cards.
-	  You might as well try it out.  Note that this driver will only probe
-	  for the Trantor T130B in its default configuration; you might have
-	  to pass a command line option to the kernel at boot time if it does
-	  not detect your card.  See the file
-	  <file:Documentation/scsi/g_NCR5380.txt> for details.
-
-config SCSI_IBMMCA
-	tristate "IBMMCA SCSI support"
-	depends on MCA && SCSI
-	---help---
-	  This is support for the IBM SCSI adapter found in many of the PS/2
-	  series computers.  These machines have an MCA bus, so you need to
-	  answer Y to "MCA support" as well and read
-	  <file:Documentation/mca.txt>.
-
-	  If the adapter isn't found during boot (a common problem for models
-	  56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
-	  option, where <pun> is the id of the SCSI subsystem (usually 7, but
-	  if that doesn't work check your reference diskette).  Owners of
-	  model 95 with a LED-matrix-display can in addition activate some
-	  activity info like under OS/2, but more informative, by setting
-	  'ibmmcascsi=display' as an additional kernel parameter.  Try "man
-	  bootparam" or see the documentation of your boot loader about how to
-	  pass options to the kernel.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ibmmca.
-
-config IBMMCA_SCSI_ORDER_STANDARD
-	bool "Standard SCSI-order"
-	depends on SCSI_IBMMCA
-	---help---
-	  In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
-	  are assigned to the drive letters, starting with the lowest SCSI-id
-	  (physical number -- pun) to be drive C:, as seen from DOS and
-	  similar operating systems. When looking into papers describing the
-	  ANSI-SCSI-standard, this assignment of drives appears to be wrong.
-	  The SCSI-standard follows a hardware-hierarchy which says that id 7
-	  has the highest priority and id 0 the lowest. Therefore, the host
-	  adapters are still today everywhere placed as SCSI-id 7 by default.
-	  In the SCSI-standard, the drive letters express the priority of the
-	  disk. C: should be the hard disk, or a partition on it, with the
-	  highest priority. This must therefore be the disk with the highest
-	  SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
-	  original definition of the SCSI-standard as also industrial- and
-	  process-control-machines, like VME-CPUs running under realtime-OSes
-	  (e.g. LynxOS, OS9) do.
-
-	  If you like to run Linux on your MCA-machine with the same
-	  assignment of hard disks as seen from e.g. DOS or OS/2 on your
-	  machine, which is in addition conformant to the SCSI-standard, you
-	  must say Y here. This is also necessary for MCA-Linux users who want
-	  to keep downward compatibility to older releases of the
-	  IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
-	  June 1997).
-
-	  If you like to have the lowest SCSI-id assigned as drive C:, as
-	  modern SCSI-BIOSes do, which does not conform to the standard, but
-	  is widespread and common in the PC-world of today, you must say N
-	  here. If unsure, say Y.
-
-config IBMMCA_SCSI_DEV_RESET
-	bool "Reset SCSI-devices at boottime"
-	depends on SCSI_IBMMCA
-	---help---
-	  By default, SCSI-devices are reset when the machine is powered on.
-	  However, some devices exist, like special-control-devices,
-	  SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
-	  not reset when switched on. If you say Y here, each device connected
-	  to your SCSI-bus will be issued a reset-command after it has been
-	  probed, while the kernel is booting. This may cause problems with
-	  more modern devices, like hard disks, which do not appreciate these
-	  reset commands, and can cause your system to hang. So say Y only if
-	  you know that one of your older devices needs it; N is the safe
-	  answer.
-
-config SCSI_IPS
-	tristate "IBM ServeRAID support"
-	depends on PCI && SCSI
-	---help---
-	  This is support for the IBM ServeRAID hardware RAID controllers.
-	  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
-	  for more information.  If this driver does not work correctly
-	  without modification please contact the author by email at
-	  <ipslinux@adaptec.com>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ips.
-
-config SCSI_IBMVSCSI
-	tristate "IBM Virtual SCSI support"
-	depends on PPC_PSERIES || PPC_ISERIES
-	help
-	  This is the IBM POWER Virtual SCSI Client
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ibmvscsic.
-
-config SCSI_IBMVSCSIS
-	tristate "IBM Virtual SCSI Server support"
-	depends on PPC_PSERIES && SCSI_TGT && SCSI_SRP
-	help
-	  This is the SRP target driver for IBM pSeries virtual environments.
-
-	  The userspace component needed to initialize the driver and
-	  documentation can be found:
-
-	  http://stgt.berlios.de/
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ibmvstgt.
-
-config SCSI_INITIO
-	tristate "Initio 9100U(W) support"
-	depends on PCI && SCSI
-	help
-	  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
-	  read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called initio.
-
-config SCSI_INIA100
-	tristate "Initio INI-A100U2W support"
-	depends on PCI && SCSI
-	help
-	  This is support for the Initio INI-A100U2W SCSI host adapter.
-	  Please read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called a100u2w.
-
-config SCSI_PPA
-	tristate "IOMEGA parallel port (ppa - older drives)"
-	depends on SCSI && PARPORT_PC
-	---help---
-	  This driver supports older versions of IOMEGA's parallel port ZIP
-	  drive (a 100 MB removable media device).
-
-	  Note that you can say N here if you have the SCSI version of the ZIP
-	  drive: it will be supported automatically if you said Y to the
-	  generic "SCSI disk support", above.
-
-	  If you have the ZIP Plus drive or a more recent parallel port ZIP
-	  drive (if the supplied cable with the drive is labeled "AutoDetect")
-	  then you should say N here and Y to "IOMEGA parallel port (imm -
-	  newer drives)", below.
-
-	  For more information about this driver and how to use it you should
-	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
-	  the SCSI-HOWTO, which is available from
-	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
-	  you will still be able to use the parallel port for other tasks,
-	  such as a printer; it is safe to compile both drivers into the
-	  kernel.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ppa.
-
-config SCSI_IMM
-	tristate "IOMEGA parallel port (imm - newer drives)"
-	depends on SCSI && PARPORT_PC
-	---help---
-	  This driver supports newer versions of IOMEGA's parallel port ZIP
-	  drive (a 100 MB removable media device).
-
-	  Note that you can say N here if you have the SCSI version of the ZIP
-	  drive: it will be supported automatically if you said Y to the
-	  generic "SCSI disk support", above.
-
-	  If you have the ZIP Plus drive or a more recent parallel port ZIP
-	  drive (if the supplied cable with the drive is labeled "AutoDetect")
-	  then you should say Y here; if you have an older ZIP drive, say N
-	  here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
-
-	  For more information about this driver and how to use it you should
-	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
-	  the SCSI-HOWTO, which is available from
-	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
-	  you will still be able to use the parallel port for other tasks,
-	  such as a printer; it is safe to compile both drivers into the
-	  kernel.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called imm.
-
-config SCSI_IZIP_EPP16
-	bool "ppa/imm option - Use slow (but safe) EPP-16"
-	depends on SCSI_PPA || SCSI_IMM
-	---help---
-	  EPP (Enhanced Parallel Port) is a standard for parallel ports which
-	  allows them to act as expansion buses that can handle up to 64
-	  peripheral devices.
-
-	  Some parallel port chipsets are slower than their motherboard, and
-	  so we have to control the state of the chipset's FIFO queue every
-	  now and then to avoid data loss. This will be done if you say Y
-	  here.
-
-	  Generally, saying Y is the safe option and slows things down a bit.
-
-config SCSI_IZIP_SLOW_CTR
-	bool "ppa/imm option - Assume slow parport control register"
-	depends on SCSI_PPA || SCSI_IMM
-	help
-	  Some parallel ports are known to have excessive delays between
-	  changing the parallel port control register and good data being
-	  available on the parallel port data/status register. This option
-	  forces a small delay (1.0 usec to be exact) after changing the
-	  control register to let things settle out. Enabling this option may
-	  result in a big drop in performance but some very old parallel ports
-	  (found in 386 vintage machines) will not work properly.
-
-	  Generally, saying N is fine.
-
-config SCSI_NCR53C406A
-	tristate "NCR53c406a SCSI support"
-	depends on ISA && SCSI
-	help
-	  This is support for the NCR53c406a SCSI host adapter.  For user
-	  configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
-	  in the kernel source.  Also read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called NCR53c406.
-
-config SCSI_NCR_D700
-	tristate "NCR Dual 700 MCA SCSI support"
-	depends on MCA && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is a driver for the MicroChannel Dual 700 card produced by
-	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
-	  tries to negotiate sync and uses tag command queueing.
-
-	  Unless you have an NCR manufactured machine, the chances are that
-	  you do not have this SCSI card, so say N.
-
-config SCSI_LASI700
-	tristate "HP Lasi SCSI support for 53c700/710"
-	depends on GSC && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is a driver for the SCSI controller in the Lasi chip found in
-	  many PA-RISC workstations & servers.  If you do not know whether you
-	  have a Lasi chip, it is safe to say "Y" here.
-
-config SCSI_SNI_53C710
-	tristate "SNI RM SCSI support for 53c710"
-	depends on SNI_RM && SCSI
-	select SCSI_SPI_ATTRS
-	select 53C700_LE_ON_BE
-	help
-	  This is a driver for the onboard SCSI controller found in older
-	  SNI RM workstations & servers.
-
-config 53C700_LE_ON_BE
-	bool
-	depends on SCSI_LASI700
-	default y
-
-config SCSI_STEX
-	tristate "Promise SuperTrak EX Series support"
-	depends on PCI && SCSI
-	---help---
-	  This driver supports Promise SuperTrak EX series storage controllers.
-
-	  Promise provides Linux RAID configuration utility for these
-	  controllers. Please visit <http://www.promise.com> to download.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called stex.
-
-config 53C700_BE_BUS
-	bool
-	depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
-	default y
-
-config SCSI_SYM53C8XX_2
-	tristate "SYM53C8XX Version 2 SCSI support"
-	depends on PCI && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This driver supports the whole NCR53C8XX/SYM53C8XX family of
-	  PCI-SCSI controllers.  It also supports the subset of LSI53C10XX
-	  Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
-	  language.  It does not support LSI53C10XX Ultra-320 PCI-X SCSI
-	  controllers; you need to use the Fusion MPT driver for that.
-
-	  Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
-	  information.
-
-config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
-	int "DMA addressing mode"
-	depends on SCSI_SYM53C8XX_2
-	default "1"
-	---help---
-	  This option only applies to PCI-SCSI chips that are PCI DAC
-	  capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
-
-	  When set to 0, the driver will program the chip to only perform
-	  32-bit DMA.  When set to 1, the chip will be able to perform DMA
-	  to addresses up to 1TB.  When set to 2, the driver supports the
-	  full 64-bit DMA address range, but can only address 16 segments
-	  of 4 GB each.  This limits the total addressable range to 64 GB.
-
-	  Most machines with less than 4GB of memory should use a setting
-	  of 0 for best performance.  If your machine has 4GB of memory
-	  or more, you should set this option to 1 (the default).
-
-	  The still experimental value 2 (64 bit DMA addressing with 16
-	  x 4GB segments limitation) can be used on systems that require
-	  PCI address bits past bit 39 to be set for the addressing of
-	  memory using PCI DAC cycles.
-
-config SCSI_SYM53C8XX_DEFAULT_TAGS
-	int "Default tagged command queue depth"
-	depends on SCSI_SYM53C8XX_2
-	default "16"
-	help
-	  This is the default value of the command queue depth the
-	  driver will announce to the generic SCSI layer for devices
-	  that support tagged command queueing. This value can be changed
-	  from the boot command line.  This is a soft limit that cannot
-	  exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
-
-config SCSI_SYM53C8XX_MAX_TAGS
-	int "Maximum number of queued commands"
-	depends on SCSI_SYM53C8XX_2
-	default "64"
-	help
-	  This option allows you to specify the maximum number of commands
-	  that can be queued to any device, when tagged command queuing is
-	  possible. The driver supports up to 256 queued commands per device.
-	  This value is used as a compiled-in hard limit.
-
-config SCSI_SYM53C8XX_MMIO
-	bool "Use memory mapped IO"
-	depends on SCSI_SYM53C8XX_2
-	default y
-	help
-	  Memory mapped IO is faster than Port IO.  Most people should
-	  answer Y here, but some machines may have problems.  If you have
-	  to answer N here, please report the problem to the maintainer.
-
-config SCSI_IPR
-	tristate "IBM Power Linux RAID adapter support"
-	depends on PCI && SCSI && ATA
-	select FW_LOADER
-	---help---
-	  This driver supports the IBM Power Linux family RAID adapters.
-	  This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
-	  as IBM iSeries 5702, 5703, 5709, and 570A.
-
-config SCSI_IPR_TRACE
-	bool "enable driver internal trace"
-	depends on SCSI_IPR
-	default y
-	help
-	  If you say Y here, the driver will trace all commands issued
-	  to the adapter. Performance impact is minimal. Trace can be
-	  dumped using /sys/bus/class/scsi_host/hostXX/trace.
-
-config SCSI_IPR_DUMP
-	bool "enable adapter dump support"
-	depends on SCSI_IPR
-	default y
-	help
-	  If you say Y here, the driver will support adapter crash dump.
-	  If you enable this support, the iprdump daemon can be used
-	  to capture adapter failure analysis information.
-
-config SCSI_ZALON
-	tristate "Zalon SCSI support"
-	depends on GSC && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  The Zalon is a GSC/HSC bus interface chip that sits between the
-	  PA-RISC processor and the NCR 53c720 SCSI controller on C100,
-	  C110, J200, J210 and some D, K & R-class machines.  It's also
-	  used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
-	  Say Y here if you have one of these machines or cards.
-
-config SCSI_NCR_Q720
-	tristate "NCR Quad 720 MCA SCSI support"
-	depends on MCA && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is a driver for the MicroChannel Quad 720 card produced by
-	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
-	  tries to negotiate sync and uses tag command queueing.
-
-	  Unless you have an NCR manufactured machine, the chances are that
-	  you do not have this SCSI card, so say N.
-
-config SCSI_NCR53C8XX_DEFAULT_TAGS
-	int "default tagged command queue depth"
-	depends on SCSI_ZALON || SCSI_NCR_Q720
-	default "8"
-	---help---
-	  "Tagged command queuing" is a feature of SCSI-2 which improves
-	  performance: the host adapter can send several SCSI commands to a
-	  device's queue even if previous commands haven't finished yet.
-	  Because the device is intelligent, it can optimize its operations
-	  (like head positioning) based on its own request queue. Some SCSI
-	  devices don't implement this properly; if you want to disable this
-	  feature, enter 0 or 1 here (it doesn't matter which).
-
-	  The default value is 8 and should be supported by most hard disks.
-	  This value can be overridden from the boot command line using the
-	  'tags' option as follows (example):
-	  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
-	  4, set queue depth to 16 for target 2 and target 3 on controller 0
-	  and set queue depth to 10 for target 0 / lun 2 on controller 1.
-
-	  The normal answer therefore is to go with the default 8 and to use
-	  a boot command line option for devices that need to use a different
-	  command queue depth.
-
-	  There is no safe option other than using good SCSI devices.
-
-config SCSI_NCR53C8XX_MAX_TAGS
-	int "maximum number of queued commands"
-	depends on SCSI_ZALON || SCSI_NCR_Q720
-	default "32"
-	---help---
-	  This option allows you to specify the maximum number of commands
-	  that can be queued to any device, when tagged command queuing is
-	  possible. The default value is 32. Minimum is 2, maximum is 64.
-	  Modern hard disks are able to support 64 tags and even more, but
-	  do not seem to be faster when more than 32 tags are being used.
-
-	  So, the normal answer here is to go with the default value 32 unless
-	  you are using very large hard disks with large cache (>= 1 MB) that
-	  are able to take advantage of more than 32 tagged commands.
-
-	  There is no safe option and the default answer is recommended.
-
-config SCSI_NCR53C8XX_SYNC
-	int "synchronous transfers frequency in MHz"
-	depends on SCSI_ZALON || SCSI_NCR_Q720
-	default "20"
-	---help---
-	  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
-	  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
-	  are respectively the maximum data transfer rates in mega-transfers
-	  per second for each class.  For example, a FAST-20 Wide 16 device is
-	  able to transfer data at 20 million 16 bit packets per second for a
-	  total rate of 40 MB/s.
-
-	  You may specify 0 if you want to only use asynchronous data
-	  transfers. This is the safest and slowest option. Otherwise, specify
-	  a value between 5 and 80, depending on the capability of your SCSI
-	  controller.  The higher the number, the faster the data transfer.
-	  Note that 80 should normally be ok since the driver decreases the
-	  value automatically according to the controller's capabilities.
-
-	  Your answer to this question is ignored for controllers with NVRAM,
-	  since the driver will get this information from the user set-up.  It
-	  also can be overridden using a boot setup option, as follows
-	  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
-	  for FAST-20 synchronous data transfer (20 mega-transfers per
-	  second).
-
-	  The normal answer therefore is not to go with the default but to
-	  select the maximum value 80 allowing the driver to use the maximum
-	  value supported by each controller. If this causes problems with
-	  your SCSI devices, you should come back and decrease the value.
-
-	  There is no safe option other than using good cabling, right
-	  terminations and SCSI conformant devices.
-
-config SCSI_NCR53C8XX_NO_DISCONNECT
-	bool "not allow targets to disconnect"
-	depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
-	help
-	  This option is only provided for safety if you suspect some SCSI
-	  device of yours to not support properly the target-disconnect
-	  feature. In that case, you would say Y here. In general however, to
-	  not allow targets to disconnect is not reasonable if there is more
-	  than 1 device on a SCSI bus. The normal answer therefore is N.
-
-config SCSI_MCA_53C9X
-	tristate "NCR MCA 53C9x SCSI support"
-	depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
-	help
-	  Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
-	  controller based on the NCR 53C94.  This driver will allow use of
-	  the controller on the 3550, and very possibly others.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mca_53c9x.
-
-config SCSI_PAS16
-	tristate "PAS16 SCSI support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This is support for a SCSI host adapter.  It is explained in section
-	  3.10 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/pas16.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called pas16.
-
-config SCSI_PSI240I
-	tristate "PSI240i support"
-	depends on ISA && SCSI
-	help
-	  This is support for the PSI240i EIDE interface card which acts as a
-	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called psi240i.
-
-config SCSI_QLOGIC_FAS
-	tristate "Qlogic FAS SCSI support"
-	depends on ISA && SCSI
-	---help---
-	  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
-	  FastSCSI! cards as well as any other card based on the FASXX chip
-	  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
-
-	  This driver does NOT support the PCI versions of these cards. The
-	  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
-	  SCSI support"), below.
-
-	  Information about this driver is contained in
-	  <file:Documentation/scsi/qlogicfas.txt>.  You should also read the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called qlogicfas.
-
-config SCSI_QLOGIC_FC_FIRMWARE
-	bool "Include loadable firmware in driver"
-	depends on SCSI_QLOGIC_FC
-  	help
-	  Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
-	  expanded LUN addressing and FcTape (FCP-2) support, in the
-	  qlogicfc driver. This is required on some platforms.
-
-config SCSI_QLOGIC_1280
-	tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
-	depends on PCI && SCSI
-	help
-	  Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called qla1280.
-
-config SCSI_QLOGICPTI
-	tristate "PTI Qlogic, ISP Driver"
-	depends on SBUS && SCSI
-	help
-	  This driver supports SBUS SCSI controllers from PTI or QLogic. These
-	  controllers are known under Solaris as qpti and in the openprom as
-	  PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
-	  driven by a different driver.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called qlogicpti.
-
-source "drivers/scsi/qla2xxx/Kconfig"
-source "drivers/scsi/qla4xxx/Kconfig"
-
-config SCSI_LPFC
-	tristate "Emulex LightPulse Fibre Channel Support"
-	depends on PCI && SCSI
-	select SCSI_FC_ATTRS
-	help
-          This lpfc driver supports the Emulex LightPulse
-          Family of Fibre Channel PCI host adapters.
-
-config SCSI_SEAGATE
-	tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
-	depends on X86 && ISA && SCSI
-	select CHECK_SIGNATURE
-	---help---
-	  These are 8-bit SCSI controllers; the ST-01 is also supported by
-	  this driver.  It is explained in section 3.9 of the SCSI-HOWTO,
-	  available from <http://www.tldp.org/docs.html#howto>.  If it
-	  doesn't work out of the box, you may have to change some macros at
-	  compiletime, which are described in <file:drivers/scsi/seagate.c>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called seagate.
-
-# definitely looks not 64bit safe:
-config SCSI_SIM710
-	tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
-	depends on (EISA || MCA) && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This driver for NCR53c710 based SCSI host adapters.
-
-	  It currently supports Compaq EISA cards and NCR MCA cards
-
-config SCSI_SYM53C416
-	tristate "Symbios 53c416 SCSI support"
-	depends on ISA && SCSI
-	---help---
-	  This is support for the sym53c416 SCSI host adapter, the SCSI
-	  adapter that comes with some HP scanners. This driver requires that
-	  the sym53c416 is configured first using some sort of PnP
-	  configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
-	  are using isapnp then you need to compile this driver as a module
-	  and then load it using insmod after isapnp has run. The parameters
-	  of the configured card(s) should be passed to the driver. The format
-	  is:
-
-	  insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called sym53c416.
-
-config SCSI_DC395x
-	tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
-	depends on PCI && SCSI && EXPERIMENTAL
-	---help---
-	  This driver supports PCI SCSI host adapters based on the ASIC
-	  TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
-
-	  This driver works, but is still in experimental status. So better
-	  have a bootable disk and a backup in case of emergency.
-
-	  Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called dc395x.
-
-config SCSI_DC390T
-	tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
-	depends on PCI && SCSI
-	---help---
-	  This driver supports PCI SCSI host adapters based on the Am53C974A
-	  chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
-	  PCscsi/PCnet (Am53/79C974) solutions.
-
-	  Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
-
-	  Note that this driver does NOT support Tekram DC390W/U/F, which are
-	  based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called tmscsim.
-
-config SCSI_T128
-	tristate "Trantor T128/T128F/T228 SCSI support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	select CHECK_SIGNATURE
-	---help---
-	  This is support for a SCSI host adapter. It is explained in section
-	  3.11 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
-	  Adaptec, and some former Trantor products are being sold under the
-	  Adaptec name.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called t128.
-
-config SCSI_U14_34F
-	tristate "UltraStor 14F/34F support"
-	depends on ISA && SCSI && ISA_DMA_API
-	---help---
-	  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
-	  The source at <file:drivers/scsi/u14-34f.c> contains some
-	  information about this hardware.  If the driver doesn't work out of
-	  the box, you may have to change some settings in
-	  <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  Note that there is also
-	  another driver for the same hardware: "UltraStor SCSI support",
-	  below.  You should say Y to both only if you want 24F support as
-	  well.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called u14-34f.
-
-config SCSI_U14_34F_TAGGED_QUEUE
-	bool "enable tagged command queueing"
-	depends on SCSI_U14_34F
-	help
-	  This is a feature of SCSI-2 which improves performance: the host
-	  adapter can send several SCSI commands to a device's queue even if
-	  previous commands haven't finished yet.
-	  This is equivalent to the "u14-34f=tc:y" boot option.
-
-config SCSI_U14_34F_LINKED_COMMANDS
-	bool "enable elevator sorting"
-	depends on SCSI_U14_34F
-	help
-	  This option enables elevator sorting for all probed SCSI disks and
-	  CD-ROMs. It definitely reduces the average seek distance when doing
-	  random seeks, but this does not necessarily result in a noticeable
-	  performance improvement: your mileage may vary...
-	  This is equivalent to the "u14-34f=lc:y" boot option.
-
-config SCSI_U14_34F_MAX_TAGS
-	int "maximum number of queued commands"
-	depends on SCSI_U14_34F
-	default "8"
-	help
-	  This specifies how many SCSI commands can be maximally queued for
-	  each probed SCSI device. You should reduce the default value of 8
-	  only if you have disks with buggy or limited tagged command support.
-	  Minimum is 2 and maximum is 14. This value is also the window size
-	  used by the elevator sorting option above. The effective value used
-	  by the driver for each probed SCSI device is reported at boot time.
-	  This is equivalent to the "u14-34f=mq:8" boot option.
-
-config SCSI_ULTRASTOR
-	tristate "UltraStor SCSI support"
-	depends on X86 && ISA && SCSI
-	---help---
-	  This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
-	  adapter family.  This driver is explained in section 3.12 of the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/ultrastor.h>.
-
-	  Note that there is also another driver for the same hardware:
-	  "UltraStor 14F/34F support", above.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ultrastor.
-
-config SCSI_NSP32
-	tristate "Workbit NinjaSCSI-32Bi/UDE support"
-	depends on PCI && SCSI && !64BIT
-	help
-	  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
-	  SCSI host adapter. Please read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called nsp32.
-
-config SCSI_DEBUG
-	tristate "SCSI debugging host simulator"
-	depends on SCSI
-	help
-	  This is a host adapter simulator that can simulate multiple hosts
-	  each with multiple dummy SCSI devices (disks). It defaults to one
-	  host adapter with one dummy SCSI disk. Each dummy disk uses kernel
-	  RAM as storage (i.e. it is a ramdisk). To save space when multiple
-	  dummy disks are simulated, they share the same kernel RAM for 
-	  their storage. See <http://www.torque.net/sg/sdebug.html> for more
-	  information. This driver is primarily of use to those testing the
-	  SCSI and block subsystems. If unsure, say N.
-
-config SCSI_MESH
-	tristate "MESH (Power Mac internal SCSI) support"
-	depends on PPC32 && PPC_PMAC && SCSI
-	help
-	  Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
-	  SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
-	  other Power Macintoshes do). Say Y to include support for this SCSI
-	  adaptor.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mesh.
-
-config SCSI_MESH_SYNC_RATE
-	int "maximum synchronous transfer rate (MB/s) (0 = async)"
-	depends on SCSI_MESH
-	default "5"
-	help
-	  On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
-	  drives a bus which is entirely internal to the machine (such as the
-	  7500, 7600, 8500, etc.), the MESH is capable of synchronous
-	  operation at up to 10 MB/s. On machines where the SCSI bus
-	  controlled by the MESH can have external devices connected, it is
-	  usually rated at 5 MB/s. 5 is a safe value here unless you know the
-	  MESH SCSI bus is internal only; in that case you can say 10. Say 0
-	  to disable synchronous operation.
-
-config SCSI_MESH_RESET_DELAY_MS
-	int "initial bus reset delay (ms) (0 = no reset)"
-	depends on SCSI_MESH
-	default "4000"
-
-config SCSI_MAC53C94
-	tristate "53C94 (Power Mac external SCSI) support"
-	depends on PPC32 && PPC_PMAC && SCSI
-	help
-	  On Power Macintoshes (and clones) with two SCSI buses, the external
-	  SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
-	  machines which only have one SCSI bus, such as the 7200, also use
-	  the 53C94. Say Y to include support for the 53C94.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mac53c94.
-
-source "drivers/scsi/arm/Kconfig"
-
-config JAZZ_ESP
-	bool "MIPS JAZZ FAS216 SCSI support"
-	depends on MACH_JAZZ && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is the driver for the onboard SCSI host adapter of MIPS Magnum
-	  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
-	  systems.
-
-config A3000_SCSI
-	tristate "A3000 WD33C93A support"
-	depends on AMIGA && SCSI
-	help
-	  If you have an Amiga 3000 and have SCSI devices connected to the
-	  built-in SCSI controller, say Y. Otherwise, say N.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called a3000.
-
-config A2091_SCSI
-	tristate "A2091/A590 WD33C93A support"
-	depends on ZORRO && SCSI
-	help
-	  If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
-	  say N.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called a2091.
-
-config GVP11_SCSI
-	tristate "GVP Series II WD33C93A support"
-	depends on ZORRO && SCSI
-	---help---
-	  If you have a Great Valley Products Series II SCSI controller,
-	  answer Y. Also say Y if you have a later model of GVP SCSI
-	  controller (such as the GVP A4008 or a Combo board). Otherwise,
-	  answer N. This driver does NOT work for the T-Rex series of
-	  accelerators from TekMagic and GVP-M.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called gvp11.
-
-config CYBERSTORM_SCSI
-	tristate "CyberStorm SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have an Amiga with an original (MkI) Phase5 Cyberstorm
-	  accelerator board and the optional Cyberstorm SCSI controller,
-	  answer Y. Otherwise, say N.
-
-config CYBERSTORMII_SCSI
-	tristate "CyberStorm Mk II SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
-	  and the optional Cyberstorm SCSI controller, say Y. Otherwise,
-	  answer N.
-
-config BLZ2060_SCSI
-	tristate "Blizzard 2060 SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
-	  and want to use the onboard SCSI controller, say Y. Otherwise,
-	  answer N.
-
-config BLZ1230_SCSI
-	tristate "Blizzard 1230IV/1260 SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
-	  1260 accelerator, and the optional SCSI module, say Y. Otherwise,
-	  say N.
-
-config FASTLANE_SCSI
-	tristate "Fastlane SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
-	  one in the near future, say Y to this question. Otherwise, say N.
-
-config SCSI_A4000T
-	tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
-	depends on AMIGA && SCSI && EXPERIMENTAL
-	select SCSI_SPI_ATTRS
-	help
-	  If you have an Amiga 4000T and have SCSI devices connected to the
-	  built-in SCSI controller, say Y. Otherwise, say N.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called a4000t.
-
-config SCSI_ZORRO7XX
-	tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
-	depends on ZORRO && SCSI && EXPERIMENTAL
-	select SCSI_SPI_ATTRS
-	help
-	  Support for various NCR53c710-based SCSI controllers on Zorro
-	  expansion boards for the Amiga.
-	  This includes:
-	    - the Amiga 4091 Zorro III SCSI-2 controller,
-	    - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
-	      (info at
-	      <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
-	    - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
-	      accelerator card for the Amiga 1200,
-	    - the SCSI controller on the GVP Turbo 040/060 accelerator.
-
-config OKTAGON_SCSI
-	tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
-	depends on ZORRO && SCSI && EXPERIMENTAL
-	help
-	  If you have the BSC Oktagon SCSI disk controller for the Amiga, say
-	  Y to this question.  If you're in doubt about whether you have one,
-	  see the picture at
-	  <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
-
-config ATARI_SCSI
-	tristate "Atari native SCSI support"
-	depends on ATARI && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  If you have an Atari with built-in NCR5380 SCSI controller (TT,
-	  Falcon, ...) say Y to get it supported. Of course also, if you have
-	  a compatible SCSI controller (e.g. for Medusa).
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called atari_scsi.
-
-	  This driver supports both styles of NCR integration into the
-	  system: the TT style (separate DMA), and the Falcon style (via
-	  ST-DMA, replacing ACSI).  It does NOT support other schemes, like
-	  in the Hades (without DMA).
-
-config ATARI_SCSI_TOSHIBA_DELAY
-	bool "Long delays for Toshiba CD-ROMs"
-	depends on ATARI_SCSI
-	help
-	  This option increases the delay after a SCSI arbitration to
-	  accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
-	  use a Toshiba CD-ROM drive; otherwise, the option is not needed and
-	  would impact performance a bit, so say N.
-
-config ATARI_SCSI_RESET_BOOT
-	bool "Reset SCSI-devices at boottime"
-	depends on ATARI_SCSI
-	help
-	  Reset the devices on your Atari whenever it boots.  This makes the
-	  boot process fractionally longer but may assist recovery from errors
-	  that leave the devices with SCSI operations partway completed.
-
-config TT_DMA_EMUL
-	bool "Hades SCSI DMA emulator"
-	depends on ATARI_SCSI && HADES
-	help
-	  This option enables code which emulates the TT SCSI DMA chip on the
-	  Hades. This increases the SCSI transfer rates at least ten times
-	  compared to PIO transfers.
-
-config MAC_SCSI
-	bool "Macintosh NCR5380 SCSI"
-	depends on MAC && SCSI=y
-	select SCSI_SPI_ATTRS
-	help
-	  This is the NCR 5380 SCSI controller included on most of the 68030
-	  based Macintoshes.  If you have one of these say Y and read the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-config SCSI_MAC_ESP
-	tristate "Macintosh NCR53c9[46] SCSI"
-	depends on MAC && SCSI
-	help
-	  This is the NCR 53c9x SCSI controller found on most of the 68040
-	  based Macintoshes.  If you have one of these say Y and read the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mac_esp.
-
-config MVME147_SCSI
-	bool "WD33C93 SCSI driver for MVME147"
-	depends on MVME147 && SCSI=y
-	select SCSI_SPI_ATTRS
-	help
-	  Support for the on-board SCSI controller on the Motorola MVME147
-	  single-board computer.
-
-config MVME16x_SCSI
-	tristate "NCR53C710 SCSI driver for MVME16x"
-	depends on MVME16x && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
-	  SCSI controller chip.  Almost everyone using one of these boards
-	  will want to say Y to this question.
-
-config BVME6000_SCSI
-	tristate "NCR53C710 SCSI driver for BVME6000"
-	depends on BVME6000 && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
-	  SCSI controller chip.  Almost everyone using one of these boards
-	  will want to say Y to this question.
-
-config SUN3_SCSI
-	tristate "Sun3 NCR5380 SCSI"
-	depends on SUN3 && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This option will enable support for the OBIO (onboard io) NCR5380
-	  SCSI controller found in the Sun 3/50 and 3/60, as well as for
-	  "Sun3" type VME scsi controllers also based on the NCR5380.
-	  General Linux information on the Sun 3 series (now discontinued)
-	  is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
-
-config SUN3X_ESP
-	bool "Sun3x ESP SCSI"
-	depends on SUN3X && SCSI=y
-	help
-	  The ESP was an on-board SCSI controller used on Sun 3/80
-	  machines.  Say Y here to compile in support for it.
-
-config SCSI_SUNESP
-	tristate "Sparc ESP Scsi Driver"
-	depends on SBUS && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is the driver for the Sun ESP SCSI host adapter. The ESP
-	  chipset is present in most SPARC SBUS-based computers.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called esp.
-
-config ZFCP
-	tristate "FCP host bus adapter driver for IBM eServer zSeries"
-	depends on S390 && QDIO && SCSI
-	select SCSI_FC_ATTRS
-	help
-          If you want to access SCSI devices attached to your IBM eServer
-          zSeries by means of Fibre Channel interfaces say Y.
-          For details please refer to the documentation provided by IBM at
-          <http://oss.software.ibm.com/developerworks/opensource/linux390>
-
-          This driver is also available as a module. This module will be
-          called zfcp. If you want to compile it as a module, say M here
-          and read <file:Documentation/kbuild/modules.txt>.
-
-config SCSI_SRP
-	tristate "SCSI RDMA Protocol helper library"
-	depends on SCSI && PCI
-	select SCSI_TGT
-	help
-	  If you wish to use SRP target drivers, say Y.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called libsrp.
-
-endif # SCSI_LOWLEVEL
-
-source "drivers/scsi/pcmcia/Kconfig"
-
-endmenu
+endmenu # Storage (core and SCSI commands)
Index: linux-2.6.23-rc6/drivers/scsi/Kconfig.lowlevel
===================================================================
--- /dev/null
+++ linux-2.6.23-rc6/drivers/scsi/Kconfig.lowlevel
@@ -0,0 +1,1578 @@
+menu "SCSI device support"
+
+config RAID_ATTRS
+	tristate "RAID Transport Class"
+	default n
+	depends on BLOCK
+	---help---
+	  Provides RAID
+
+config SCSI_TGT
+	tristate "SCSI target support"
+	depends on SCSI && EXPERIMENTAL
+	---help---
+	  If you want to use SCSI target mode drivers enable this option.
+	  If you choose M, the module will be called scsi_tgt.
+
+menu "SCSI Transports"
+	depends on SCSI
+
+config SCSI_SPI_ATTRS
+	tristate "Parallel SCSI (SPI) Transport Attributes"
+	depends on SCSI
+	help
+	  If you wish to export transport-specific information about
+	  each attached SCSI device to sysfs, say Y.  Otherwise, say N.
+
+config SCSI_FC_ATTRS
+	tristate "FiberChannel Transport Attributes"
+	depends on SCSI
+	select SCSI_NETLINK
+	help
+	  If you wish to export transport-specific information about
+	  each attached FiberChannel device to sysfs, say Y.
+	  Otherwise, say N.
+
+config SCSI_ISCSI_ATTRS
+	tristate "iSCSI Transport Attributes"
+	depends on SCSI && NET
+	help
+	  If you wish to export transport-specific information about
+	  each attached iSCSI device to sysfs, say Y.
+	  Otherwise, say N.
+
+config SCSI_SAS_ATTRS
+	tristate "SAS Transport Attributes"
+	depends on SCSI && BLK_DEV_BSG
+	help
+	  If you wish to export transport-specific information about
+	  each attached SAS device to sysfs, say Y.
+
+source "drivers/scsi/libsas/Kconfig"
+
+endmenu
+
+menuconfig SCSI_LOWLEVEL
+	bool "SCSI low-level drivers"
+	depends on SCSI!=n
+	default y
+
+if SCSI_LOWLEVEL
+
+config ISCSI_TCP
+	tristate "iSCSI Initiator over TCP/IP"
+	depends on SCSI && INET
+	select CRYPTO
+	select CRYPTO_MD5
+	select CRYPTO_CRC32C
+	select SCSI_ISCSI_ATTRS
+	help
+	 The iSCSI Driver provides a host with the ability to access storage
+	 through an IP network. The driver uses the iSCSI protocol to transport
+	 SCSI requests and responses over a TCP/IP network between the host
+	 (the "initiator") and "targets".  Architecturally, the iSCSI driver
+	 combines with the host's TCP/IP stack, network drivers, and Network
+	 Interface Card (NIC) to provide the same functions as a SCSI or a
+	 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
+
+	 To compile this driver as a module, choose M here: the
+	 module will be called iscsi_tcp.
+
+	 The userspace component needed to initialize the driver, documentation,
+	 and sample configuration files can be found here:
+
+	 http://linux-iscsi.sf.net
+
+config SGIWD93_SCSI
+	tristate "SGI WD93C93 SCSI Driver"
+	depends on SGI_IP22 && SCSI
+  	help
+	  If you have a Western Digital WD93 SCSI controller on
+	  an SGI MIPS system, say Y.  Otherwise, say N.
+
+config SCSI_DECNCR
+	tristate "DEC NCR53C94 Scsi Driver"
+	depends on MACH_DECSTATION && SCSI && TC
+	help
+	  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
+	  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
+
+config SCSI_DECSII
+	tristate "DEC SII Scsi Driver"
+	depends on MACH_DECSTATION && SCSI && 32BIT
+
+config BLK_DEV_3W_XXXX_RAID
+	tristate "3ware 5/6/7/8xxx ATA-RAID support"
+	depends on PCI && SCSI
+	help
+	  3ware is the only hardware ATA-Raid product in Linux to date.
+	  This card is 2,4, or 8 channel master mode support only.
+	  SCSI support required!!!
+
+	  <http://www.3ware.com/>
+
+	  Please read the comments at the top of
+	  <file:drivers/scsi/3w-xxxx.c>.
+
+config SCSI_3W_9XXX
+	tristate "3ware 9xxx SATA-RAID support"
+	depends on PCI && SCSI
+	help
+	  This driver supports the 9000 series 3ware SATA-RAID cards.
+
+	  <http://www.amcc.com>
+
+	  Please read the comments at the top of
+	  <file:drivers/scsi/3w-9xxx.c>.
+
+config SCSI_7000FASST
+	tristate "7000FASST SCSI support"
+	depends on ISA && SCSI && ISA_DMA_API
+	select CHECK_SIGNATURE
+	help
+	  This driver supports the Western Digital 7000 SCSI host adapter
+	  family.  Some information is in the source:
+	  <file:drivers/scsi/wd7000.c>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called wd7000.
+
+config SCSI_ACARD
+	tristate "ACARD SCSI support"
+	depends on PCI && SCSI
+	help
+	  This driver supports the ACARD SCSI host adapter.
+	  Support Chip <ATP870 ATP876 ATP880 ATP885>
+	  To compile this driver as a module, choose M here: the
+	  module will be called atp870u.
+
+config SCSI_AHA152X
+	tristate "Adaptec AHA152X/2825 support"
+	depends on ISA && SCSI && !64BIT
+	select SCSI_SPI_ATTRS
+	select CHECK_SIGNATURE
+	---help---
+	  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
+	  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
+	  must be manually specified in this case.
+
+	  It is explained in section 3.3 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>. You might also want to
+	  read the file <file:Documentation/scsi/aha152x.txt>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called aha152x.
+
+config SCSI_AHA1542
+	tristate "Adaptec AHA1542 support"
+	depends on ISA && SCSI && ISA_DMA_API
+	---help---
+	  This is support for a SCSI host adapter.  It is explained in section
+	  3.4 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
+	  purchased by Adaptec, and some former Trantor products are being
+	  sold under the Adaptec name.  If it doesn't work out of the box, you
+	  may have to change some settings in <file:drivers/scsi/aha1542.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called aha1542.
+
+config SCSI_AHA1740
+	tristate "Adaptec AHA1740 support"
+	depends on EISA && SCSI
+	---help---
+	  This is support for a SCSI host adapter.  It is explained in section
+	  3.5 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/aha1740.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called aha1740.
+
+config SCSI_AACRAID
+	tristate "Adaptec AACRAID support"
+	depends on SCSI && PCI
+	help
+	  This driver supports a variety of Dell, HP, Adaptec, IBM and
+	  ICP storage products. For a list of supported products, refer
+	  to <file:Documentation/scsi/aacraid.txt>.
+
+	  To compile this driver as a module, choose M here: the module
+	  will be called aacraid.
+
+
+source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
+
+config SCSI_AIC7XXX_OLD
+	tristate "Adaptec AIC7xxx support (old driver)"
+	depends on (ISA || EISA || PCI ) && SCSI
+	help
+	  WARNING This driver is an older aic7xxx driver and is no longer
+	  under active development.  Adaptec, Inc. is writing a new driver to
+	  take the place of this one, and it is recommended that whenever
+	  possible, people should use the new Adaptec written driver instead
+	  of this one.  This driver will eventually be phased out entirely.
+
+	  This is support for the various aic7xxx based Adaptec SCSI
+	  controllers. These include the 274x EISA cards; 284x VLB cards;
+	  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
+	  motherboard based SCSI controllers from Adaptec. It does not support
+	  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
+	  support them. It does not support the 2920 cards from Adaptec that
+	  use the Future Domain SCSI controller chip. For those cards, you
+	  need the "Future Domain 16xx SCSI support" driver.
+
+	  In general, if the controller is based on an Adaptec SCSI controller
+	  chip from the aic777x series or the aic78xx series, this driver
+	  should work. The only exception is the 7810 which is specifically
+	  not supported (that's the RAID controller chip on the AAA-13x
+	  cards).
+
+	  Note that the AHA2920 SCSI host adapter is *not* supported by this
+	  driver; choose "Future Domain 16xx SCSI support" instead if you have
+	  one of those.
+
+	  Information on the configuration options for this controller can be
+	  found by checking the help file for each of the available
+	  configuration options. You should read
+	  <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
+	  contacting the maintainer with any questions.  The SCSI-HOWTO,
+	  available from <http://www.tldp.org/docs.html#howto>, can also
+	  be of great help.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called aic7xxx_old.
+
+source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
+source "drivers/scsi/aic94xx/Kconfig"
+
+# All the I2O code and drivers do not seem to be 64bit safe.
+config SCSI_DPT_I2O
+	tristate "Adaptec I2O RAID support "
+	depends on !64BIT && SCSI && PCI && VIRT_TO_BUS
+	help
+	  This driver supports all of Adaptec's I2O based RAID controllers as 
+	  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
+	  driver by Deanna Bonds.  See <file:Documentation/scsi/dpti.txt>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called dpt_i2o.
+
+config SCSI_ADVANSYS
+	tristate "AdvanSys SCSI support"
+	depends on SCSI
+	depends on ISA || EISA || PCI
+	depends on BROKEN || X86_32
+	help
+	  This is a driver for all SCSI host adapters manufactured by
+	  AdvanSys. It is documented in the kernel source in
+	  <file:drivers/scsi/advansys.c>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called advansys.
+
+config SCSI_IN2000
+	tristate "Always IN2000 SCSI support"
+	depends on ISA && SCSI
+	help
+	  This is support for an ISA bus SCSI host adapter.  You'll find more
+	  information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
+	  out of the box, you may have to change the jumpers for IRQ or
+	  address selection.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called in2000.
+
+config SCSI_ARCMSR
+	tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
+	depends on PCI && SCSI
+	help
+	  This driver supports all of ARECA's SATA RAID controller cards.
+	  This is an ARECA-maintained driver by Erich Chen.
+	  If you have any problems, please mail to: < erich@areca.com.tw >
+	  Areca supports Linux RAID config tools.
+
+	  < http://www.areca.com.tw >
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called arcmsr (modprobe arcmsr).
+
+source "drivers/scsi/megaraid/Kconfig.megaraid"
+
+config SCSI_HPTIOP
+	tristate "HighPoint RocketRAID 3xxx Controller support"
+	depends on SCSI && PCI
+	help
+	  This option enables support for HighPoint RocketRAID 3xxx
+	  controllers.
+
+	  To compile this driver as a module, choose M here; the module
+	  will be called hptiop. If unsure, say N.
+
+config SCSI_BUSLOGIC
+	tristate "BusLogic SCSI support"
+	depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
+	---help---
+	  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
+	  Adapters. Consult the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>, and the files
+	  <file:Documentation/scsi/BusLogic.txt> and
+	  <file:Documentation/scsi/FlashPoint.txt> for more information.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called BusLogic.
+
+config SCSI_OMIT_FLASHPOINT
+	bool "Omit FlashPoint support"
+	depends on SCSI_BUSLOGIC
+	help
+	  This option allows you to omit the FlashPoint support from the
+	  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
+	  substantial, so users of MultiMaster Host Adapters may wish to omit
+	  it.
+
+config SCSI_DMX3191D
+	tristate "DMX3191D SCSI support"
+	depends on PCI && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is support for Domex DMX3191D SCSI Host Adapters.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called dmx3191d.
+
+config SCSI_DTC3280
+	tristate "DTC3180/3280 SCSI support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	select CHECK_SIGNATURE
+	help
+	  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
+	  the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>, and the file
+	  <file:Documentation/scsi/dtc3x80.txt>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called dtc.
+
+config SCSI_EATA
+	tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
+	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
+	---help---
+	  This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
+	  ISA and all EISA I/O addresses are probed looking for the "EATA"
+	  signature. The addresses of all the PCI SCSI controllers reported
+          by the PCI subsystem are probed as well.
+
+	  You want to read the start of <file:drivers/scsi/eata.c> and the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called eata.
+
+config SCSI_EATA_TAGGED_QUEUE
+	bool "enable tagged command queueing"
+	depends on SCSI_EATA
+	help
+	  This is a feature of SCSI-2 which improves performance: the host
+	  adapter can send several SCSI commands to a device's queue even if
+	  previous commands haven't finished yet.
+	  This is equivalent to the "eata=tc:y" boot option.
+
+config SCSI_EATA_LINKED_COMMANDS
+	bool "enable elevator sorting"
+	depends on SCSI_EATA
+	help
+	  This option enables elevator sorting for all probed SCSI disks and
+	  CD-ROMs. It definitely reduces the average seek distance when doing
+	  random seeks, but this does not necessarily result in a noticeable
+	  performance improvement: your mileage may vary...
+	  This is equivalent to the "eata=lc:y" boot option.
+
+config SCSI_EATA_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on SCSI_EATA
+	default "16"
+	help
+	  This specifies how many SCSI commands can be maximally queued for
+	  each probed SCSI device. You should reduce the default value of 16
+	  only if you have disks with buggy or limited tagged command support.
+	  Minimum is 2 and maximum is 62. This value is also the window size
+	  used by the elevator sorting option above. The effective value used
+	  by the driver for each probed SCSI device is reported at boot time.
+	  This is equivalent to the "eata=mq:8" boot option.
+
+config SCSI_EATA_PIO
+	tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
+	depends on (ISA || EISA || PCI) && SCSI && BROKEN
+	---help---
+	  This driver supports all EATA-PIO protocol compliant SCSI Host
+	  Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
+	  host adapters could also use this driver but are discouraged from
+	  doing so, since this driver only supports hard disks and lacks
+	  numerous features.  You might want to have a look at the SCSI-HOWTO,
+	  available from <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called eata_pio.
+
+config SCSI_FUTURE_DOMAIN
+	tristate "Future Domain 16xx SCSI/AHA-2920A support"
+	depends on (ISA || PCI) && SCSI
+	select CHECK_SIGNATURE
+	---help---
+	  This is support for Future Domain's 16-bit SCSI host adapters
+	  (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
+	  other adapters based on the Future Domain chipsets (Quantum
+	  ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
+	  It is explained in section 3.7 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
+	  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
+	  controller support"). This Future Domain driver works with the older
+	  Adaptec AHA-2920A boards with a Future Domain chip on them.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called fdomain.
+
+config SCSI_FD_MCS
+	tristate "Future Domain MCS-600/700 SCSI support"
+	depends on MCA_LEGACY && SCSI
+	---help---
+	  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
+	  Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
+	  is identical to the MCS 700 and hence also supported by this driver.
+	  This driver also supports the Reply SB16/SCSI card (the SCSI part).
+	  It supports multiple adapters in the same system.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called fd_mcs.
+
+config SCSI_GDTH
+	tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
+	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
+	---help---
+	  Formerly called GDT SCSI Disk Array Controller Support.
+
+	  This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 
+	  manufactured by Intel Corporation/ICP vortex GmbH. It is documented
+	  in the kernel source in <file:drivers/scsi/gdth.c> and
+	  <file:drivers/scsi/gdth.h.>
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called gdth.
+
+config SCSI_GENERIC_NCR5380
+	tristate "Generic NCR5380/53c400 SCSI PIO support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This is a driver for the old NCR 53c80 series of SCSI controllers
+	  on boards using PIO. Most boards such as the Trantor T130 fit this
+	  category, along with a large number of ISA 8bit controllers shipped
+	  for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
+	  you should select the specific driver for that card rather than
+	  generic 5380 support.
+
+	  It is explained in section 3.8 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/g_NCR5380.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called g_NCR5380.
+
+config SCSI_GENERIC_NCR5380_MMIO
+	tristate "Generic NCR5380/53c400 SCSI MMIO support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This is a driver for the old NCR 53c80 series of SCSI controllers
+	  on boards using memory mapped I/O. 
+	  It is explained in section 3.8 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/g_NCR5380.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called g_NCR5380_mmio.
+
+config SCSI_GENERIC_NCR53C400
+	bool "Enable NCR53c400 extensions"
+	depends on SCSI_GENERIC_NCR5380
+	help
+	  This enables certain optimizations for the NCR53c400 SCSI cards.
+	  You might as well try it out.  Note that this driver will only probe
+	  for the Trantor T130B in its default configuration; you might have
+	  to pass a command line option to the kernel at boot time if it does
+	  not detect your card.  See the file
+	  <file:Documentation/scsi/g_NCR5380.txt> for details.
+
+config SCSI_IBMMCA
+	tristate "IBMMCA SCSI support"
+	depends on MCA && SCSI
+	---help---
+	  This is support for the IBM SCSI adapter found in many of the PS/2
+	  series computers.  These machines have an MCA bus, so you need to
+	  answer Y to "MCA support" as well and read
+	  <file:Documentation/mca.txt>.
+
+	  If the adapter isn't found during boot (a common problem for models
+	  56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
+	  option, where <pun> is the id of the SCSI subsystem (usually 7, but
+	  if that doesn't work check your reference diskette).  Owners of
+	  model 95 with a LED-matrix-display can in addition activate some
+	  activity info like under OS/2, but more informative, by setting
+	  'ibmmcascsi=display' as an additional kernel parameter.  Try "man
+	  bootparam" or see the documentation of your boot loader about how to
+	  pass options to the kernel.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ibmmca.
+
+config IBMMCA_SCSI_ORDER_STANDARD
+	bool "Standard SCSI-order"
+	depends on SCSI_IBMMCA
+	---help---
+	  In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
+	  are assigned to the drive letters, starting with the lowest SCSI-id
+	  (physical number -- pun) to be drive C:, as seen from DOS and
+	  similar operating systems. When looking into papers describing the
+	  ANSI-SCSI-standard, this assignment of drives appears to be wrong.
+	  The SCSI-standard follows a hardware-hierarchy which says that id 7
+	  has the highest priority and id 0 the lowest. Therefore, the host
+	  adapters are still today everywhere placed as SCSI-id 7 by default.
+	  In the SCSI-standard, the drive letters express the priority of the
+	  disk. C: should be the hard disk, or a partition on it, with the
+	  highest priority. This must therefore be the disk with the highest
+	  SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
+	  original definition of the SCSI-standard as also industrial- and
+	  process-control-machines, like VME-CPUs running under realtime-OSes
+	  (e.g. LynxOS, OS9) do.
+
+	  If you like to run Linux on your MCA-machine with the same
+	  assignment of hard disks as seen from e.g. DOS or OS/2 on your
+	  machine, which is in addition conformant to the SCSI-standard, you
+	  must say Y here. This is also necessary for MCA-Linux users who want
+	  to keep downward compatibility to older releases of the
+	  IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
+	  June 1997).
+
+	  If you like to have the lowest SCSI-id assigned as drive C:, as
+	  modern SCSI-BIOSes do, which does not conform to the standard, but
+	  is widespread and common in the PC-world of today, you must say N
+	  here. If unsure, say Y.
+
+config IBMMCA_SCSI_DEV_RESET
+	bool "Reset SCSI-devices at boottime"
+	depends on SCSI_IBMMCA
+	---help---
+	  By default, SCSI-devices are reset when the machine is powered on.
+	  However, some devices exist, like special-control-devices,
+	  SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
+	  not reset when switched on. If you say Y here, each device connected
+	  to your SCSI-bus will be issued a reset-command after it has been
+	  probed, while the kernel is booting. This may cause problems with
+	  more modern devices, like hard disks, which do not appreciate these
+	  reset commands, and can cause your system to hang. So say Y only if
+	  you know that one of your older devices needs it; N is the safe
+	  answer.
+
+config SCSI_IPS
+	tristate "IBM ServeRAID support"
+	depends on PCI && SCSI
+	---help---
+	  This is support for the IBM ServeRAID hardware RAID controllers.
+	  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
+	  for more information.  If this driver does not work correctly
+	  without modification please contact the author by email at
+	  <ipslinux@adaptec.com>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ips.
+
+config SCSI_IBMVSCSI
+	tristate "IBM Virtual SCSI support"
+	depends on PPC_PSERIES || PPC_ISERIES
+	help
+	  This is the IBM POWER Virtual SCSI Client
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ibmvscsic.
+
+config SCSI_IBMVSCSIS
+	tristate "IBM Virtual SCSI Server support"
+	depends on PPC_PSERIES && SCSI_TGT && SCSI_SRP
+	help
+	  This is the SRP target driver for IBM pSeries virtual environments.
+
+	  The userspace component needed to initialize the driver and
+	  documentation can be found:
+
+	  http://stgt.berlios.de/
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ibmvstgt.
+
+config SCSI_INITIO
+	tristate "Initio 9100U(W) support"
+	depends on PCI && SCSI
+	help
+	  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
+	  read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called initio.
+
+config SCSI_INIA100
+	tristate "Initio INI-A100U2W support"
+	depends on PCI && SCSI
+	help
+	  This is support for the Initio INI-A100U2W SCSI host adapter.
+	  Please read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called a100u2w.
+
+config SCSI_PPA
+	tristate "IOMEGA parallel port (ppa - older drives)"
+	depends on SCSI && PARPORT_PC
+	---help---
+	  This driver supports older versions of IOMEGA's parallel port ZIP
+	  drive (a 100 MB removable media device).
+
+	  Note that you can say N here if you have the SCSI version of the ZIP
+	  drive: it will be supported automatically if you said Y to the
+	  generic "SCSI disk support", above.
+
+	  If you have the ZIP Plus drive or a more recent parallel port ZIP
+	  drive (if the supplied cable with the drive is labeled "AutoDetect")
+	  then you should say N here and Y to "IOMEGA parallel port (imm -
+	  newer drives)", below.
+
+	  For more information about this driver and how to use it you should
+	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
+	  the SCSI-HOWTO, which is available from
+	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
+	  you will still be able to use the parallel port for other tasks,
+	  such as a printer; it is safe to compile both drivers into the
+	  kernel.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ppa.
+
+config SCSI_IMM
+	tristate "IOMEGA parallel port (imm - newer drives)"
+	depends on SCSI && PARPORT_PC
+	---help---
+	  This driver supports newer versions of IOMEGA's parallel port ZIP
+	  drive (a 100 MB removable media device).
+
+	  Note that you can say N here if you have the SCSI version of the ZIP
+	  drive: it will be supported automatically if you said Y to the
+	  generic "SCSI disk support", above.
+
+	  If you have the ZIP Plus drive or a more recent parallel port ZIP
+	  drive (if the supplied cable with the drive is labeled "AutoDetect")
+	  then you should say Y here; if you have an older ZIP drive, say N
+	  here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
+
+	  For more information about this driver and how to use it you should
+	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
+	  the SCSI-HOWTO, which is available from
+	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
+	  you will still be able to use the parallel port for other tasks,
+	  such as a printer; it is safe to compile both drivers into the
+	  kernel.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called imm.
+
+config SCSI_IZIP_EPP16
+	bool "ppa/imm option - Use slow (but safe) EPP-16"
+	depends on SCSI_PPA || SCSI_IMM
+	---help---
+	  EPP (Enhanced Parallel Port) is a standard for parallel ports which
+	  allows them to act as expansion buses that can handle up to 64
+	  peripheral devices.
+
+	  Some parallel port chipsets are slower than their motherboard, and
+	  so we have to control the state of the chipset's FIFO queue every
+	  now and then to avoid data loss. This will be done if you say Y
+	  here.
+
+	  Generally, saying Y is the safe option and slows things down a bit.
+
+config SCSI_IZIP_SLOW_CTR
+	bool "ppa/imm option - Assume slow parport control register"
+	depends on SCSI_PPA || SCSI_IMM
+	help
+	  Some parallel ports are known to have excessive delays between
+	  changing the parallel port control register and good data being
+	  available on the parallel port data/status register. This option
+	  forces a small delay (1.0 usec to be exact) after changing the
+	  control register to let things settle out. Enabling this option may
+	  result in a big drop in performance but some very old parallel ports
+	  (found in 386 vintage machines) will not work properly.
+
+	  Generally, saying N is fine.
+
+config SCSI_NCR53C406A
+	tristate "NCR53c406a SCSI support"
+	depends on ISA && SCSI
+	help
+	  This is support for the NCR53c406a SCSI host adapter.  For user
+	  configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
+	  in the kernel source.  Also read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called NCR53c406.
+
+config SCSI_NCR_D700
+	tristate "NCR Dual 700 MCA SCSI support"
+	depends on MCA && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is a driver for the MicroChannel Dual 700 card produced by
+	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
+	  tries to negotiate sync and uses tag command queueing.
+
+	  Unless you have an NCR manufactured machine, the chances are that
+	  you do not have this SCSI card, so say N.
+
+config SCSI_LASI700
+	tristate "HP Lasi SCSI support for 53c700/710"
+	depends on GSC && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is a driver for the SCSI controller in the Lasi chip found in
+	  many PA-RISC workstations & servers.  If you do not know whether you
+	  have a Lasi chip, it is safe to say "Y" here.
+
+config SCSI_SNI_53C710
+	tristate "SNI RM SCSI support for 53c710"
+	depends on SNI_RM && SCSI
+	select SCSI_SPI_ATTRS
+	select 53C700_LE_ON_BE
+	help
+	  This is a driver for the onboard SCSI controller found in older
+	  SNI RM workstations & servers.
+
+config 53C700_LE_ON_BE
+	bool
+	depends on SCSI_LASI700
+	default y
+
+config SCSI_STEX
+	tristate "Promise SuperTrak EX Series support"
+	depends on PCI && SCSI
+	---help---
+	  This driver supports Promise SuperTrak EX series storage controllers.
+
+	  Promise provides Linux RAID configuration utility for these
+	  controllers. Please visit <http://www.promise.com> to download.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called stex.
+
+config 53C700_BE_BUS
+	bool
+	depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
+	default y
+
+config SCSI_SYM53C8XX_2
+	tristate "SYM53C8XX Version 2 SCSI support"
+	depends on PCI && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This driver supports the whole NCR53C8XX/SYM53C8XX family of
+	  PCI-SCSI controllers.  It also supports the subset of LSI53C10XX
+	  Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
+	  language.  It does not support LSI53C10XX Ultra-320 PCI-X SCSI
+	  controllers; you need to use the Fusion MPT driver for that.
+
+	  Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
+	  information.
+
+config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
+	int "DMA addressing mode"
+	depends on SCSI_SYM53C8XX_2
+	default "1"
+	---help---
+	  This option only applies to PCI-SCSI chips that are PCI DAC
+	  capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
+
+	  When set to 0, the driver will program the chip to only perform
+	  32-bit DMA.  When set to 1, the chip will be able to perform DMA
+	  to addresses up to 1TB.  When set to 2, the driver supports the
+	  full 64-bit DMA address range, but can only address 16 segments
+	  of 4 GB each.  This limits the total addressable range to 64 GB.
+
+	  Most machines with less than 4GB of memory should use a setting
+	  of 0 for best performance.  If your machine has 4GB of memory
+	  or more, you should set this option to 1 (the default).
+
+	  The still experimental value 2 (64 bit DMA addressing with 16
+	  x 4GB segments limitation) can be used on systems that require
+	  PCI address bits past bit 39 to be set for the addressing of
+	  memory using PCI DAC cycles.
+
+config SCSI_SYM53C8XX_DEFAULT_TAGS
+	int "Default tagged command queue depth"
+	depends on SCSI_SYM53C8XX_2
+	default "16"
+	help
+	  This is the default value of the command queue depth the
+	  driver will announce to the generic SCSI layer for devices
+	  that support tagged command queueing. This value can be changed
+	  from the boot command line.  This is a soft limit that cannot
+	  exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
+
+config SCSI_SYM53C8XX_MAX_TAGS
+	int "Maximum number of queued commands"
+	depends on SCSI_SYM53C8XX_2
+	default "64"
+	help
+	  This option allows you to specify the maximum number of commands
+	  that can be queued to any device, when tagged command queuing is
+	  possible. The driver supports up to 256 queued commands per device.
+	  This value is used as a compiled-in hard limit.
+
+config SCSI_SYM53C8XX_MMIO
+	bool "Use memory mapped IO"
+	depends on SCSI_SYM53C8XX_2
+	default y
+	help
+	  Memory mapped IO is faster than Port IO.  Most people should
+	  answer Y here, but some machines may have problems.  If you have
+	  to answer N here, please report the problem to the maintainer.
+
+config SCSI_IPR
+	tristate "IBM Power Linux RAID adapter support"
+	depends on PCI && SCSI && ATA
+	select FW_LOADER
+	---help---
+	  This driver supports the IBM Power Linux family RAID adapters.
+	  This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
+	  as IBM iSeries 5702, 5703, 5709, and 570A.
+
+config SCSI_IPR_TRACE
+	bool "enable driver internal trace"
+	depends on SCSI_IPR
+	default y
+	help
+	  If you say Y here, the driver will trace all commands issued
+	  to the adapter. Performance impact is minimal. Trace can be
+	  dumped using /sys/bus/class/scsi_host/hostXX/trace.
+
+config SCSI_IPR_DUMP
+	bool "enable adapter dump support"
+	depends on SCSI_IPR
+	default y
+	help
+	  If you say Y here, the driver will support adapter crash dump.
+	  If you enable this support, the iprdump daemon can be used
+	  to capture adapter failure analysis information.
+
+config SCSI_ZALON
+	tristate "Zalon SCSI support"
+	depends on GSC && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  The Zalon is a GSC/HSC bus interface chip that sits between the
+	  PA-RISC processor and the NCR 53c720 SCSI controller on C100,
+	  C110, J200, J210 and some D, K & R-class machines.  It's also
+	  used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
+	  Say Y here if you have one of these machines or cards.
+
+config SCSI_NCR_Q720
+	tristate "NCR Quad 720 MCA SCSI support"
+	depends on MCA && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is a driver for the MicroChannel Quad 720 card produced by
+	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
+	  tries to negotiate sync and uses tag command queueing.
+
+	  Unless you have an NCR manufactured machine, the chances are that
+	  you do not have this SCSI card, so say N.
+
+config SCSI_NCR53C8XX_DEFAULT_TAGS
+	int "default tagged command queue depth"
+	depends on SCSI_ZALON || SCSI_NCR_Q720
+	default "8"
+	---help---
+	  "Tagged command queuing" is a feature of SCSI-2 which improves
+	  performance: the host adapter can send several SCSI commands to a
+	  device's queue even if previous commands haven't finished yet.
+	  Because the device is intelligent, it can optimize its operations
+	  (like head positioning) based on its own request queue. Some SCSI
+	  devices don't implement this properly; if you want to disable this
+	  feature, enter 0 or 1 here (it doesn't matter which).
+
+	  The default value is 8 and should be supported by most hard disks.
+	  This value can be overridden from the boot command line using the
+	  'tags' option as follows (example):
+	  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
+	  4, set queue depth to 16 for target 2 and target 3 on controller 0
+	  and set queue depth to 10 for target 0 / lun 2 on controller 1.
+
+	  The normal answer therefore is to go with the default 8 and to use
+	  a boot command line option for devices that need to use a different
+	  command queue depth.
+
+	  There is no safe option other than using good SCSI devices.
+
+config SCSI_NCR53C8XX_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on SCSI_ZALON || SCSI_NCR_Q720
+	default "32"
+	---help---
+	  This option allows you to specify the maximum number of commands
+	  that can be queued to any device, when tagged command queuing is
+	  possible. The default value is 32. Minimum is 2, maximum is 64.
+	  Modern hard disks are able to support 64 tags and even more, but
+	  do not seem to be faster when more than 32 tags are being used.
+
+	  So, the normal answer here is to go with the default value 32 unless
+	  you are using very large hard disks with large cache (>= 1 MB) that
+	  are able to take advantage of more than 32 tagged commands.
+
+	  There is no safe option and the default answer is recommended.
+
+config SCSI_NCR53C8XX_SYNC
+	int "synchronous transfers frequency in MHz"
+	depends on SCSI_ZALON || SCSI_NCR_Q720
+	default "20"
+	---help---
+	  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
+	  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
+	  are respectively the maximum data transfer rates in mega-transfers
+	  per second for each class.  For example, a FAST-20 Wide 16 device is
+	  able to transfer data at 20 million 16 bit packets per second for a
+	  total rate of 40 MB/s.
+
+	  You may specify 0 if you want to only use asynchronous data
+	  transfers. This is the safest and slowest option. Otherwise, specify
+	  a value between 5 and 80, depending on the capability of your SCSI
+	  controller.  The higher the number, the faster the data transfer.
+	  Note that 80 should normally be ok since the driver decreases the
+	  value automatically according to the controller's capabilities.
+
+	  Your answer to this question is ignored for controllers with NVRAM,
+	  since the driver will get this information from the user set-up.  It
+	  also can be overridden using a boot setup option, as follows
+	  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
+	  for FAST-20 synchronous data transfer (20 mega-transfers per
+	  second).
+
+	  The normal answer therefore is not to go with the default but to
+	  select the maximum value 80 allowing the driver to use the maximum
+	  value supported by each controller. If this causes problems with
+	  your SCSI devices, you should come back and decrease the value.
+
+	  There is no safe option other than using good cabling, right
+	  terminations and SCSI conformant devices.
+
+config SCSI_NCR53C8XX_NO_DISCONNECT
+	bool "not allow targets to disconnect"
+	depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
+	help
+	  This option is only provided for safety if you suspect some SCSI
+	  device of yours to not support properly the target-disconnect
+	  feature. In that case, you would say Y here. In general however, to
+	  not allow targets to disconnect is not reasonable if there is more
+	  than 1 device on a SCSI bus. The normal answer therefore is N.
+
+config SCSI_MCA_53C9X
+	tristate "NCR MCA 53C9x SCSI support"
+	depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
+	help
+	  Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
+	  controller based on the NCR 53C94.  This driver will allow use of
+	  the controller on the 3550, and very possibly others.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mca_53c9x.
+
+config SCSI_PAS16
+	tristate "PAS16 SCSI support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This is support for a SCSI host adapter.  It is explained in section
+	  3.10 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/pas16.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called pas16.
+
+config SCSI_PSI240I
+	tristate "PSI240i support"
+	depends on ISA && SCSI
+	help
+	  This is support for the PSI240i EIDE interface card which acts as a
+	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called psi240i.
+
+config SCSI_QLOGIC_FAS
+	tristate "Qlogic FAS SCSI support"
+	depends on ISA && SCSI
+	---help---
+	  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
+	  FastSCSI! cards as well as any other card based on the FASXX chip
+	  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
+
+	  This driver does NOT support the PCI versions of these cards. The
+	  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
+	  SCSI support"), below.
+
+	  Information about this driver is contained in
+	  <file:Documentation/scsi/qlogicfas.txt>.  You should also read the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called qlogicfas.
+
+config SCSI_QLOGIC_FC_FIRMWARE
+	bool "Include loadable firmware in driver"
+	depends on SCSI_QLOGIC_FC
+  	help
+	  Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
+	  expanded LUN addressing and FcTape (FCP-2) support, in the
+	  qlogicfc driver. This is required on some platforms.
+
+config SCSI_QLOGIC_1280
+	tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
+	depends on PCI && SCSI
+	help
+	  Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called qla1280.
+
+config SCSI_QLOGICPTI
+	tristate "PTI Qlogic, ISP Driver"
+	depends on SBUS && SCSI
+	help
+	  This driver supports SBUS SCSI controllers from PTI or QLogic. These
+	  controllers are known under Solaris as qpti and in the openprom as
+	  PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
+	  driven by a different driver.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called qlogicpti.
+
+source "drivers/scsi/qla2xxx/Kconfig"
+source "drivers/scsi/qla4xxx/Kconfig"
+
+config SCSI_LPFC
+	tristate "Emulex LightPulse Fibre Channel Support"
+	depends on PCI && SCSI
+	select SCSI_FC_ATTRS
+	help
+          This lpfc driver supports the Emulex LightPulse
+          Family of Fibre Channel PCI host adapters.
+
+config SCSI_SEAGATE
+	tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
+	depends on X86 && ISA && SCSI
+	select CHECK_SIGNATURE
+	---help---
+	  These are 8-bit SCSI controllers; the ST-01 is also supported by
+	  this driver.  It is explained in section 3.9 of the SCSI-HOWTO,
+	  available from <http://www.tldp.org/docs.html#howto>.  If it
+	  doesn't work out of the box, you may have to change some macros at
+	  compiletime, which are described in <file:drivers/scsi/seagate.c>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called seagate.
+
+# definitely looks not 64bit safe:
+config SCSI_SIM710
+	tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
+	depends on (EISA || MCA) && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This driver for NCR53c710 based SCSI host adapters.
+
+	  It currently supports Compaq EISA cards and NCR MCA cards
+
+config SCSI_SYM53C416
+	tristate "Symbios 53c416 SCSI support"
+	depends on ISA && SCSI
+	---help---
+	  This is support for the sym53c416 SCSI host adapter, the SCSI
+	  adapter that comes with some HP scanners. This driver requires that
+	  the sym53c416 is configured first using some sort of PnP
+	  configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
+	  are using isapnp then you need to compile this driver as a module
+	  and then load it using insmod after isapnp has run. The parameters
+	  of the configured card(s) should be passed to the driver. The format
+	  is:
+
+	  insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called sym53c416.
+
+config SCSI_DC395x
+	tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
+	depends on PCI && SCSI && EXPERIMENTAL
+	---help---
+	  This driver supports PCI SCSI host adapters based on the ASIC
+	  TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
+
+	  This driver works, but is still in experimental status. So better
+	  have a bootable disk and a backup in case of emergency.
+
+	  Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called dc395x.
+
+config SCSI_DC390T
+	tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
+	depends on PCI && SCSI
+	---help---
+	  This driver supports PCI SCSI host adapters based on the Am53C974A
+	  chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
+	  PCscsi/PCnet (Am53/79C974) solutions.
+
+	  Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
+
+	  Note that this driver does NOT support Tekram DC390W/U/F, which are
+	  based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called tmscsim.
+
+config SCSI_T128
+	tristate "Trantor T128/T128F/T228 SCSI support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	select CHECK_SIGNATURE
+	---help---
+	  This is support for a SCSI host adapter. It is explained in section
+	  3.11 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
+	  Adaptec, and some former Trantor products are being sold under the
+	  Adaptec name.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called t128.
+
+config SCSI_U14_34F
+	tristate "UltraStor 14F/34F support"
+	depends on ISA && SCSI && ISA_DMA_API
+	---help---
+	  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
+	  The source at <file:drivers/scsi/u14-34f.c> contains some
+	  information about this hardware.  If the driver doesn't work out of
+	  the box, you may have to change some settings in
+	  <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  Note that there is also
+	  another driver for the same hardware: "UltraStor SCSI support",
+	  below.  You should say Y to both only if you want 24F support as
+	  well.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called u14-34f.
+
+config SCSI_U14_34F_TAGGED_QUEUE
+	bool "enable tagged command queueing"
+	depends on SCSI_U14_34F
+	help
+	  This is a feature of SCSI-2 which improves performance: the host
+	  adapter can send several SCSI commands to a device's queue even if
+	  previous commands haven't finished yet.
+	  This is equivalent to the "u14-34f=tc:y" boot option.
+
+config SCSI_U14_34F_LINKED_COMMANDS
+	bool "enable elevator sorting"
+	depends on SCSI_U14_34F
+	help
+	  This option enables elevator sorting for all probed SCSI disks and
+	  CD-ROMs. It definitely reduces the average seek distance when doing
+	  random seeks, but this does not necessarily result in a noticeable
+	  performance improvement: your mileage may vary...
+	  This is equivalent to the "u14-34f=lc:y" boot option.
+
+config SCSI_U14_34F_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on SCSI_U14_34F
+	default "8"
+	help
+	  This specifies how many SCSI commands can be maximally queued for
+	  each probed SCSI device. You should reduce the default value of 8
+	  only if you have disks with buggy or limited tagged command support.
+	  Minimum is 2 and maximum is 14. This value is also the window size
+	  used by the elevator sorting option above. The effective value used
+	  by the driver for each probed SCSI device is reported at boot time.
+	  This is equivalent to the "u14-34f=mq:8" boot option.
+
+config SCSI_ULTRASTOR
+	tristate "UltraStor SCSI support"
+	depends on X86 && ISA && SCSI
+	---help---
+	  This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
+	  adapter family.  This driver is explained in section 3.12 of the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/ultrastor.h>.
+
+	  Note that there is also another driver for the same hardware:
+	  "UltraStor 14F/34F support", above.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ultrastor.
+
+config SCSI_NSP32
+	tristate "Workbit NinjaSCSI-32Bi/UDE support"
+	depends on PCI && SCSI && !64BIT
+	help
+	  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
+	  SCSI host adapter. Please read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called nsp32.
+
+config SCSI_DEBUG
+	tristate "SCSI debugging host simulator"
+	depends on SCSI
+	help
+	  This is a host adapter simulator that can simulate multiple hosts
+	  each with multiple dummy SCSI devices (disks). It defaults to one
+	  host adapter with one dummy SCSI disk. Each dummy disk uses kernel
+	  RAM as storage (i.e. it is a ramdisk). To save space when multiple
+	  dummy disks are simulated, they share the same kernel RAM for 
+	  their storage. See <http://www.torque.net/sg/sdebug.html> for more
+	  information. This driver is primarily of use to those testing the
+	  SCSI and block subsystems. If unsure, say N.
+
+config SCSI_MESH
+	tristate "MESH (Power Mac internal SCSI) support"
+	depends on PPC32 && PPC_PMAC && SCSI
+	help
+	  Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
+	  SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
+	  other Power Macintoshes do). Say Y to include support for this SCSI
+	  adaptor.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mesh.
+
+config SCSI_MESH_SYNC_RATE
+	int "maximum synchronous transfer rate (MB/s) (0 = async)"
+	depends on SCSI_MESH
+	default "5"
+	help
+	  On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
+	  drives a bus which is entirely internal to the machine (such as the
+	  7500, 7600, 8500, etc.), the MESH is capable of synchronous
+	  operation at up to 10 MB/s. On machines where the SCSI bus
+	  controlled by the MESH can have external devices connected, it is
+	  usually rated at 5 MB/s. 5 is a safe value here unless you know the
+	  MESH SCSI bus is internal only; in that case you can say 10. Say 0
+	  to disable synchronous operation.
+
+config SCSI_MESH_RESET_DELAY_MS
+	int "initial bus reset delay (ms) (0 = no reset)"
+	depends on SCSI_MESH
+	default "4000"
+
+config SCSI_MAC53C94
+	tristate "53C94 (Power Mac external SCSI) support"
+	depends on PPC32 && PPC_PMAC && SCSI
+	help
+	  On Power Macintoshes (and clones) with two SCSI buses, the external
+	  SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
+	  machines which only have one SCSI bus, such as the 7200, also use
+	  the 53C94. Say Y to include support for the 53C94.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mac53c94.
+
+source "drivers/scsi/arm/Kconfig"
+
+config JAZZ_ESP
+	bool "MIPS JAZZ FAS216 SCSI support"
+	depends on MACH_JAZZ && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is the driver for the onboard SCSI host adapter of MIPS Magnum
+	  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
+	  systems.
+
+config A3000_SCSI
+	tristate "A3000 WD33C93A support"
+	depends on AMIGA && SCSI
+	help
+	  If you have an Amiga 3000 and have SCSI devices connected to the
+	  built-in SCSI controller, say Y. Otherwise, say N.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called a3000.
+
+config A2091_SCSI
+	tristate "A2091/A590 WD33C93A support"
+	depends on ZORRO && SCSI
+	help
+	  If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
+	  say N.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called a2091.
+
+config GVP11_SCSI
+	tristate "GVP Series II WD33C93A support"
+	depends on ZORRO && SCSI
+	---help---
+	  If you have a Great Valley Products Series II SCSI controller,
+	  answer Y. Also say Y if you have a later model of GVP SCSI
+	  controller (such as the GVP A4008 or a Combo board). Otherwise,
+	  answer N. This driver does NOT work for the T-Rex series of
+	  accelerators from TekMagic and GVP-M.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called gvp11.
+
+config CYBERSTORM_SCSI
+	tristate "CyberStorm SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga with an original (MkI) Phase5 Cyberstorm
+	  accelerator board and the optional Cyberstorm SCSI controller,
+	  answer Y. Otherwise, say N.
+
+config CYBERSTORMII_SCSI
+	tristate "CyberStorm Mk II SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
+	  and the optional Cyberstorm SCSI controller, say Y. Otherwise,
+	  answer N.
+
+config BLZ2060_SCSI
+	tristate "Blizzard 2060 SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
+	  and want to use the onboard SCSI controller, say Y. Otherwise,
+	  answer N.
+
+config BLZ1230_SCSI
+	tristate "Blizzard 1230IV/1260 SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
+	  1260 accelerator, and the optional SCSI module, say Y. Otherwise,
+	  say N.
+
+config FASTLANE_SCSI
+	tristate "Fastlane SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
+	  one in the near future, say Y to this question. Otherwise, say N.
+
+config SCSI_A4000T
+	tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
+	depends on AMIGA && SCSI && EXPERIMENTAL
+	select SCSI_SPI_ATTRS
+	help
+	  If you have an Amiga 4000T and have SCSI devices connected to the
+	  built-in SCSI controller, say Y. Otherwise, say N.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called a4000t.
+
+config SCSI_ZORRO7XX
+	tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
+	depends on ZORRO && SCSI && EXPERIMENTAL
+	select SCSI_SPI_ATTRS
+	help
+	  Support for various NCR53c710-based SCSI controllers on Zorro
+	  expansion boards for the Amiga.
+	  This includes:
+	    - the Amiga 4091 Zorro III SCSI-2 controller,
+	    - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
+	      (info at
+	      <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
+	    - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
+	      accelerator card for the Amiga 1200,
+	    - the SCSI controller on the GVP Turbo 040/060 accelerator.
+
+config OKTAGON_SCSI
+	tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
+	depends on ZORRO && SCSI && EXPERIMENTAL
+	help
+	  If you have the BSC Oktagon SCSI disk controller for the Amiga, say
+	  Y to this question.  If you're in doubt about whether you have one,
+	  see the picture at
+	  <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
+
+config ATARI_SCSI
+	tristate "Atari native SCSI support"
+	depends on ATARI && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  If you have an Atari with built-in NCR5380 SCSI controller (TT,
+	  Falcon, ...) say Y to get it supported. Of course also, if you have
+	  a compatible SCSI controller (e.g. for Medusa).
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called atari_scsi.
+
+	  This driver supports both styles of NCR integration into the
+	  system: the TT style (separate DMA), and the Falcon style (via
+	  ST-DMA, replacing ACSI).  It does NOT support other schemes, like
+	  in the Hades (without DMA).
+
+config ATARI_SCSI_TOSHIBA_DELAY
+	bool "Long delays for Toshiba CD-ROMs"
+	depends on ATARI_SCSI
+	help
+	  This option increases the delay after a SCSI arbitration to
+	  accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
+	  use a Toshiba CD-ROM drive; otherwise, the option is not needed and
+	  would impact performance a bit, so say N.
+
+config ATARI_SCSI_RESET_BOOT
+	bool "Reset SCSI-devices at boottime"
+	depends on ATARI_SCSI
+	help
+	  Reset the devices on your Atari whenever it boots.  This makes the
+	  boot process fractionally longer but may assist recovery from errors
+	  that leave the devices with SCSI operations partway completed.
+
+config TT_DMA_EMUL
+	bool "Hades SCSI DMA emulator"
+	depends on ATARI_SCSI && HADES
+	help
+	  This option enables code which emulates the TT SCSI DMA chip on the
+	  Hades. This increases the SCSI transfer rates at least ten times
+	  compared to PIO transfers.
+
+config MAC_SCSI
+	bool "Macintosh NCR5380 SCSI"
+	depends on MAC && SCSI=y
+	select SCSI_SPI_ATTRS
+	help
+	  This is the NCR 5380 SCSI controller included on most of the 68030
+	  based Macintoshes.  If you have one of these say Y and read the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+config SCSI_MAC_ESP
+	tristate "Macintosh NCR53c9[46] SCSI"
+	depends on MAC && SCSI
+	help
+	  This is the NCR 53c9x SCSI controller found on most of the 68040
+	  based Macintoshes.  If you have one of these say Y and read the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mac_esp.
+
+config MVME147_SCSI
+	bool "WD33C93 SCSI driver for MVME147"
+	depends on MVME147 && SCSI=y
+	select SCSI_SPI_ATTRS
+	help
+	  Support for the on-board SCSI controller on the Motorola MVME147
+	  single-board computer.
+
+config MVME16x_SCSI
+	tristate "NCR53C710 SCSI driver for MVME16x"
+	depends on MVME16x && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
+	  SCSI controller chip.  Almost everyone using one of these boards
+	  will want to say Y to this question.
+
+config BVME6000_SCSI
+	tristate "NCR53C710 SCSI driver for BVME6000"
+	depends on BVME6000 && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
+	  SCSI controller chip.  Almost everyone using one of these boards
+	  will want to say Y to this question.
+
+config SUN3_SCSI
+	tristate "Sun3 NCR5380 SCSI"
+	depends on SUN3 && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This option will enable support for the OBIO (onboard io) NCR5380
+	  SCSI controller found in the Sun 3/50 and 3/60, as well as for
+	  "Sun3" type VME scsi controllers also based on the NCR5380.
+	  General Linux information on the Sun 3 series (now discontinued)
+	  is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
+
+config SUN3X_ESP
+	bool "Sun3x ESP SCSI"
+	depends on SUN3X && SCSI=y
+	help
+	  The ESP was an on-board SCSI controller used on Sun 3/80
+	  machines.  Say Y here to compile in support for it.
+
+config SCSI_SUNESP
+	tristate "Sparc ESP Scsi Driver"
+	depends on SBUS && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is the driver for the Sun ESP SCSI host adapter. The ESP
+	  chipset is present in most SPARC SBUS-based computers.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called esp.
+
+config ZFCP
+	tristate "FCP host bus adapter driver for IBM eServer zSeries"
+	depends on S390 && QDIO && SCSI
+	select SCSI_FC_ATTRS
+	help
+          If you want to access SCSI devices attached to your IBM eServer
+          zSeries by means of Fibre Channel interfaces say Y.
+          For details please refer to the documentation provided by IBM at
+          <http://oss.software.ibm.com/developerworks/opensource/linux390>
+
+          This driver is also available as a module. This module will be
+          called zfcp. If you want to compile it as a module, say M here
+          and read <file:Documentation/kbuild/modules.txt>.
+
+config SCSI_SRP
+	tristate "SCSI RDMA Protocol helper library"
+	depends on SCSI && PCI
+	select SCSI_TGT
+	help
+	  If you wish to use SRP target drivers, say Y.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called libsrp.
+
+endif # SCSI_LOWLEVEL
+
+source "drivers/scsi/pcmcia/Kconfig"
+
+endmenu


-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Adrian Bunk]

On Fri, Sep 14, 2007 at 10:01:18PM +0200, Stefan Richter wrote:
> On 14 Sep, Adrian Bunk wrote:
> > On Fri, Sep 14, 2007 at 09:00:33PM +0200, Sam Ravnborg wrote:
> >> Hi Stefan.
> >> 
> >> Such a patch really calls for some minimal unifacation among
> >> the architectures.
> >> 
> >> > 
> >> >  arch/alpha/Kconfig            |    2 
> >> >  arch/arm/Kconfig              |    2 
> >> >  arch/avr32/Kconfig            |    2 
> >> >  arch/blackfin/Kconfig         |    2 
> >> >  arch/cris/Kconfig             |    2 
> >> >  arch/frv/Kconfig              |    2 
> >> >  arch/i386/Kconfig             |    2 
> >> >  arch/ia64/Kconfig             |    2 
> >> >  arch/m32r/Kconfig             |    2 
> >> >  arch/m68k/Kconfig             |    2 
> >> >  arch/m68knommu/Kconfig        |    2 
> >> >  arch/mips/Kconfig             |    2 
> >> >  arch/parisc/Kconfig           |    2 
> >> >  arch/powerpc/Kconfig          |    2 
> >> >  arch/ppc/Kconfig              |    2 
> >> >  arch/s390/Kconfig             |    2 
> >> >  arch/sh/Kconfig               |    2 
> >> >  arch/sh64/Kconfig             |    2 
> >> >  arch/sparc/Kconfig            |    2 
> >> >  arch/sparc64/Kconfig          |    2 
> >> >  arch/um/Kconfig               |    2 
> >> >  arch/v850/Kconfig             |    2 
> >> >  arch/x86_64/Kconfig           |    4 
> >> >  arch/xtensa/Kconfig           |    2 
> >> 
> >> 
> >> Exactly the same change for all architectures.
> >> IT would be good to introduce a common file that contains
> >> some of the shared stuff from the different architectures.
> >> We could start out simple with:
> >> 
> >> arch/Kconfig.arch:
> >>...
> 
> Yes, that would be good.  But Adrian has a point too.
> 
> > Stefan simply shouldn't move it out of drivers/Kconfig.
>...
>  drivers/Kconfig               |    4 
>  drivers/scsi/Kconfig          | 1589 ----------------------------------
>  drivers/scsi/Kconfig.lowlevel | 1578 +++++++++++++++++++++++++++++++++
>  3 files changed, 1588 insertions(+), 1583 deletions(-)

Nearly right.  ;-)

There are a few architectures not (yet) using drivers/Kconfig.

> Index: linux-2.6.23-rc6/drivers/Kconfig
> ===================================================================
> --- linux-2.6.23-rc6.orig/drivers/Kconfig
> +++ linux-2.6.23-rc6/drivers/Kconfig
> @@ -1,5 +1,7 @@
>  # drivers/Kconfig
>  
> +source "drivers/scsi/Kconfig"
> +
>  menu "Device Drivers"
>  
>  source "drivers/base/Kconfig"
> @@ -22,7 +24,7 @@ source "drivers/misc/Kconfig"
>  
>  source "drivers/ide/Kconfig"
>  
> -source "drivers/scsi/Kconfig"
> +source "drivers/scsi/Kconfig.lowlevel"
>  
>  source "drivers/ata/Kconfig"
>...

This way the order is wrong:

There should first be the lowlevel SCSI, SATA, USB etc. drivers, these 
drivers should select CONFIG_SCSI, and then the menu offering support 
for disk, CD,...

> Index: linux-2.6.23-rc6/drivers/scsi/Kconfig
> ===================================================================
> --- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig
> +++ linux-2.6.23-rc6/drivers/scsi/Kconfig
> @@ -1,14 +1,7 @@
> -menu "SCSI device support"
> -
> -config RAID_ATTRS
> -	tristate "RAID Transport Class"
> -	default n
> -	depends on BLOCK
> -	---help---
> -	  Provides RAID
> +menu "Storage (core and SCSI commands)"
>  
>  config SCSI
> -	tristate "SCSI device support"
> +	tristate "Storage support (core and SCSI commands)"
>  	depends on BLOCK
>  	select SCSI_DMA if HAS_DMA
>  	---help---
>...

What is "storage support"?
SATA?
PATA?
USB mass storage?
MMC?
MTD?

Whether or not a driver uses the SCSI layer is an implementation detail 
(it even differs for the two USB mass storage implementations and the 
two PATA implementations in the kernel) the user shouldn't have to know 
about.

I don't see any reason why CONFIG_SCSI should have to stay user-visible 
at all after your patch.

> Stefan Richter

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Stefan Richter]

Adrian Bunk wrote:
> On Fri, Sep 14, 2007 at 10:01:18PM +0200, Stefan Richter wrote:
>>  drivers/Kconfig               |    4 
>>  drivers/scsi/Kconfig          | 1589 ----------------------------------
>>  drivers/scsi/Kconfig.lowlevel | 1578 +++++++++++++++++++++++++++++++++
>>  3 files changed, 1588 insertions(+), 1583 deletions(-)
> 
> Nearly right.  ;-)
> 
> There are a few architectures not (yet) using drivers/Kconfig.

Right, the patch is wrong for those architectures which include
drivers/scsi/Kconfig directly, rather than indirectly via drivers/Kconfig.

[...]
>>  # drivers/Kconfig
>>  
>> +source "drivers/scsi/Kconfig"
>> +
>>  menu "Device Drivers"
>>  
>>  source "drivers/base/Kconfig"
>> @@ -22,7 +24,7 @@ source "drivers/misc/Kconfig"
>>  
>>  source "drivers/ide/Kconfig"
>>  
>> -source "drivers/scsi/Kconfig"
>> +source "drivers/scsi/Kconfig.lowlevel"
>>  
>>  source "drivers/ata/Kconfig"
>> ...
> 
> This way the order is wrong:
> 
> There should first be the lowlevel SCSI, SATA, USB etc. drivers, these 
> drivers should select CONFIG_SCSI, and then the menu offering support 
> for disk, CD,...

The order was inspired by

	# the protocols etc.
	"Networking"

	# the interconnects
	"Device Drivers"/ "Network device support"

So that order is wrong too?

However, there is also precedence for the order which you suggest:  The
partition and filesystems options come after device driver options.

[...]
>> +menu "Storage (core and SCSI commands)"
>>  
>>  config SCSI
>> -	tristate "SCSI device support"
>> +	tristate "Storage support (core and SCSI commands)"
>>  	depends on BLOCK
>>  	select SCSI_DMA if HAS_DMA
>>  	---help---
>> ...
> 
> What is "storage support"?
> SATA?
> PATA?
> USB mass storage?
> MMC?
> MTD?

What is "Networking"?  Ethernet?  Infiniband?  ...?

> Whether or not a driver uses the SCSI layer is an implementation detail 
> (it even differs for the two USB mass storage implementations and the 
> two PATA implementations in the kernel) the user shouldn't have to know 
> about.
> 
> I don't see any reason why CONFIG_SCSI should have to stay user-visible 
> at all after your patch.

Vice versa, I don't see any reason for "select SCSI" anywhere after my
patch.
-- 
Stefan Richter
-=====-=-=== =--= -====
http://arcgraph.de/sr/

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Adrian Bunk]

On Sat, Sep 15, 2007 at 02:24:17PM +0200, Stefan Richter wrote:
> Adrian Bunk wrote:
>...
> >>  # drivers/Kconfig
> >>  
> >> +source "drivers/scsi/Kconfig"
> >> +
> >>  menu "Device Drivers"
> >>  
> >>  source "drivers/base/Kconfig"
> >> @@ -22,7 +24,7 @@ source "drivers/misc/Kconfig"
> >>  
> >>  source "drivers/ide/Kconfig"
> >>  
> >> -source "drivers/scsi/Kconfig"
> >> +source "drivers/scsi/Kconfig.lowlevel"
> >>  
> >>  source "drivers/ata/Kconfig"
> >> ...
> > 
> > This way the order is wrong:
> > 
> > There should first be the lowlevel SCSI, SATA, USB etc. drivers, these 
> > drivers should select CONFIG_SCSI, and then the menu offering support 
> > for disk, CD,...
> 
> The order was inspired by
> 
> 	# the protocols etc.
> 	"Networking"
> 
> 	# the interconnects
> 	"Device Drivers"/ "Network device support"
> 
> So that order is wrong too?

It's different since _all_ network device drivers require networking 
support.

> However, there is also precedence for the order which you suggest:  The
> partition and filesystems options come after device driver options.
> 
> [...]
> >> +menu "Storage (core and SCSI commands)"
> >>  
> >>  config SCSI
> >> -	tristate "SCSI device support"
> >> +	tristate "Storage support (core and SCSI commands)"
> >>  	depends on BLOCK
> >>  	select SCSI_DMA if HAS_DMA
> >>  	---help---
> >> ...
> > 
> > What is "storage support"?
> > SATA?
> > PATA?
> > USB mass storage?
> > MMC?
> > MTD?
> 
> What is "Networking"?  Ethernet?  Infiniband?  ...?

Different to CONFIG_SCSI, CONFIG_NET=n is so exotic that we should 
change it to no longer show users the question unless CONFIG_EMBEDDED=y.

> > Whether or not a driver uses the SCSI layer is an implementation detail 
> > (it even differs for the two USB mass storage implementations and the 
> > two PATA implementations in the kernel) the user shouldn't have to know 
> > about.
> > 
> > I don't see any reason why CONFIG_SCSI should have to stay user-visible 
> > at all after your patch.
> 
> Vice versa, I don't see any reason for "select SCSI" anywhere after my
> patch.

If users who don't need it now enable CONFIG_SCSI (and drivers/ide/ 
usage is not that uncommon) that's a regression in the user interface.

If the lowlevel SCSI drivers move into a separate menu as your patch 
does, we simply no longer have any good reason for bothering the user 
with the CONFIG_SCSI.

> Stefan Richter

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Stefan Richter]

Adrian Bunk wrote:
>>> There should first be the lowlevel SCSI, SATA, USB etc. drivers, these 
>>> drivers should select CONFIG_SCSI, and then the menu offering support 
>>> for disk, CD,...
...
> If users who don't need it now enable CONFIG_SCSI (and drivers/ide/ 
> usage is not that uncommon) that's a regression in the user interface.

Aha, first all interconnects/transports are configured.  If none of them
'select'ed SCSI, the menu for sd, sr, st stays invisible.  Otherwise it
is exposed.

It still doesn't entirely clarify whether users need sd, sr, st, and
whether thy need sd for the disk with root filesystem.
-- 
Stefan Richter
-=====-=-=== =--= -====
http://arcgraph.de/sr/

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Adrian Bunk]

On Sat, Sep 15, 2007 at 03:20:06PM +0200, Stefan Richter wrote:
> Adrian Bunk wrote:
> >>> There should first be the lowlevel SCSI, SATA, USB etc. drivers, these 
> >>> drivers should select CONFIG_SCSI, and then the menu offering support 
> >>> for disk, CD,...
> ...
> > If users who don't need it now enable CONFIG_SCSI (and drivers/ide/ 
> > usage is not that uncommon) that's a regression in the user interface.
> 
> Aha, first all interconnects/transports are configured.  If none of them
> 'select'ed SCSI, the menu for sd, sr, st stays invisible.  Otherwise it
> is exposed.
> 
> It still doesn't entirely clarify whether users need sd, sr, st, and
> whether thy need sd for the disk with root filesystem.

If you want to do it in a really perfect way, help texts aren't the 
solution. You'll have to make the options like CONFIG_BLK_DEV_SR no 
longer be user visible and select'ed through dummy options like e.g.:

config USB_STORAGE
        tristate "USB Mass Storage support"
        depends on USB
	select SCSI
	help
	  ...

config USB_STORAGE_SD
	tristate "USB Mass Storage hard disk support"
	depends on USB_STORAGE
	select BLK_DEV_SD
	help
	  ...

config USB_STORAGE_SR
        tristate "USB Mass Storage CD/DVD support"
        depends on USB_STORAGE
	select BLK_DEV_SR
        help
          ...


> Stefan Richter

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Stefan Richter]

Adrian Bunk wrote:
> On Sat, Sep 15, 2007 at 03:20:06PM +0200, Stefan Richter wrote:
>> It still doesn't entirely clarify whether users need sd, sr, st, and
>> whether thy need sd for the disk with root filesystem.
> 
> If you want to do it in a really perfect way, help texts aren't the 
> solution. You'll have to make the options like CONFIG_BLK_DEV_SR no 
> longer be user visible and select'ed through dummy options like e.g.:
...
> 	tristate "USB Mass Storage hard disk support"
> 	depends on USB_STORAGE
> 	select BLK_DEV_SD
...
>         tristate "USB Mass Storage CD/DVD support"
>         depends on USB_STORAGE
> 	select BLK_DEV_SR
...

Perfect is in the eye of the beholder.  You would consequently have to
add such options into all menus which contain scsi low-level providers.

Also, one more question on whether CONFIG_SCSI ought to be 'select'ed:
Where do scsi-core options like CONFIG_SCSI_CONSTANTS go?
-- 
Stefan Richter
-=====-=-=== =--= -====
http://arcgraph.de/sr/

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Adrian Bunk]

On Sat, Sep 15, 2007 at 04:11:45PM +0200, Stefan Richter wrote:
> Adrian Bunk wrote:
> > On Sat, Sep 15, 2007 at 03:20:06PM +0200, Stefan Richter wrote:
> >> It still doesn't entirely clarify whether users need sd, sr, st, and
> >> whether thy need sd for the disk with root filesystem.
> > 
> > If you want to do it in a really perfect way, help texts aren't the 
> > solution. You'll have to make the options like CONFIG_BLK_DEV_SR no 
> > longer be user visible and select'ed through dummy options like e.g.:
> ...
> > 	tristate "USB Mass Storage hard disk support"
> > 	depends on USB_STORAGE
> > 	select BLK_DEV_SD
> ...
> >         tristate "USB Mass Storage CD/DVD support"
> >         depends on USB_STORAGE
> > 	select BLK_DEV_SR
> ...
> 
> Perfect is in the eye of the beholder.  You would consequently have to
> add such options into all menus which contain scsi low-level providers.

Kconfig is a user interface, so perfect is what is best for the
kconfig users.

> Also, one more question on whether CONFIG_SCSI ought to be 'select'ed:
> Where do scsi-core options like CONFIG_SCSI_CONSTANTS go?

The first question is whether it's for actual SCSI hardware [1] or for 
the block layer functionality which the SCSI subsystem has become.
The mixture of these two is the root of much user confusion.

With the help text "The error messages regarding your SCSI hardware will 
be easier to understand if you say Y here" a user wouldn't have expected 
to see you using it in a firewire driver. But unless I miss anything, 
the setting of SCSI_SCAN_ASYNC does only affect "real" SCSI hardware.

If you check each option and place it either in the generic storage menu 
or the SCSI lowlevel menu this would fix much possible user confusion.

But these are relatively unimportant options compared to e.g.
USB_STORAGE=y, BLK_DEV_SD=n, which is a misconfiguration many
users run into, so having one menu somewhere with these advanced 
options should be enough.

> Stefan Richter

cu
Adrian

[1] SCSI as in "sold as SCSI"

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Stefan Richter]

Adrian Bunk wrote:
> On Sat, Sep 15, 2007 at 04:11:45PM +0200, Stefan Richter wrote:
>> Perfect is in the eye of the beholder.  You would consequently have to
>> add such options into all menus which contain scsi low-level providers.
> 
> Kconfig is a user interface, so perfect is what is best for the
> kconfig users.

Duplicate options with different names in different menus, but which all
do the same, --- is this the best for users?

>> Also, one more question on whether CONFIG_SCSI ought to be 'select'ed:
>> Where do scsi-core options like CONFIG_SCSI_CONSTANTS go?
> 
> The first question is whether it's for actual SCSI hardware [1] or for 
> the block layer functionality which the SCSI subsystem has become.
> The mixture of these two is the root of much user confusion.
> 
> With the help text "The error messages regarding your SCSI hardware will 
> be easier to understand if you say Y here" a user wouldn't have expected 
> to see you using it in a firewire driver.

FireWire hardware which implements SBP-2 is SCSI hardware...  But this
detail aside --- yes, of course this help text is old and misleading.

> But unless I miss anything, 
> the setting of SCSI_SCAN_ASYNC does only affect "real" SCSI hardware.

It affects every hardware which is driven by scsi low-level providers
which have been integrated with the SCSI_SCAN_ASYNC facility.

> If you check each option and place it either in the generic storage menu 
> or the SCSI lowlevel menu this would fix much possible user confusion.
> 
> But these are relatively unimportant options compared to e.g.
> USB_STORAGE=y, BLK_DEV_SD=n, which is a misconfiguration many
> users run into, so having one menu somewhere with these advanced 
> options should be enough.

True.

So,
    config SCSI_CONSTANTS
        "Kernel log messages from the SCSI subsystem will be easier to
        understand if you say Y here..."
would say what this option really does.  But to some degree the need to
explain what the SCSI subsystem or SCSI core is and which other
subsystems make use of it remains.  Maybe it's OK to provide
documentation of this kind outside of Kconfig help though.

> [1] SCSI as in "sold as SCSI"

Difficult.  Does e.g. hardware sold as SAS count as "sold as SCSI"?  How
about SBP-2 then?  ;-)
-- 
Stefan Richter
-=====-=-=== =--= -====
http://arcgraph.de/sr/

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Jeff Garzik]

Stefan Richter wrote:
> Adrian Bunk wrote:
>> On Sat, Sep 15, 2007 at 04:11:45PM +0200, Stefan Richter wrote:
>>> Perfect is in the eye of the beholder.  You would consequently have to
>>> add such options into all menus which contain scsi low-level providers.
>> Kconfig is a user interface, so perfect is what is best for the
>> kconfig users.
> 
> Duplicate options with different names in different menus, but which all
> do the same, --- is this the best for users?

I recognize it's a rhetorical question :)  The answer is of course "no".

I hope the other participants of this thread register the severe 
disinclination of the maintainers to change this stuff, as this is a 
classic case of making a mountain out of a molehill[1].

For the -vast majority- of people configuring the kernel, this is not a 
problem.  Kernel people are -expected- to know what they're doing, 
especially when switching from one major subsystem to another.

Therefore, all this is IMO wasted effort and hot air.  There are far 
more important issues to deal with.

	Jeff


[1] http://www.bartleby.com/59/4/makeamountai.html

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Adrian Bunk]

On Sat, Sep 15, 2007 at 11:44:59AM -0400, Jeff Garzik wrote:
> Stefan Richter wrote:
>> Adrian Bunk wrote:
>>> On Sat, Sep 15, 2007 at 04:11:45PM +0200, Stefan Richter wrote:
>>>> Perfect is in the eye of the beholder.  You would consequently have to
>>>> add such options into all menus which contain scsi low-level providers.
>>> Kconfig is a user interface, so perfect is what is best for the
>>> kconfig users.
>> Duplicate options with different names in different menus, but which all
>> do the same, --- is this the best for users?
>
> I recognize it's a rhetorical question :)  The answer is of course "no".
>
> I hope the other participants of this thread register the severe 
> disinclination of the maintainers to change this stuff, as this is a 
> classic case of making a mountain out of a molehill[1].
>
> For the -vast majority- of people configuring the kernel, this is not a 
> problem.  Kernel people are -expected- to know what they're doing, 

I doubt your claim is true since the vast majority of kconfig users
are most likely not kernel developers.

@Greg:
Do you have any numbers regarding how your "Linux Kernel in a Nutshell" 
is selling?
Even download numbers?

> especially when switching from one major subsystem to another.

It's not only about switching, the same problems awaits people when 
configuring a kernel for their hardware the first time.

> Therefore, all this is IMO wasted effort and hot air.  There are far more 
> important issues to deal with.

Why don't we dump kconfig and write the .config by hand?  ;-)

More seriously:
Yes, there are many other important issues in the kernel.
But not fixing kconfig UI problems doesn't fix these issues faster.

I have seen people running into problems because some required 
option wasn't set - in the simplest cases things like IDE without DMA 
because a help text wasn't updated when more hardware support was added 
to a driver.

You might not care about the kconfig users.
But other people do.

> 	Jeff
>...

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Bartlomiej Zolnierkiewicz]

On Saturday 15 September 2007, Adrian Bunk wrote:
> On Sat, Sep 15, 2007 at 11:44:59AM -0400, Jeff Garzik wrote:
> > Stefan Richter wrote:
> >> Adrian Bunk wrote:
> >>> On Sat, Sep 15, 2007 at 04:11:45PM +0200, Stefan Richter wrote:
> >>>> Perfect is in the eye of the beholder.  You would consequently have to
> >>>> add such options into all menus which contain scsi low-level providers.
> >>> Kconfig is a user interface, so perfect is what is best for the
> >>> kconfig users.
> >> Duplicate options with different names in different menus, but which all
> >> do the same, --- is this the best for users?
> >
> > I recognize it's a rhetorical question :)  The answer is of course "no".
> >
> > I hope the other participants of this thread register the severe 
> > disinclination of the maintainers to change this stuff, as this is a 
> > classic case of making a mountain out of a molehill[1].
> >
> > For the -vast majority- of people configuring the kernel, this is not a 
> > problem.  Kernel people are -expected- to know what they're doing, 
> 
> I doubt your claim is true since the vast majority of kconfig users
> are most likely not kernel developers.

Yes, we shouldn't be needlessly raising the bar for power users.

> @Greg:
> Do you have any numbers regarding how your "Linux Kernel in a Nutshell" 
> is selling?
> Even download numbers?
> 
> > especially when switching from one major subsystem to another.
> 
> It's not only about switching, the same problems awaits people when 
> configuring a kernel for their hardware the first time.

*nods*

> > Therefore, all this is IMO wasted effort and hot air.  There are far more 
> > important issues to deal with.
> 
> Why don't we dump kconfig and write the .config by hand?  ;-)
> 
> More seriously:
> Yes, there are many other important issues in the kernel.
> But not fixing kconfig UI problems doesn't fix these issues faster.

Agreed, and actually not fixing Kconfig UI problems will make the other
issues being fixed *slower* (because they result in *increased* workload
on developers' side).

> I have seen people running into problems because some required 
> option wasn't set - in the simplest cases things like IDE without DMA 
> because a help text wasn't updated when more hardware support was added 
> to a driver.

This is why nowadays IDE DMA support is automatically selected by IDE
host drivers that need it - a big relief for everybody.

> You might not care about the kconfig users.
> But other people do.

...and even if their attempts/solutions may not be proper yet they should
not be discouraged to work on these problems...

Thanks,
Bart

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Jeff Garzik]

Bartlomiej Zolnierkiewicz wrote:
> On Saturday 15 September 2007, Adrian Bunk wrote:
>> On Sat, Sep 15, 2007 at 11:44:59AM -0400, Jeff Garzik wrote:
>>> Stefan Richter wrote:
>>>> Adrian Bunk wrote:
>>>>> On Sat, Sep 15, 2007 at 04:11:45PM +0200, Stefan Richter wrote:
>>>>>> Perfect is in the eye of the beholder.  You would consequently have to
>>>>>> add such options into all menus which contain scsi low-level providers.
>>>>> Kconfig is a user interface, so perfect is what is best for the
>>>>> kconfig users.
>>>> Duplicate options with different names in different menus, but which all
>>>> do the same, --- is this the best for users?
>>> I recognize it's a rhetorical question :)  The answer is of course "no".
>>>
>>> I hope the other participants of this thread register the severe 
>>> disinclination of the maintainers to change this stuff, as this is a 
>>> classic case of making a mountain out of a molehill[1].
>>>
>>> For the -vast majority- of people configuring the kernel, this is not a 
>>> problem.  Kernel people are -expected- to know what they're doing, 
>> I doubt your claim is true since the vast majority of kconfig users
>> are most likely not kernel developers.
> 
> Yes, we shouldn't be needlessly raising the bar for power users.

In this case, no bar is being "raised," for any user.


>> @Greg:
>> Do you have any numbers regarding how your "Linux Kernel in a Nutshell" 
>> is selling?
>> Even download numbers?
>>
>>> especially when switching from one major subsystem to another.
>> It's not only about switching, the same problems awaits people when 
>> configuring a kernel for their hardware the first time.
> 
> *nods*
> 
>>> Therefore, all this is IMO wasted effort and hot air.  There are far more 
>>> important issues to deal with.
>> Why don't we dump kconfig and write the .config by hand?  ;-)
>>
>> More seriously:
>> Yes, there are many other important issues in the kernel.
>> But not fixing kconfig UI problems doesn't fix these issues faster.
> 
> Agreed, and actually not fixing Kconfig UI problems will make the other
> issues being fixed *slower* (because they result in *increased* workload
> on developers' side).

Irrelevant in this case, because there is no increased workload on the 
developer's side.


>> I have seen people running into problems because some required 
>> option wasn't set - in the simplest cases things like IDE without DMA 
>> because a help text wasn't updated when more hardware support was added 
>> to a driver.
> 
> This is why nowadays IDE DMA support is automatically selected by IDE
> host drivers that need it - a big relief for everybody.

Please don't take this any more off-topic than it already is.

IDE DMA option was vastly different.  The options in question here 
affect whether or not you have a block device to use -- something that 
is immediately obviously and corrected quickly.


>> You might not care about the kconfig users.
>> But other people do.
> 
> ...and even if their attempts/solutions may not be proper yet they should
> not be discouraged to work on these problems...

There is no problem, in this case.

Otherwise, there would be more than a complaint or two per year.

	Jeff

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Bartlomiej Zolnierkiewicz]

On Saturday 15 September 2007, Jeff Garzik wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > On Saturday 15 September 2007, Adrian Bunk wrote:
> >> On Sat, Sep 15, 2007 at 11:44:59AM -0400, Jeff Garzik wrote:
> >>> Stefan Richter wrote:
> >>>> Adrian Bunk wrote:
> >>>>> On Sat, Sep 15, 2007 at 04:11:45PM +0200, Stefan Richter wrote:
> >>>>>> Perfect is in the eye of the beholder.  You would consequently have to
> >>>>>> add such options into all menus which contain scsi low-level providers.
> >>>>> Kconfig is a user interface, so perfect is what is best for the
> >>>>> kconfig users.
> >>>> Duplicate options with different names in different menus, but which all
> >>>> do the same, --- is this the best for users?
> >>> I recognize it's a rhetorical question :)  The answer is of course "no".
> >>>
> >>> I hope the other participants of this thread register the severe 
> >>> disinclination of the maintainers to change this stuff, as this is a 
> >>> classic case of making a mountain out of a molehill[1].
> >>>
> >>> For the -vast majority- of people configuring the kernel, this is not a 
> >>> problem.  Kernel people are -expected- to know what they're doing, 
> >> I doubt your claim is true since the vast majority of kconfig users
> >> are most likely not kernel developers.
> > 
> > Yes, we shouldn't be needlessly raising the bar for power users.
> 
> In this case, no bar is being "raised," for any user.

It has already been raised by making SATA configuration counterintuitive
(SATA has a separate Kconfig menu but depends on SCSI device drivers).

> >> @Greg:
> >> Do you have any numbers regarding how your "Linux Kernel in a Nutshell" 
> >> is selling?
> >> Even download numbers?
> >>
> >>> especially when switching from one major subsystem to another.
> >> It's not only about switching, the same problems awaits people when 
> >> configuring a kernel for their hardware the first time.
> > 
> > *nods*
> > 
> >>> Therefore, all this is IMO wasted effort and hot air.  There are far more 
> >>> important issues to deal with.
> >> Why don't we dump kconfig and write the .config by hand?  ;-)
> >>
> >> More seriously:
> >> Yes, there are many other important issues in the kernel.
> >> But not fixing kconfig UI problems doesn't fix these issues faster.
> > 
> > Agreed, and actually not fixing Kconfig UI problems will make the other
> > issues being fixed *slower* (because they result in *increased* workload
> > on developers' side).
> 
> Irrelevant in this case, because there is no increased workload on the 
> developer's side.

This thread alone serves as a perfect counter-example. ;)

> >> I have seen people running into problems because some required 
> >> option wasn't set - in the simplest cases things like IDE without DMA 
> >> because a help text wasn't updated when more hardware support was added 
> >> to a driver.
> > 
> > This is why nowadays IDE DMA support is automatically selected by IDE
> > host drivers that need it - a big relief for everybody.
> 
> Please don't take this any more off-topic than it already is.

OK, I'll stop here and I'll just patiently wait till the SATA Kconfig
issue comes up again on LKML (then I'll just smile and move on to
the next post 8).

> IDE DMA option was vastly different.  The options in question here 
> affect whether or not you have a block device to use -- something that 
> is immediately obviously and corrected quickly.

Indeed -- completely different situation.

> >> You might not care about the kconfig users.
> >> But other people do.
> > 
> > ...and even if their attempts/solutions may not be proper yet they should
> > not be discouraged to work on these problems...
> 
> There is no problem, in this case.

Fine with me then.  The above was the most important part for me.

> Otherwise, there would be more than a complaint or two per year.

Thanks,
Bart

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Greg KH]

On Sat, Sep 15, 2007 at 06:23:13PM +0200, Adrian Bunk wrote:
> 
> @Greg:
> Do you have any numbers regarding how your "Linux Kernel in a Nutshell" 
> is selling?

It is selling reasonably well for an O'Reilly book from what I have been
told.  But I have not seen any real numbers yet.

> Even download numbers?

The downloads are spread around all of the kernel.org mirrors so I have
absolutely no idea what they are.

Nor do I really want to, as it doesn't matter to me.

thanks,

greg k-h

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Adrian Bunk]

On Sat, Sep 15, 2007 at 05:27:24PM +0200, Stefan Richter wrote:
> Adrian Bunk wrote:
> > On Sat, Sep 15, 2007 at 04:11:45PM +0200, Stefan Richter wrote:
> >> Perfect is in the eye of the beholder.  You would consequently have to
> >> add such options into all menus which contain scsi low-level providers.
> > 
> > Kconfig is a user interface, so perfect is what is best for the
> > kconfig users.
> 
> Duplicate options with different names in different menus, but which all
> do the same, --- is this the best for users?

Different to your approach of trying to achieve the same with one huge 
help text I see a realistic chance of it working.

What's other alternatives do we have?

Automatically select BLK_DEV_SD and BLK_DEV_SR if one driver that uses 
the SCSI layer gets enabled by the user?

> >> Also, one more question on whether CONFIG_SCSI ought to be 'select'ed:
> >> Where do scsi-core options like CONFIG_SCSI_CONSTANTS go?
> > 
> > The first question is whether it's for actual SCSI hardware [1] or for 
> > the block layer functionality which the SCSI subsystem has become.
> > The mixture of these two is the root of much user confusion.
> > 
> > With the help text "The error messages regarding your SCSI hardware will 
> > be easier to understand if you say Y here" a user wouldn't have expected 
> > to see you using it in a firewire driver.
> 
> FireWire hardware which implements SBP-2 is SCSI hardware...  But this
> detail aside --- yes, of course this help text is old and misleading.
> 
> > But unless I miss anything, 
> > the setting of SCSI_SCAN_ASYNC does only affect "real" SCSI hardware.
> 
> It affects every hardware which is driven by scsi low-level providers
> which have been integrated with the SCSI_SCAN_ASYNC facility.
> 
> > If you check each option and place it either in the generic storage menu 
> > or the SCSI lowlevel menu this would fix much possible user confusion.
> > 
> > But these are relatively unimportant options compared to e.g.
> > USB_STORAGE=y, BLK_DEV_SD=n, which is a misconfiguration many
> > users run into, so having one menu somewhere with these advanced 
> > options should be enough.
> 
> True.
> 
> So,
>     config SCSI_CONSTANTS
>         "Kernel log messages from the SCSI subsystem will be easier to
>         understand if you say Y here..."
> would say what this option really does.  But to some degree the need to
> explain what the SCSI subsystem or SCSI core is and which other
> subsystems make use of it remains.  Maybe it's OK to provide
> documentation of this kind outside of Kconfig help though.

This is a debug option and it's unlikely that users will need it unless 
someone explicitely requested them to do so, so it's not such an 
important issue.

> > [1] SCSI as in "sold as SCSI"
> 
> Difficult.  Does e.g. hardware sold as SAS count as "sold as SCSI"?  How
> about SBP-2 then?  ;-)

If SBP-2 is what you get in a shop when asking for an external
Firewire disk enclosure then it's not sold as SCSI.

> Stefan Richter

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Maciej W. Rozycki]

On Sat, 15 Sep 2007, Stefan Richter wrote:

> >> +menu "Storage (core and SCSI commands)"
> >>  
> >>  config SCSI
> >> -	tristate "SCSI device support"
> >> +	tristate "Storage support (core and SCSI commands)"
> >>  	depends on BLOCK
> >>  	select SCSI_DMA if HAS_DMA
> >>  	---help---
> >> ...
> > 
> > What is "storage support"?
> > SATA?
> > PATA?
> > USB mass storage?
> > MMC?
> > MTD?
> 
> What is "Networking"?  Ethernet?  Infiniband?  ...?

 SCSI is a generic peripheral bus (recall the expansion of the acronym).  
Even though probably the most common, storage is one of its applications 
only (think scanners for an immediately obvious other one).  I find 
describing CONFIG_SCSI as "storage support" misleading and inappropriate.

 Referring to your example it is like calling generic networking (i.e. 
CONFIG_NET) "Ethernet support".

  Maciej

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Stefan Richter]

Maciej W. Rozycki wrote:
>  SCSI is a generic peripheral bus

No, not anymore.  http://www.t10.org/scsi-3.htm

> (recall the expansion of the acronym).

The expansion of the acronym doesn't fit anymore to what SCSI is today,
or even to what it became already circa 10 years ago.

> Even though probably the most common, storage is one of its applications 
> only (think scanners for an immediately obvious other one).  I find 
> describing CONFIG_SCSI as "storage support" misleading and inappropriate.

Right.  I wrote that in lack of better words, but at least I added "SCSI
commands" in parentheses.  Something like "SCSI I/O - core and command
sets" would much better describe what it is, but it would put "SCSI"
first again and thus wouldn't reflect that  Linux' SCSI core and
highlevel is in broader use than just for actual SCSI hardware...  Of
course there is no way around the issue that Linux' SCSI core's and
highlevel's role cannot be characterized in 3...6 words only, but there
should be a way to point out its general importance.

>  Referring to your example it is like calling generic networking (i.e. 
> CONFIG_NET) "Ethernet support".

Wrong comparison.
-- 
Stefan Richter
-=====-=-=== =--= =---=
http://arcgraph.de/sr/

Re: [RFC PATCH] SCSI: split Kconfig menu into two

[Stefan Richter]

I wrote:
> Applies after patch "SCSI: update Kconfig help text to indicate SCSI
> core's widespread usage",

Actually the addition "This menu also presents options for specific SCSI
controllers..." from that patch is then no longer true.

> These two patches could very well be collapsed into one.

(I'll gladly do that, or only send an update of the 'split Kconfig menu'
patch with that sentence backed out, if desired.)
-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

[PATCH update] SCSI: split Kconfig menu into two

[Stefan Richter]

Date: 
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: SCSI: split Kconfig menu into two

The SCSI core and SCSI high-level drivers play a central role not just
for the whole lot of different SCSI Architecture types of hardware and
protocols, but also for subsystems which drive non SCSI hardware,
especially libata.

Hence the options pertaining to SCSI core and high-level are separated
out into an own top-level menu outside the "Device Drivers" submenu, and
some prompts are reworded.

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---

Update:  adjusted to "[PATCH update] SCSI: update Kconfig help text to
indicate SCSI core's widespread usage" from September 14, 23:14:21 +0200

 drivers/Kconfig               |    4 
 drivers/scsi/Kconfig          | 1587 ----------------------------------
 drivers/scsi/Kconfig.lowlevel | 1578 +++++++++++++++++++++++++++++++++
 3 files changed, 1584 insertions(+), 1585 deletions(-)

Index: linux-2.6.23-rc6/drivers/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/drivers/Kconfig
+++ linux-2.6.23-rc6/drivers/Kconfig
@@ -1,5 +1,7 @@
 # drivers/Kconfig
 
+source "drivers/scsi/Kconfig"
+
 menu "Device Drivers"
 
 source "drivers/base/Kconfig"
@@ -22,7 +24,7 @@ source "drivers/misc/Kconfig"
 
 source "drivers/ide/Kconfig"
 
-source "drivers/scsi/Kconfig"
+source "drivers/scsi/Kconfig.lowlevel"
 
 source "drivers/ata/Kconfig"
 
Index: linux-2.6.23-rc6/drivers/scsi/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig
+++ linux-2.6.23-rc6/drivers/scsi/Kconfig
@@ -1,14 +1,7 @@
-menu "SCSI device support"
-
-config RAID_ATTRS
-	tristate "RAID Transport Class"
-	default n
-	depends on BLOCK
-	---help---
-	  Provides RAID
+menu "Storage (core and SCSI commands)"
 
 config SCSI
-	tristate "SCSI device support"
+	tristate "Storage support (core and SCSI commands)"
 	depends on BLOCK
 	select SCSI_DMA if HAS_DMA
 	---help---
@@ -32,23 +25,10 @@ config SCSI
 	  or on a device whose driver represents it as SCSI device, as
 	  indicated above.  Choose Y in this case, or set up an initrd.
 
-	  Subsequent options in this menu enable specific SCSI command set
-	  support for harddisks, CD/DVD-ROM/R/W, tapes etc..  This menu also
-	  presents options for specific SCSI controllers, while options for
-	  some other SCSI transports and all non-SCSI controllers are located
-	  in other menus (SATA, USB, FireWire etc.).
-
 config SCSI_DMA
 	bool
 	default n
 
-config SCSI_TGT
-	tristate "SCSI target support"
-	depends on SCSI && EXPERIMENTAL
-	---help---
-	  If you want to use SCSI target mode drivers enable this option.
-	  If you choose M, the module will be called scsi_tgt.
-
 config SCSI_NETLINK
 	bool
 	default	n
@@ -256,1565 +236,4 @@ config SCSI_WAIT_SCAN
 	depends on SCSI
 	depends on MODULES
 
-menu "SCSI Transports"
-	depends on SCSI
-
-config SCSI_SPI_ATTRS
-	tristate "Parallel SCSI (SPI) Transport Attributes"
-	depends on SCSI
-	help
-	  If you wish to export transport-specific information about
-	  each attached SCSI device to sysfs, say Y.  Otherwise, say N.
-
-config SCSI_FC_ATTRS
-	tristate "FiberChannel Transport Attributes"
-	depends on SCSI
-	select SCSI_NETLINK
-	help
-	  If you wish to export transport-specific information about
-	  each attached FiberChannel device to sysfs, say Y.
-	  Otherwise, say N.
-
-config SCSI_ISCSI_ATTRS
-	tristate "iSCSI Transport Attributes"
-	depends on SCSI && NET
-	help
-	  If you wish to export transport-specific information about
-	  each attached iSCSI device to sysfs, say Y.
-	  Otherwise, say N.
-
-config SCSI_SAS_ATTRS
-	tristate "SAS Transport Attributes"
-	depends on SCSI && BLK_DEV_BSG
-	help
-	  If you wish to export transport-specific information about
-	  each attached SAS device to sysfs, say Y.
-
-source "drivers/scsi/libsas/Kconfig"
-
-endmenu
-
-menuconfig SCSI_LOWLEVEL
-	bool "SCSI low-level drivers"
-	depends on SCSI!=n
-	default y
-
-if SCSI_LOWLEVEL
-
-config ISCSI_TCP
-	tristate "iSCSI Initiator over TCP/IP"
-	depends on SCSI && INET
-	select CRYPTO
-	select CRYPTO_MD5
-	select CRYPTO_CRC32C
-	select SCSI_ISCSI_ATTRS
-	help
-	 The iSCSI Driver provides a host with the ability to access storage
-	 through an IP network. The driver uses the iSCSI protocol to transport
-	 SCSI requests and responses over a TCP/IP network between the host
-	 (the "initiator") and "targets".  Architecturally, the iSCSI driver
-	 combines with the host's TCP/IP stack, network drivers, and Network
-	 Interface Card (NIC) to provide the same functions as a SCSI or a
-	 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
-
-	 To compile this driver as a module, choose M here: the
-	 module will be called iscsi_tcp.
-
-	 The userspace component needed to initialize the driver, documentation,
-	 and sample configuration files can be found here:
-
-	 http://linux-iscsi.sf.net
-
-config SGIWD93_SCSI
-	tristate "SGI WD93C93 SCSI Driver"
-	depends on SGI_IP22 && SCSI
-  	help
-	  If you have a Western Digital WD93 SCSI controller on
-	  an SGI MIPS system, say Y.  Otherwise, say N.
-
-config SCSI_DECNCR
-	tristate "DEC NCR53C94 Scsi Driver"
-	depends on MACH_DECSTATION && SCSI && TC
-	help
-	  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
-	  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
-
-config SCSI_DECSII
-	tristate "DEC SII Scsi Driver"
-	depends on MACH_DECSTATION && SCSI && 32BIT
-
-config BLK_DEV_3W_XXXX_RAID
-	tristate "3ware 5/6/7/8xxx ATA-RAID support"
-	depends on PCI && SCSI
-	help
-	  3ware is the only hardware ATA-Raid product in Linux to date.
-	  This card is 2,4, or 8 channel master mode support only.
-	  SCSI support required!!!
-
-	  <http://www.3ware.com/>
-
-	  Please read the comments at the top of
-	  <file:drivers/scsi/3w-xxxx.c>.
-
-config SCSI_3W_9XXX
-	tristate "3ware 9xxx SATA-RAID support"
-	depends on PCI && SCSI
-	help
-	  This driver supports the 9000 series 3ware SATA-RAID cards.
-
-	  <http://www.amcc.com>
-
-	  Please read the comments at the top of
-	  <file:drivers/scsi/3w-9xxx.c>.
-
-config SCSI_7000FASST
-	tristate "7000FASST SCSI support"
-	depends on ISA && SCSI && ISA_DMA_API
-	select CHECK_SIGNATURE
-	help
-	  This driver supports the Western Digital 7000 SCSI host adapter
-	  family.  Some information is in the source:
-	  <file:drivers/scsi/wd7000.c>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called wd7000.
-
-config SCSI_ACARD
-	tristate "ACARD SCSI support"
-	depends on PCI && SCSI
-	help
-	  This driver supports the ACARD SCSI host adapter.
-	  Support Chip <ATP870 ATP876 ATP880 ATP885>
-	  To compile this driver as a module, choose M here: the
-	  module will be called atp870u.
-
-config SCSI_AHA152X
-	tristate "Adaptec AHA152X/2825 support"
-	depends on ISA && SCSI && !64BIT
-	select SCSI_SPI_ATTRS
-	select CHECK_SIGNATURE
-	---help---
-	  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
-	  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
-	  must be manually specified in this case.
-
-	  It is explained in section 3.3 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>. You might also want to
-	  read the file <file:Documentation/scsi/aha152x.txt>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called aha152x.
-
-config SCSI_AHA1542
-	tristate "Adaptec AHA1542 support"
-	depends on ISA && SCSI && ISA_DMA_API
-	---help---
-	  This is support for a SCSI host adapter.  It is explained in section
-	  3.4 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
-	  purchased by Adaptec, and some former Trantor products are being
-	  sold under the Adaptec name.  If it doesn't work out of the box, you
-	  may have to change some settings in <file:drivers/scsi/aha1542.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called aha1542.
-
-config SCSI_AHA1740
-	tristate "Adaptec AHA1740 support"
-	depends on EISA && SCSI
-	---help---
-	  This is support for a SCSI host adapter.  It is explained in section
-	  3.5 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/aha1740.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called aha1740.
-
-config SCSI_AACRAID
-	tristate "Adaptec AACRAID support"
-	depends on SCSI && PCI
-	help
-	  This driver supports a variety of Dell, HP, Adaptec, IBM and
-	  ICP storage products. For a list of supported products, refer
-	  to <file:Documentation/scsi/aacraid.txt>.
-
-	  To compile this driver as a module, choose M here: the module
-	  will be called aacraid.
-
-
-source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
-
-config SCSI_AIC7XXX_OLD
-	tristate "Adaptec AIC7xxx support (old driver)"
-	depends on (ISA || EISA || PCI ) && SCSI
-	help
-	  WARNING This driver is an older aic7xxx driver and is no longer
-	  under active development.  Adaptec, Inc. is writing a new driver to
-	  take the place of this one, and it is recommended that whenever
-	  possible, people should use the new Adaptec written driver instead
-	  of this one.  This driver will eventually be phased out entirely.
-
-	  This is support for the various aic7xxx based Adaptec SCSI
-	  controllers. These include the 274x EISA cards; 284x VLB cards;
-	  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
-	  motherboard based SCSI controllers from Adaptec. It does not support
-	  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
-	  support them. It does not support the 2920 cards from Adaptec that
-	  use the Future Domain SCSI controller chip. For those cards, you
-	  need the "Future Domain 16xx SCSI support" driver.
-
-	  In general, if the controller is based on an Adaptec SCSI controller
-	  chip from the aic777x series or the aic78xx series, this driver
-	  should work. The only exception is the 7810 which is specifically
-	  not supported (that's the RAID controller chip on the AAA-13x
-	  cards).
-
-	  Note that the AHA2920 SCSI host adapter is *not* supported by this
-	  driver; choose "Future Domain 16xx SCSI support" instead if you have
-	  one of those.
-
-	  Information on the configuration options for this controller can be
-	  found by checking the help file for each of the available
-	  configuration options. You should read
-	  <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
-	  contacting the maintainer with any questions.  The SCSI-HOWTO,
-	  available from <http://www.tldp.org/docs.html#howto>, can also
-	  be of great help.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called aic7xxx_old.
-
-source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
-source "drivers/scsi/aic94xx/Kconfig"
-
-# All the I2O code and drivers do not seem to be 64bit safe.
-config SCSI_DPT_I2O
-	tristate "Adaptec I2O RAID support "
-	depends on !64BIT && SCSI && PCI && VIRT_TO_BUS
-	help
-	  This driver supports all of Adaptec's I2O based RAID controllers as 
-	  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
-	  driver by Deanna Bonds.  See <file:Documentation/scsi/dpti.txt>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called dpt_i2o.
-
-config SCSI_ADVANSYS
-	tristate "AdvanSys SCSI support"
-	depends on SCSI
-	depends on ISA || EISA || PCI
-	depends on BROKEN || X86_32
-	help
-	  This is a driver for all SCSI host adapters manufactured by
-	  AdvanSys. It is documented in the kernel source in
-	  <file:drivers/scsi/advansys.c>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called advansys.
-
-config SCSI_IN2000
-	tristate "Always IN2000 SCSI support"
-	depends on ISA && SCSI
-	help
-	  This is support for an ISA bus SCSI host adapter.  You'll find more
-	  information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
-	  out of the box, you may have to change the jumpers for IRQ or
-	  address selection.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called in2000.
-
-config SCSI_ARCMSR
-	tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
-	depends on PCI && SCSI
-	help
-	  This driver supports all of ARECA's SATA RAID controller cards.
-	  This is an ARECA-maintained driver by Erich Chen.
-	  If you have any problems, please mail to: < erich@areca.com.tw >
-	  Areca supports Linux RAID config tools.
-
-	  < http://www.areca.com.tw >
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called arcmsr (modprobe arcmsr).
-
-source "drivers/scsi/megaraid/Kconfig.megaraid"
-
-config SCSI_HPTIOP
-	tristate "HighPoint RocketRAID 3xxx Controller support"
-	depends on SCSI && PCI
-	help
-	  This option enables support for HighPoint RocketRAID 3xxx
-	  controllers.
-
-	  To compile this driver as a module, choose M here; the module
-	  will be called hptiop. If unsure, say N.
-
-config SCSI_BUSLOGIC
-	tristate "BusLogic SCSI support"
-	depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
-	---help---
-	  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
-	  Adapters. Consult the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>, and the files
-	  <file:Documentation/scsi/BusLogic.txt> and
-	  <file:Documentation/scsi/FlashPoint.txt> for more information.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called BusLogic.
-
-config SCSI_OMIT_FLASHPOINT
-	bool "Omit FlashPoint support"
-	depends on SCSI_BUSLOGIC
-	help
-	  This option allows you to omit the FlashPoint support from the
-	  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
-	  substantial, so users of MultiMaster Host Adapters may wish to omit
-	  it.
-
-config SCSI_DMX3191D
-	tristate "DMX3191D SCSI support"
-	depends on PCI && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is support for Domex DMX3191D SCSI Host Adapters.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called dmx3191d.
-
-config SCSI_DTC3280
-	tristate "DTC3180/3280 SCSI support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	select CHECK_SIGNATURE
-	help
-	  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
-	  the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>, and the file
-	  <file:Documentation/scsi/dtc3x80.txt>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called dtc.
-
-config SCSI_EATA
-	tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
-	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
-	---help---
-	  This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
-	  ISA and all EISA I/O addresses are probed looking for the "EATA"
-	  signature. The addresses of all the PCI SCSI controllers reported
-          by the PCI subsystem are probed as well.
-
-	  You want to read the start of <file:drivers/scsi/eata.c> and the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called eata.
-
-config SCSI_EATA_TAGGED_QUEUE
-	bool "enable tagged command queueing"
-	depends on SCSI_EATA
-	help
-	  This is a feature of SCSI-2 which improves performance: the host
-	  adapter can send several SCSI commands to a device's queue even if
-	  previous commands haven't finished yet.
-	  This is equivalent to the "eata=tc:y" boot option.
-
-config SCSI_EATA_LINKED_COMMANDS
-	bool "enable elevator sorting"
-	depends on SCSI_EATA
-	help
-	  This option enables elevator sorting for all probed SCSI disks and
-	  CD-ROMs. It definitely reduces the average seek distance when doing
-	  random seeks, but this does not necessarily result in a noticeable
-	  performance improvement: your mileage may vary...
-	  This is equivalent to the "eata=lc:y" boot option.
-
-config SCSI_EATA_MAX_TAGS
-	int "maximum number of queued commands"
-	depends on SCSI_EATA
-	default "16"
-	help
-	  This specifies how many SCSI commands can be maximally queued for
-	  each probed SCSI device. You should reduce the default value of 16
-	  only if you have disks with buggy or limited tagged command support.
-	  Minimum is 2 and maximum is 62. This value is also the window size
-	  used by the elevator sorting option above. The effective value used
-	  by the driver for each probed SCSI device is reported at boot time.
-	  This is equivalent to the "eata=mq:8" boot option.
-
-config SCSI_EATA_PIO
-	tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
-	depends on (ISA || EISA || PCI) && SCSI && BROKEN
-	---help---
-	  This driver supports all EATA-PIO protocol compliant SCSI Host
-	  Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
-	  host adapters could also use this driver but are discouraged from
-	  doing so, since this driver only supports hard disks and lacks
-	  numerous features.  You might want to have a look at the SCSI-HOWTO,
-	  available from <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called eata_pio.
-
-config SCSI_FUTURE_DOMAIN
-	tristate "Future Domain 16xx SCSI/AHA-2920A support"
-	depends on (ISA || PCI) && SCSI
-	select CHECK_SIGNATURE
-	---help---
-	  This is support for Future Domain's 16-bit SCSI host adapters
-	  (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
-	  other adapters based on the Future Domain chipsets (Quantum
-	  ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
-	  It is explained in section 3.7 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
-	  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
-	  controller support"). This Future Domain driver works with the older
-	  Adaptec AHA-2920A boards with a Future Domain chip on them.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called fdomain.
-
-config SCSI_FD_MCS
-	tristate "Future Domain MCS-600/700 SCSI support"
-	depends on MCA_LEGACY && SCSI
-	---help---
-	  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
-	  Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
-	  is identical to the MCS 700 and hence also supported by this driver.
-	  This driver also supports the Reply SB16/SCSI card (the SCSI part).
-	  It supports multiple adapters in the same system.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called fd_mcs.
-
-config SCSI_GDTH
-	tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
-	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
-	---help---
-	  Formerly called GDT SCSI Disk Array Controller Support.
-
-	  This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 
-	  manufactured by Intel Corporation/ICP vortex GmbH. It is documented
-	  in the kernel source in <file:drivers/scsi/gdth.c> and
-	  <file:drivers/scsi/gdth.h.>
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called gdth.
-
-config SCSI_GENERIC_NCR5380
-	tristate "Generic NCR5380/53c400 SCSI PIO support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This is a driver for the old NCR 53c80 series of SCSI controllers
-	  on boards using PIO. Most boards such as the Trantor T130 fit this
-	  category, along with a large number of ISA 8bit controllers shipped
-	  for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
-	  you should select the specific driver for that card rather than
-	  generic 5380 support.
-
-	  It is explained in section 3.8 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/g_NCR5380.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called g_NCR5380.
-
-config SCSI_GENERIC_NCR5380_MMIO
-	tristate "Generic NCR5380/53c400 SCSI MMIO support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This is a driver for the old NCR 53c80 series of SCSI controllers
-	  on boards using memory mapped I/O. 
-	  It is explained in section 3.8 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/g_NCR5380.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called g_NCR5380_mmio.
-
-config SCSI_GENERIC_NCR53C400
-	bool "Enable NCR53c400 extensions"
-	depends on SCSI_GENERIC_NCR5380
-	help
-	  This enables certain optimizations for the NCR53c400 SCSI cards.
-	  You might as well try it out.  Note that this driver will only probe
-	  for the Trantor T130B in its default configuration; you might have
-	  to pass a command line option to the kernel at boot time if it does
-	  not detect your card.  See the file
-	  <file:Documentation/scsi/g_NCR5380.txt> for details.
-
-config SCSI_IBMMCA
-	tristate "IBMMCA SCSI support"
-	depends on MCA && SCSI
-	---help---
-	  This is support for the IBM SCSI adapter found in many of the PS/2
-	  series computers.  These machines have an MCA bus, so you need to
-	  answer Y to "MCA support" as well and read
-	  <file:Documentation/mca.txt>.
-
-	  If the adapter isn't found during boot (a common problem for models
-	  56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
-	  option, where <pun> is the id of the SCSI subsystem (usually 7, but
-	  if that doesn't work check your reference diskette).  Owners of
-	  model 95 with a LED-matrix-display can in addition activate some
-	  activity info like under OS/2, but more informative, by setting
-	  'ibmmcascsi=display' as an additional kernel parameter.  Try "man
-	  bootparam" or see the documentation of your boot loader about how to
-	  pass options to the kernel.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ibmmca.
-
-config IBMMCA_SCSI_ORDER_STANDARD
-	bool "Standard SCSI-order"
-	depends on SCSI_IBMMCA
-	---help---
-	  In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
-	  are assigned to the drive letters, starting with the lowest SCSI-id
-	  (physical number -- pun) to be drive C:, as seen from DOS and
-	  similar operating systems. When looking into papers describing the
-	  ANSI-SCSI-standard, this assignment of drives appears to be wrong.
-	  The SCSI-standard follows a hardware-hierarchy which says that id 7
-	  has the highest priority and id 0 the lowest. Therefore, the host
-	  adapters are still today everywhere placed as SCSI-id 7 by default.
-	  In the SCSI-standard, the drive letters express the priority of the
-	  disk. C: should be the hard disk, or a partition on it, with the
-	  highest priority. This must therefore be the disk with the highest
-	  SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
-	  original definition of the SCSI-standard as also industrial- and
-	  process-control-machines, like VME-CPUs running under realtime-OSes
-	  (e.g. LynxOS, OS9) do.
-
-	  If you like to run Linux on your MCA-machine with the same
-	  assignment of hard disks as seen from e.g. DOS or OS/2 on your
-	  machine, which is in addition conformant to the SCSI-standard, you
-	  must say Y here. This is also necessary for MCA-Linux users who want
-	  to keep downward compatibility to older releases of the
-	  IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
-	  June 1997).
-
-	  If you like to have the lowest SCSI-id assigned as drive C:, as
-	  modern SCSI-BIOSes do, which does not conform to the standard, but
-	  is widespread and common in the PC-world of today, you must say N
-	  here. If unsure, say Y.
-
-config IBMMCA_SCSI_DEV_RESET
-	bool "Reset SCSI-devices at boottime"
-	depends on SCSI_IBMMCA
-	---help---
-	  By default, SCSI-devices are reset when the machine is powered on.
-	  However, some devices exist, like special-control-devices,
-	  SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
-	  not reset when switched on. If you say Y here, each device connected
-	  to your SCSI-bus will be issued a reset-command after it has been
-	  probed, while the kernel is booting. This may cause problems with
-	  more modern devices, like hard disks, which do not appreciate these
-	  reset commands, and can cause your system to hang. So say Y only if
-	  you know that one of your older devices needs it; N is the safe
-	  answer.
-
-config SCSI_IPS
-	tristate "IBM ServeRAID support"
-	depends on PCI && SCSI
-	---help---
-	  This is support for the IBM ServeRAID hardware RAID controllers.
-	  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
-	  for more information.  If this driver does not work correctly
-	  without modification please contact the author by email at
-	  <ipslinux@adaptec.com>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ips.
-
-config SCSI_IBMVSCSI
-	tristate "IBM Virtual SCSI support"
-	depends on PPC_PSERIES || PPC_ISERIES
-	help
-	  This is the IBM POWER Virtual SCSI Client
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ibmvscsic.
-
-config SCSI_IBMVSCSIS
-	tristate "IBM Virtual SCSI Server support"
-	depends on PPC_PSERIES && SCSI_TGT && SCSI_SRP
-	help
-	  This is the SRP target driver for IBM pSeries virtual environments.
-
-	  The userspace component needed to initialize the driver and
-	  documentation can be found:
-
-	  http://stgt.berlios.de/
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ibmvstgt.
-
-config SCSI_INITIO
-	tristate "Initio 9100U(W) support"
-	depends on PCI && SCSI
-	help
-	  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
-	  read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called initio.
-
-config SCSI_INIA100
-	tristate "Initio INI-A100U2W support"
-	depends on PCI && SCSI
-	help
-	  This is support for the Initio INI-A100U2W SCSI host adapter.
-	  Please read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called a100u2w.
-
-config SCSI_PPA
-	tristate "IOMEGA parallel port (ppa - older drives)"
-	depends on SCSI && PARPORT_PC
-	---help---
-	  This driver supports older versions of IOMEGA's parallel port ZIP
-	  drive (a 100 MB removable media device).
-
-	  Note that you can say N here if you have the SCSI version of the ZIP
-	  drive: it will be supported automatically if you said Y to the
-	  generic "SCSI disk support", above.
-
-	  If you have the ZIP Plus drive or a more recent parallel port ZIP
-	  drive (if the supplied cable with the drive is labeled "AutoDetect")
-	  then you should say N here and Y to "IOMEGA parallel port (imm -
-	  newer drives)", below.
-
-	  For more information about this driver and how to use it you should
-	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
-	  the SCSI-HOWTO, which is available from
-	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
-	  you will still be able to use the parallel port for other tasks,
-	  such as a printer; it is safe to compile both drivers into the
-	  kernel.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ppa.
-
-config SCSI_IMM
-	tristate "IOMEGA parallel port (imm - newer drives)"
-	depends on SCSI && PARPORT_PC
-	---help---
-	  This driver supports newer versions of IOMEGA's parallel port ZIP
-	  drive (a 100 MB removable media device).
-
-	  Note that you can say N here if you have the SCSI version of the ZIP
-	  drive: it will be supported automatically if you said Y to the
-	  generic "SCSI disk support", above.
-
-	  If you have the ZIP Plus drive or a more recent parallel port ZIP
-	  drive (if the supplied cable with the drive is labeled "AutoDetect")
-	  then you should say Y here; if you have an older ZIP drive, say N
-	  here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
-
-	  For more information about this driver and how to use it you should
-	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
-	  the SCSI-HOWTO, which is available from
-	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
-	  you will still be able to use the parallel port for other tasks,
-	  such as a printer; it is safe to compile both drivers into the
-	  kernel.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called imm.
-
-config SCSI_IZIP_EPP16
-	bool "ppa/imm option - Use slow (but safe) EPP-16"
-	depends on SCSI_PPA || SCSI_IMM
-	---help---
-	  EPP (Enhanced Parallel Port) is a standard for parallel ports which
-	  allows them to act as expansion buses that can handle up to 64
-	  peripheral devices.
-
-	  Some parallel port chipsets are slower than their motherboard, and
-	  so we have to control the state of the chipset's FIFO queue every
-	  now and then to avoid data loss. This will be done if you say Y
-	  here.
-
-	  Generally, saying Y is the safe option and slows things down a bit.
-
-config SCSI_IZIP_SLOW_CTR
-	bool "ppa/imm option - Assume slow parport control register"
-	depends on SCSI_PPA || SCSI_IMM
-	help
-	  Some parallel ports are known to have excessive delays between
-	  changing the parallel port control register and good data being
-	  available on the parallel port data/status register. This option
-	  forces a small delay (1.0 usec to be exact) after changing the
-	  control register to let things settle out. Enabling this option may
-	  result in a big drop in performance but some very old parallel ports
-	  (found in 386 vintage machines) will not work properly.
-
-	  Generally, saying N is fine.
-
-config SCSI_NCR53C406A
-	tristate "NCR53c406a SCSI support"
-	depends on ISA && SCSI
-	help
-	  This is support for the NCR53c406a SCSI host adapter.  For user
-	  configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
-	  in the kernel source.  Also read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called NCR53c406.
-
-config SCSI_NCR_D700
-	tristate "NCR Dual 700 MCA SCSI support"
-	depends on MCA && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is a driver for the MicroChannel Dual 700 card produced by
-	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
-	  tries to negotiate sync and uses tag command queueing.
-
-	  Unless you have an NCR manufactured machine, the chances are that
-	  you do not have this SCSI card, so say N.
-
-config SCSI_LASI700
-	tristate "HP Lasi SCSI support for 53c700/710"
-	depends on GSC && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is a driver for the SCSI controller in the Lasi chip found in
-	  many PA-RISC workstations & servers.  If you do not know whether you
-	  have a Lasi chip, it is safe to say "Y" here.
-
-config SCSI_SNI_53C710
-	tristate "SNI RM SCSI support for 53c710"
-	depends on SNI_RM && SCSI
-	select SCSI_SPI_ATTRS
-	select 53C700_LE_ON_BE
-	help
-	  This is a driver for the onboard SCSI controller found in older
-	  SNI RM workstations & servers.
-
-config 53C700_LE_ON_BE
-	bool
-	depends on SCSI_LASI700
-	default y
-
-config SCSI_STEX
-	tristate "Promise SuperTrak EX Series support"
-	depends on PCI && SCSI
-	---help---
-	  This driver supports Promise SuperTrak EX series storage controllers.
-
-	  Promise provides Linux RAID configuration utility for these
-	  controllers. Please visit <http://www.promise.com> to download.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called stex.
-
-config 53C700_BE_BUS
-	bool
-	depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
-	default y
-
-config SCSI_SYM53C8XX_2
-	tristate "SYM53C8XX Version 2 SCSI support"
-	depends on PCI && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This driver supports the whole NCR53C8XX/SYM53C8XX family of
-	  PCI-SCSI controllers.  It also supports the subset of LSI53C10XX
-	  Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
-	  language.  It does not support LSI53C10XX Ultra-320 PCI-X SCSI
-	  controllers; you need to use the Fusion MPT driver for that.
-
-	  Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
-	  information.
-
-config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
-	int "DMA addressing mode"
-	depends on SCSI_SYM53C8XX_2
-	default "1"
-	---help---
-	  This option only applies to PCI-SCSI chips that are PCI DAC
-	  capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
-
-	  When set to 0, the driver will program the chip to only perform
-	  32-bit DMA.  When set to 1, the chip will be able to perform DMA
-	  to addresses up to 1TB.  When set to 2, the driver supports the
-	  full 64-bit DMA address range, but can only address 16 segments
-	  of 4 GB each.  This limits the total addressable range to 64 GB.
-
-	  Most machines with less than 4GB of memory should use a setting
-	  of 0 for best performance.  If your machine has 4GB of memory
-	  or more, you should set this option to 1 (the default).
-
-	  The still experimental value 2 (64 bit DMA addressing with 16
-	  x 4GB segments limitation) can be used on systems that require
-	  PCI address bits past bit 39 to be set for the addressing of
-	  memory using PCI DAC cycles.
-
-config SCSI_SYM53C8XX_DEFAULT_TAGS
-	int "Default tagged command queue depth"
-	depends on SCSI_SYM53C8XX_2
-	default "16"
-	help
-	  This is the default value of the command queue depth the
-	  driver will announce to the generic SCSI layer for devices
-	  that support tagged command queueing. This value can be changed
-	  from the boot command line.  This is a soft limit that cannot
-	  exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
-
-config SCSI_SYM53C8XX_MAX_TAGS
-	int "Maximum number of queued commands"
-	depends on SCSI_SYM53C8XX_2
-	default "64"
-	help
-	  This option allows you to specify the maximum number of commands
-	  that can be queued to any device, when tagged command queuing is
-	  possible. The driver supports up to 256 queued commands per device.
-	  This value is used as a compiled-in hard limit.
-
-config SCSI_SYM53C8XX_MMIO
-	bool "Use memory mapped IO"
-	depends on SCSI_SYM53C8XX_2
-	default y
-	help
-	  Memory mapped IO is faster than Port IO.  Most people should
-	  answer Y here, but some machines may have problems.  If you have
-	  to answer N here, please report the problem to the maintainer.
-
-config SCSI_IPR
-	tristate "IBM Power Linux RAID adapter support"
-	depends on PCI && SCSI && ATA
-	select FW_LOADER
-	---help---
-	  This driver supports the IBM Power Linux family RAID adapters.
-	  This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
-	  as IBM iSeries 5702, 5703, 5709, and 570A.
-
-config SCSI_IPR_TRACE
-	bool "enable driver internal trace"
-	depends on SCSI_IPR
-	default y
-	help
-	  If you say Y here, the driver will trace all commands issued
-	  to the adapter. Performance impact is minimal. Trace can be
-	  dumped using /sys/bus/class/scsi_host/hostXX/trace.
-
-config SCSI_IPR_DUMP
-	bool "enable adapter dump support"
-	depends on SCSI_IPR
-	default y
-	help
-	  If you say Y here, the driver will support adapter crash dump.
-	  If you enable this support, the iprdump daemon can be used
-	  to capture adapter failure analysis information.
-
-config SCSI_ZALON
-	tristate "Zalon SCSI support"
-	depends on GSC && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  The Zalon is a GSC/HSC bus interface chip that sits between the
-	  PA-RISC processor and the NCR 53c720 SCSI controller on C100,
-	  C110, J200, J210 and some D, K & R-class machines.  It's also
-	  used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
-	  Say Y here if you have one of these machines or cards.
-
-config SCSI_NCR_Q720
-	tristate "NCR Quad 720 MCA SCSI support"
-	depends on MCA && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is a driver for the MicroChannel Quad 720 card produced by
-	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
-	  tries to negotiate sync and uses tag command queueing.
-
-	  Unless you have an NCR manufactured machine, the chances are that
-	  you do not have this SCSI card, so say N.
-
-config SCSI_NCR53C8XX_DEFAULT_TAGS
-	int "default tagged command queue depth"
-	depends on SCSI_ZALON || SCSI_NCR_Q720
-	default "8"
-	---help---
-	  "Tagged command queuing" is a feature of SCSI-2 which improves
-	  performance: the host adapter can send several SCSI commands to a
-	  device's queue even if previous commands haven't finished yet.
-	  Because the device is intelligent, it can optimize its operations
-	  (like head positioning) based on its own request queue. Some SCSI
-	  devices don't implement this properly; if you want to disable this
-	  feature, enter 0 or 1 here (it doesn't matter which).
-
-	  The default value is 8 and should be supported by most hard disks.
-	  This value can be overridden from the boot command line using the
-	  'tags' option as follows (example):
-	  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
-	  4, set queue depth to 16 for target 2 and target 3 on controller 0
-	  and set queue depth to 10 for target 0 / lun 2 on controller 1.
-
-	  The normal answer therefore is to go with the default 8 and to use
-	  a boot command line option for devices that need to use a different
-	  command queue depth.
-
-	  There is no safe option other than using good SCSI devices.
-
-config SCSI_NCR53C8XX_MAX_TAGS
-	int "maximum number of queued commands"
-	depends on SCSI_ZALON || SCSI_NCR_Q720
-	default "32"
-	---help---
-	  This option allows you to specify the maximum number of commands
-	  that can be queued to any device, when tagged command queuing is
-	  possible. The default value is 32. Minimum is 2, maximum is 64.
-	  Modern hard disks are able to support 64 tags and even more, but
-	  do not seem to be faster when more than 32 tags are being used.
-
-	  So, the normal answer here is to go with the default value 32 unless
-	  you are using very large hard disks with large cache (>= 1 MB) that
-	  are able to take advantage of more than 32 tagged commands.
-
-	  There is no safe option and the default answer is recommended.
-
-config SCSI_NCR53C8XX_SYNC
-	int "synchronous transfers frequency in MHz"
-	depends on SCSI_ZALON || SCSI_NCR_Q720
-	default "20"
-	---help---
-	  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
-	  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
-	  are respectively the maximum data transfer rates in mega-transfers
-	  per second for each class.  For example, a FAST-20 Wide 16 device is
-	  able to transfer data at 20 million 16 bit packets per second for a
-	  total rate of 40 MB/s.
-
-	  You may specify 0 if you want to only use asynchronous data
-	  transfers. This is the safest and slowest option. Otherwise, specify
-	  a value between 5 and 80, depending on the capability of your SCSI
-	  controller.  The higher the number, the faster the data transfer.
-	  Note that 80 should normally be ok since the driver decreases the
-	  value automatically according to the controller's capabilities.
-
-	  Your answer to this question is ignored for controllers with NVRAM,
-	  since the driver will get this information from the user set-up.  It
-	  also can be overridden using a boot setup option, as follows
-	  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
-	  for FAST-20 synchronous data transfer (20 mega-transfers per
-	  second).
-
-	  The normal answer therefore is not to go with the default but to
-	  select the maximum value 80 allowing the driver to use the maximum
-	  value supported by each controller. If this causes problems with
-	  your SCSI devices, you should come back and decrease the value.
-
-	  There is no safe option other than using good cabling, right
-	  terminations and SCSI conformant devices.
-
-config SCSI_NCR53C8XX_NO_DISCONNECT
-	bool "not allow targets to disconnect"
-	depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
-	help
-	  This option is only provided for safety if you suspect some SCSI
-	  device of yours to not support properly the target-disconnect
-	  feature. In that case, you would say Y here. In general however, to
-	  not allow targets to disconnect is not reasonable if there is more
-	  than 1 device on a SCSI bus. The normal answer therefore is N.
-
-config SCSI_MCA_53C9X
-	tristate "NCR MCA 53C9x SCSI support"
-	depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
-	help
-	  Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
-	  controller based on the NCR 53C94.  This driver will allow use of
-	  the controller on the 3550, and very possibly others.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mca_53c9x.
-
-config SCSI_PAS16
-	tristate "PAS16 SCSI support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This is support for a SCSI host adapter.  It is explained in section
-	  3.10 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/pas16.h>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called pas16.
-
-config SCSI_PSI240I
-	tristate "PSI240i support"
-	depends on ISA && SCSI
-	help
-	  This is support for the PSI240i EIDE interface card which acts as a
-	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called psi240i.
-
-config SCSI_QLOGIC_FAS
-	tristate "Qlogic FAS SCSI support"
-	depends on ISA && SCSI
-	---help---
-	  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
-	  FastSCSI! cards as well as any other card based on the FASXX chip
-	  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
-
-	  This driver does NOT support the PCI versions of these cards. The
-	  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
-	  SCSI support"), below.
-
-	  Information about this driver is contained in
-	  <file:Documentation/scsi/qlogicfas.txt>.  You should also read the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called qlogicfas.
-
-config SCSI_QLOGIC_FC_FIRMWARE
-	bool "Include loadable firmware in driver"
-	depends on SCSI_QLOGIC_FC
-  	help
-	  Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
-	  expanded LUN addressing and FcTape (FCP-2) support, in the
-	  qlogicfc driver. This is required on some platforms.
-
-config SCSI_QLOGIC_1280
-	tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
-	depends on PCI && SCSI
-	help
-	  Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called qla1280.
-
-config SCSI_QLOGICPTI
-	tristate "PTI Qlogic, ISP Driver"
-	depends on SBUS && SCSI
-	help
-	  This driver supports SBUS SCSI controllers from PTI or QLogic. These
-	  controllers are known under Solaris as qpti and in the openprom as
-	  PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
-	  driven by a different driver.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called qlogicpti.
-
-source "drivers/scsi/qla2xxx/Kconfig"
-source "drivers/scsi/qla4xxx/Kconfig"
-
-config SCSI_LPFC
-	tristate "Emulex LightPulse Fibre Channel Support"
-	depends on PCI && SCSI
-	select SCSI_FC_ATTRS
-	help
-          This lpfc driver supports the Emulex LightPulse
-          Family of Fibre Channel PCI host adapters.
-
-config SCSI_SEAGATE
-	tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
-	depends on X86 && ISA && SCSI
-	select CHECK_SIGNATURE
-	---help---
-	  These are 8-bit SCSI controllers; the ST-01 is also supported by
-	  this driver.  It is explained in section 3.9 of the SCSI-HOWTO,
-	  available from <http://www.tldp.org/docs.html#howto>.  If it
-	  doesn't work out of the box, you may have to change some macros at
-	  compiletime, which are described in <file:drivers/scsi/seagate.c>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called seagate.
-
-# definitely looks not 64bit safe:
-config SCSI_SIM710
-	tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
-	depends on (EISA || MCA) && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  This driver for NCR53c710 based SCSI host adapters.
-
-	  It currently supports Compaq EISA cards and NCR MCA cards
-
-config SCSI_SYM53C416
-	tristate "Symbios 53c416 SCSI support"
-	depends on ISA && SCSI
-	---help---
-	  This is support for the sym53c416 SCSI host adapter, the SCSI
-	  adapter that comes with some HP scanners. This driver requires that
-	  the sym53c416 is configured first using some sort of PnP
-	  configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
-	  are using isapnp then you need to compile this driver as a module
-	  and then load it using insmod after isapnp has run. The parameters
-	  of the configured card(s) should be passed to the driver. The format
-	  is:
-
-	  insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called sym53c416.
-
-config SCSI_DC395x
-	tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
-	depends on PCI && SCSI && EXPERIMENTAL
-	---help---
-	  This driver supports PCI SCSI host adapters based on the ASIC
-	  TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
-
-	  This driver works, but is still in experimental status. So better
-	  have a bootable disk and a backup in case of emergency.
-
-	  Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called dc395x.
-
-config SCSI_DC390T
-	tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
-	depends on PCI && SCSI
-	---help---
-	  This driver supports PCI SCSI host adapters based on the Am53C974A
-	  chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
-	  PCscsi/PCnet (Am53/79C974) solutions.
-
-	  Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
-
-	  Note that this driver does NOT support Tekram DC390W/U/F, which are
-	  based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called tmscsim.
-
-config SCSI_T128
-	tristate "Trantor T128/T128F/T228 SCSI support"
-	depends on ISA && SCSI
-	select SCSI_SPI_ATTRS
-	select CHECK_SIGNATURE
-	---help---
-	  This is support for a SCSI host adapter. It is explained in section
-	  3.11 of the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
-	  Adaptec, and some former Trantor products are being sold under the
-	  Adaptec name.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called t128.
-
-config SCSI_U14_34F
-	tristate "UltraStor 14F/34F support"
-	depends on ISA && SCSI && ISA_DMA_API
-	---help---
-	  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
-	  The source at <file:drivers/scsi/u14-34f.c> contains some
-	  information about this hardware.  If the driver doesn't work out of
-	  the box, you may have to change some settings in
-	  <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  Note that there is also
-	  another driver for the same hardware: "UltraStor SCSI support",
-	  below.  You should say Y to both only if you want 24F support as
-	  well.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called u14-34f.
-
-config SCSI_U14_34F_TAGGED_QUEUE
-	bool "enable tagged command queueing"
-	depends on SCSI_U14_34F
-	help
-	  This is a feature of SCSI-2 which improves performance: the host
-	  adapter can send several SCSI commands to a device's queue even if
-	  previous commands haven't finished yet.
-	  This is equivalent to the "u14-34f=tc:y" boot option.
-
-config SCSI_U14_34F_LINKED_COMMANDS
-	bool "enable elevator sorting"
-	depends on SCSI_U14_34F
-	help
-	  This option enables elevator sorting for all probed SCSI disks and
-	  CD-ROMs. It definitely reduces the average seek distance when doing
-	  random seeks, but this does not necessarily result in a noticeable
-	  performance improvement: your mileage may vary...
-	  This is equivalent to the "u14-34f=lc:y" boot option.
-
-config SCSI_U14_34F_MAX_TAGS
-	int "maximum number of queued commands"
-	depends on SCSI_U14_34F
-	default "8"
-	help
-	  This specifies how many SCSI commands can be maximally queued for
-	  each probed SCSI device. You should reduce the default value of 8
-	  only if you have disks with buggy or limited tagged command support.
-	  Minimum is 2 and maximum is 14. This value is also the window size
-	  used by the elevator sorting option above. The effective value used
-	  by the driver for each probed SCSI device is reported at boot time.
-	  This is equivalent to the "u14-34f=mq:8" boot option.
-
-config SCSI_ULTRASTOR
-	tristate "UltraStor SCSI support"
-	depends on X86 && ISA && SCSI
-	---help---
-	  This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
-	  adapter family.  This driver is explained in section 3.12 of the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
-	  of the box, you may have to change some settings in
-	  <file:drivers/scsi/ultrastor.h>.
-
-	  Note that there is also another driver for the same hardware:
-	  "UltraStor 14F/34F support", above.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ultrastor.
-
-config SCSI_NSP32
-	tristate "Workbit NinjaSCSI-32Bi/UDE support"
-	depends on PCI && SCSI && !64BIT
-	help
-	  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
-	  SCSI host adapter. Please read the SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called nsp32.
-
-config SCSI_DEBUG
-	tristate "SCSI debugging host simulator"
-	depends on SCSI
-	help
-	  This is a host adapter simulator that can simulate multiple hosts
-	  each with multiple dummy SCSI devices (disks). It defaults to one
-	  host adapter with one dummy SCSI disk. Each dummy disk uses kernel
-	  RAM as storage (i.e. it is a ramdisk). To save space when multiple
-	  dummy disks are simulated, they share the same kernel RAM for 
-	  their storage. See <http://www.torque.net/sg/sdebug.html> for more
-	  information. This driver is primarily of use to those testing the
-	  SCSI and block subsystems. If unsure, say N.
-
-config SCSI_MESH
-	tristate "MESH (Power Mac internal SCSI) support"
-	depends on PPC32 && PPC_PMAC && SCSI
-	help
-	  Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
-	  SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
-	  other Power Macintoshes do). Say Y to include support for this SCSI
-	  adaptor.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mesh.
-
-config SCSI_MESH_SYNC_RATE
-	int "maximum synchronous transfer rate (MB/s) (0 = async)"
-	depends on SCSI_MESH
-	default "5"
-	help
-	  On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
-	  drives a bus which is entirely internal to the machine (such as the
-	  7500, 7600, 8500, etc.), the MESH is capable of synchronous
-	  operation at up to 10 MB/s. On machines where the SCSI bus
-	  controlled by the MESH can have external devices connected, it is
-	  usually rated at 5 MB/s. 5 is a safe value here unless you know the
-	  MESH SCSI bus is internal only; in that case you can say 10. Say 0
-	  to disable synchronous operation.
-
-config SCSI_MESH_RESET_DELAY_MS
-	int "initial bus reset delay (ms) (0 = no reset)"
-	depends on SCSI_MESH
-	default "4000"
-
-config SCSI_MAC53C94
-	tristate "53C94 (Power Mac external SCSI) support"
-	depends on PPC32 && PPC_PMAC && SCSI
-	help
-	  On Power Macintoshes (and clones) with two SCSI buses, the external
-	  SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
-	  machines which only have one SCSI bus, such as the 7200, also use
-	  the 53C94. Say Y to include support for the 53C94.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mac53c94.
-
-source "drivers/scsi/arm/Kconfig"
-
-config JAZZ_ESP
-	bool "MIPS JAZZ FAS216 SCSI support"
-	depends on MACH_JAZZ && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is the driver for the onboard SCSI host adapter of MIPS Magnum
-	  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
-	  systems.
-
-config A3000_SCSI
-	tristate "A3000 WD33C93A support"
-	depends on AMIGA && SCSI
-	help
-	  If you have an Amiga 3000 and have SCSI devices connected to the
-	  built-in SCSI controller, say Y. Otherwise, say N.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called a3000.
-
-config A2091_SCSI
-	tristate "A2091/A590 WD33C93A support"
-	depends on ZORRO && SCSI
-	help
-	  If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
-	  say N.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called a2091.
-
-config GVP11_SCSI
-	tristate "GVP Series II WD33C93A support"
-	depends on ZORRO && SCSI
-	---help---
-	  If you have a Great Valley Products Series II SCSI controller,
-	  answer Y. Also say Y if you have a later model of GVP SCSI
-	  controller (such as the GVP A4008 or a Combo board). Otherwise,
-	  answer N. This driver does NOT work for the T-Rex series of
-	  accelerators from TekMagic and GVP-M.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called gvp11.
-
-config CYBERSTORM_SCSI
-	tristate "CyberStorm SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have an Amiga with an original (MkI) Phase5 Cyberstorm
-	  accelerator board and the optional Cyberstorm SCSI controller,
-	  answer Y. Otherwise, say N.
-
-config CYBERSTORMII_SCSI
-	tristate "CyberStorm Mk II SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
-	  and the optional Cyberstorm SCSI controller, say Y. Otherwise,
-	  answer N.
-
-config BLZ2060_SCSI
-	tristate "Blizzard 2060 SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
-	  and want to use the onboard SCSI controller, say Y. Otherwise,
-	  answer N.
-
-config BLZ1230_SCSI
-	tristate "Blizzard 1230IV/1260 SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
-	  1260 accelerator, and the optional SCSI module, say Y. Otherwise,
-	  say N.
-
-config FASTLANE_SCSI
-	tristate "Fastlane SCSI support"
-	depends on ZORRO && SCSI
-	help
-	  If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
-	  one in the near future, say Y to this question. Otherwise, say N.
-
-config SCSI_A4000T
-	tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
-	depends on AMIGA && SCSI && EXPERIMENTAL
-	select SCSI_SPI_ATTRS
-	help
-	  If you have an Amiga 4000T and have SCSI devices connected to the
-	  built-in SCSI controller, say Y. Otherwise, say N.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called a4000t.
-
-config SCSI_ZORRO7XX
-	tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
-	depends on ZORRO && SCSI && EXPERIMENTAL
-	select SCSI_SPI_ATTRS
-	help
-	  Support for various NCR53c710-based SCSI controllers on Zorro
-	  expansion boards for the Amiga.
-	  This includes:
-	    - the Amiga 4091 Zorro III SCSI-2 controller,
-	    - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
-	      (info at
-	      <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
-	    - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
-	      accelerator card for the Amiga 1200,
-	    - the SCSI controller on the GVP Turbo 040/060 accelerator.
-
-config OKTAGON_SCSI
-	tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
-	depends on ZORRO && SCSI && EXPERIMENTAL
-	help
-	  If you have the BSC Oktagon SCSI disk controller for the Amiga, say
-	  Y to this question.  If you're in doubt about whether you have one,
-	  see the picture at
-	  <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
-
-config ATARI_SCSI
-	tristate "Atari native SCSI support"
-	depends on ATARI && SCSI
-	select SCSI_SPI_ATTRS
-	---help---
-	  If you have an Atari with built-in NCR5380 SCSI controller (TT,
-	  Falcon, ...) say Y to get it supported. Of course also, if you have
-	  a compatible SCSI controller (e.g. for Medusa).
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called atari_scsi.
-
-	  This driver supports both styles of NCR integration into the
-	  system: the TT style (separate DMA), and the Falcon style (via
-	  ST-DMA, replacing ACSI).  It does NOT support other schemes, like
-	  in the Hades (without DMA).
-
-config ATARI_SCSI_TOSHIBA_DELAY
-	bool "Long delays for Toshiba CD-ROMs"
-	depends on ATARI_SCSI
-	help
-	  This option increases the delay after a SCSI arbitration to
-	  accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
-	  use a Toshiba CD-ROM drive; otherwise, the option is not needed and
-	  would impact performance a bit, so say N.
-
-config ATARI_SCSI_RESET_BOOT
-	bool "Reset SCSI-devices at boottime"
-	depends on ATARI_SCSI
-	help
-	  Reset the devices on your Atari whenever it boots.  This makes the
-	  boot process fractionally longer but may assist recovery from errors
-	  that leave the devices with SCSI operations partway completed.
-
-config TT_DMA_EMUL
-	bool "Hades SCSI DMA emulator"
-	depends on ATARI_SCSI && HADES
-	help
-	  This option enables code which emulates the TT SCSI DMA chip on the
-	  Hades. This increases the SCSI transfer rates at least ten times
-	  compared to PIO transfers.
-
-config MAC_SCSI
-	bool "Macintosh NCR5380 SCSI"
-	depends on MAC && SCSI=y
-	select SCSI_SPI_ATTRS
-	help
-	  This is the NCR 5380 SCSI controller included on most of the 68030
-	  based Macintoshes.  If you have one of these say Y and read the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-config SCSI_MAC_ESP
-	tristate "Macintosh NCR53c9[46] SCSI"
-	depends on MAC && SCSI
-	help
-	  This is the NCR 53c9x SCSI controller found on most of the 68040
-	  based Macintoshes.  If you have one of these say Y and read the
-	  SCSI-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mac_esp.
-
-config MVME147_SCSI
-	bool "WD33C93 SCSI driver for MVME147"
-	depends on MVME147 && SCSI=y
-	select SCSI_SPI_ATTRS
-	help
-	  Support for the on-board SCSI controller on the Motorola MVME147
-	  single-board computer.
-
-config MVME16x_SCSI
-	tristate "NCR53C710 SCSI driver for MVME16x"
-	depends on MVME16x && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
-	  SCSI controller chip.  Almost everyone using one of these boards
-	  will want to say Y to this question.
-
-config BVME6000_SCSI
-	tristate "NCR53C710 SCSI driver for BVME6000"
-	depends on BVME6000 && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
-	  SCSI controller chip.  Almost everyone using one of these boards
-	  will want to say Y to this question.
-
-config SUN3_SCSI
-	tristate "Sun3 NCR5380 SCSI"
-	depends on SUN3 && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This option will enable support for the OBIO (onboard io) NCR5380
-	  SCSI controller found in the Sun 3/50 and 3/60, as well as for
-	  "Sun3" type VME scsi controllers also based on the NCR5380.
-	  General Linux information on the Sun 3 series (now discontinued)
-	  is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
-
-config SUN3X_ESP
-	bool "Sun3x ESP SCSI"
-	depends on SUN3X && SCSI=y
-	help
-	  The ESP was an on-board SCSI controller used on Sun 3/80
-	  machines.  Say Y here to compile in support for it.
-
-config SCSI_SUNESP
-	tristate "Sparc ESP Scsi Driver"
-	depends on SBUS && SCSI
-	select SCSI_SPI_ATTRS
-	help
-	  This is the driver for the Sun ESP SCSI host adapter. The ESP
-	  chipset is present in most SPARC SBUS-based computers.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called esp.
-
-config ZFCP
-	tristate "FCP host bus adapter driver for IBM eServer zSeries"
-	depends on S390 && QDIO && SCSI
-	select SCSI_FC_ATTRS
-	help
-          If you want to access SCSI devices attached to your IBM eServer
-          zSeries by means of Fibre Channel interfaces say Y.
-          For details please refer to the documentation provided by IBM at
-          <http://oss.software.ibm.com/developerworks/opensource/linux390>
-
-          This driver is also available as a module. This module will be
-          called zfcp. If you want to compile it as a module, say M here
-          and read <file:Documentation/kbuild/modules.txt>.
-
-config SCSI_SRP
-	tristate "SCSI RDMA Protocol helper library"
-	depends on SCSI && PCI
-	select SCSI_TGT
-	help
-	  If you wish to use SRP target drivers, say Y.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called libsrp.
-
-endif # SCSI_LOWLEVEL
-
-source "drivers/scsi/pcmcia/Kconfig"
-
-endmenu
+endmenu # Storage (core and SCSI commands)
Index: linux-2.6.23-rc6/drivers/scsi/Kconfig.lowlevel
===================================================================
--- /dev/null
+++ linux-2.6.23-rc6/drivers/scsi/Kconfig.lowlevel
@@ -0,0 +1,1578 @@
+menu "SCSI device support"
+
+config RAID_ATTRS
+	tristate "RAID Transport Class"
+	default n
+	depends on BLOCK
+	---help---
+	  Provides RAID
+
+config SCSI_TGT
+	tristate "SCSI target support"
+	depends on SCSI && EXPERIMENTAL
+	---help---
+	  If you want to use SCSI target mode drivers enable this option.
+	  If you choose M, the module will be called scsi_tgt.
+
+menu "SCSI Transports"
+	depends on SCSI
+
+config SCSI_SPI_ATTRS
+	tristate "Parallel SCSI (SPI) Transport Attributes"
+	depends on SCSI
+	help
+	  If you wish to export transport-specific information about
+	  each attached SCSI device to sysfs, say Y.  Otherwise, say N.
+
+config SCSI_FC_ATTRS
+	tristate "FiberChannel Transport Attributes"
+	depends on SCSI
+	select SCSI_NETLINK
+	help
+	  If you wish to export transport-specific information about
+	  each attached FiberChannel device to sysfs, say Y.
+	  Otherwise, say N.
+
+config SCSI_ISCSI_ATTRS
+	tristate "iSCSI Transport Attributes"
+	depends on SCSI && NET
+	help
+	  If you wish to export transport-specific information about
+	  each attached iSCSI device to sysfs, say Y.
+	  Otherwise, say N.
+
+config SCSI_SAS_ATTRS
+	tristate "SAS Transport Attributes"
+	depends on SCSI && BLK_DEV_BSG
+	help
+	  If you wish to export transport-specific information about
+	  each attached SAS device to sysfs, say Y.
+
+source "drivers/scsi/libsas/Kconfig"
+
+endmenu
+
+menuconfig SCSI_LOWLEVEL
+	bool "SCSI low-level drivers"
+	depends on SCSI!=n
+	default y
+
+if SCSI_LOWLEVEL
+
+config ISCSI_TCP
+	tristate "iSCSI Initiator over TCP/IP"
+	depends on SCSI && INET
+	select CRYPTO
+	select CRYPTO_MD5
+	select CRYPTO_CRC32C
+	select SCSI_ISCSI_ATTRS
+	help
+	 The iSCSI Driver provides a host with the ability to access storage
+	 through an IP network. The driver uses the iSCSI protocol to transport
+	 SCSI requests and responses over a TCP/IP network between the host
+	 (the "initiator") and "targets".  Architecturally, the iSCSI driver
+	 combines with the host's TCP/IP stack, network drivers, and Network
+	 Interface Card (NIC) to provide the same functions as a SCSI or a
+	 Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
+
+	 To compile this driver as a module, choose M here: the
+	 module will be called iscsi_tcp.
+
+	 The userspace component needed to initialize the driver, documentation,
+	 and sample configuration files can be found here:
+
+	 http://linux-iscsi.sf.net
+
+config SGIWD93_SCSI
+	tristate "SGI WD93C93 SCSI Driver"
+	depends on SGI_IP22 && SCSI
+  	help
+	  If you have a Western Digital WD93 SCSI controller on
+	  an SGI MIPS system, say Y.  Otherwise, say N.
+
+config SCSI_DECNCR
+	tristate "DEC NCR53C94 Scsi Driver"
+	depends on MACH_DECSTATION && SCSI && TC
+	help
+	  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
+	  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
+
+config SCSI_DECSII
+	tristate "DEC SII Scsi Driver"
+	depends on MACH_DECSTATION && SCSI && 32BIT
+
+config BLK_DEV_3W_XXXX_RAID
+	tristate "3ware 5/6/7/8xxx ATA-RAID support"
+	depends on PCI && SCSI
+	help
+	  3ware is the only hardware ATA-Raid product in Linux to date.
+	  This card is 2,4, or 8 channel master mode support only.
+	  SCSI support required!!!
+
+	  <http://www.3ware.com/>
+
+	  Please read the comments at the top of
+	  <file:drivers/scsi/3w-xxxx.c>.
+
+config SCSI_3W_9XXX
+	tristate "3ware 9xxx SATA-RAID support"
+	depends on PCI && SCSI
+	help
+	  This driver supports the 9000 series 3ware SATA-RAID cards.
+
+	  <http://www.amcc.com>
+
+	  Please read the comments at the top of
+	  <file:drivers/scsi/3w-9xxx.c>.
+
+config SCSI_7000FASST
+	tristate "7000FASST SCSI support"
+	depends on ISA && SCSI && ISA_DMA_API
+	select CHECK_SIGNATURE
+	help
+	  This driver supports the Western Digital 7000 SCSI host adapter
+	  family.  Some information is in the source:
+	  <file:drivers/scsi/wd7000.c>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called wd7000.
+
+config SCSI_ACARD
+	tristate "ACARD SCSI support"
+	depends on PCI && SCSI
+	help
+	  This driver supports the ACARD SCSI host adapter.
+	  Support Chip <ATP870 ATP876 ATP880 ATP885>
+	  To compile this driver as a module, choose M here: the
+	  module will be called atp870u.
+
+config SCSI_AHA152X
+	tristate "Adaptec AHA152X/2825 support"
+	depends on ISA && SCSI && !64BIT
+	select SCSI_SPI_ATTRS
+	select CHECK_SIGNATURE
+	---help---
+	  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
+	  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
+	  must be manually specified in this case.
+
+	  It is explained in section 3.3 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>. You might also want to
+	  read the file <file:Documentation/scsi/aha152x.txt>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called aha152x.
+
+config SCSI_AHA1542
+	tristate "Adaptec AHA1542 support"
+	depends on ISA && SCSI && ISA_DMA_API
+	---help---
+	  This is support for a SCSI host adapter.  It is explained in section
+	  3.4 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
+	  purchased by Adaptec, and some former Trantor products are being
+	  sold under the Adaptec name.  If it doesn't work out of the box, you
+	  may have to change some settings in <file:drivers/scsi/aha1542.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called aha1542.
+
+config SCSI_AHA1740
+	tristate "Adaptec AHA1740 support"
+	depends on EISA && SCSI
+	---help---
+	  This is support for a SCSI host adapter.  It is explained in section
+	  3.5 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/aha1740.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called aha1740.
+
+config SCSI_AACRAID
+	tristate "Adaptec AACRAID support"
+	depends on SCSI && PCI
+	help
+	  This driver supports a variety of Dell, HP, Adaptec, IBM and
+	  ICP storage products. For a list of supported products, refer
+	  to <file:Documentation/scsi/aacraid.txt>.
+
+	  To compile this driver as a module, choose M here: the module
+	  will be called aacraid.
+
+
+source "drivers/scsi/aic7xxx/Kconfig.aic7xxx"
+
+config SCSI_AIC7XXX_OLD
+	tristate "Adaptec AIC7xxx support (old driver)"
+	depends on (ISA || EISA || PCI ) && SCSI
+	help
+	  WARNING This driver is an older aic7xxx driver and is no longer
+	  under active development.  Adaptec, Inc. is writing a new driver to
+	  take the place of this one, and it is recommended that whenever
+	  possible, people should use the new Adaptec written driver instead
+	  of this one.  This driver will eventually be phased out entirely.
+
+	  This is support for the various aic7xxx based Adaptec SCSI
+	  controllers. These include the 274x EISA cards; 284x VLB cards;
+	  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
+	  motherboard based SCSI controllers from Adaptec. It does not support
+	  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
+	  support them. It does not support the 2920 cards from Adaptec that
+	  use the Future Domain SCSI controller chip. For those cards, you
+	  need the "Future Domain 16xx SCSI support" driver.
+
+	  In general, if the controller is based on an Adaptec SCSI controller
+	  chip from the aic777x series or the aic78xx series, this driver
+	  should work. The only exception is the 7810 which is specifically
+	  not supported (that's the RAID controller chip on the AAA-13x
+	  cards).
+
+	  Note that the AHA2920 SCSI host adapter is *not* supported by this
+	  driver; choose "Future Domain 16xx SCSI support" instead if you have
+	  one of those.
+
+	  Information on the configuration options for this controller can be
+	  found by checking the help file for each of the available
+	  configuration options. You should read
+	  <file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
+	  contacting the maintainer with any questions.  The SCSI-HOWTO,
+	  available from <http://www.tldp.org/docs.html#howto>, can also
+	  be of great help.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called aic7xxx_old.
+
+source "drivers/scsi/aic7xxx/Kconfig.aic79xx"
+source "drivers/scsi/aic94xx/Kconfig"
+
+# All the I2O code and drivers do not seem to be 64bit safe.
+config SCSI_DPT_I2O
+	tristate "Adaptec I2O RAID support "
+	depends on !64BIT && SCSI && PCI && VIRT_TO_BUS
+	help
+	  This driver supports all of Adaptec's I2O based RAID controllers as 
+	  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
+	  driver by Deanna Bonds.  See <file:Documentation/scsi/dpti.txt>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called dpt_i2o.
+
+config SCSI_ADVANSYS
+	tristate "AdvanSys SCSI support"
+	depends on SCSI
+	depends on ISA || EISA || PCI
+	depends on BROKEN || X86_32
+	help
+	  This is a driver for all SCSI host adapters manufactured by
+	  AdvanSys. It is documented in the kernel source in
+	  <file:drivers/scsi/advansys.c>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called advansys.
+
+config SCSI_IN2000
+	tristate "Always IN2000 SCSI support"
+	depends on ISA && SCSI
+	help
+	  This is support for an ISA bus SCSI host adapter.  You'll find more
+	  information in <file:Documentation/scsi/in2000.txt>. If it doesn't work
+	  out of the box, you may have to change the jumpers for IRQ or
+	  address selection.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called in2000.
+
+config SCSI_ARCMSR
+	tristate "ARECA ARC11X0[PCI-X]/ARC12X0[PCI-EXPRESS] SATA-RAID support"
+	depends on PCI && SCSI
+	help
+	  This driver supports all of ARECA's SATA RAID controller cards.
+	  This is an ARECA-maintained driver by Erich Chen.
+	  If you have any problems, please mail to: < erich@areca.com.tw >
+	  Areca supports Linux RAID config tools.
+
+	  < http://www.areca.com.tw >
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called arcmsr (modprobe arcmsr).
+
+source "drivers/scsi/megaraid/Kconfig.megaraid"
+
+config SCSI_HPTIOP
+	tristate "HighPoint RocketRAID 3xxx Controller support"
+	depends on SCSI && PCI
+	help
+	  This option enables support for HighPoint RocketRAID 3xxx
+	  controllers.
+
+	  To compile this driver as a module, choose M here; the module
+	  will be called hptiop. If unsure, say N.
+
+config SCSI_BUSLOGIC
+	tristate "BusLogic SCSI support"
+	depends on (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS
+	---help---
+	  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
+	  Adapters. Consult the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>, and the files
+	  <file:Documentation/scsi/BusLogic.txt> and
+	  <file:Documentation/scsi/FlashPoint.txt> for more information.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called BusLogic.
+
+config SCSI_OMIT_FLASHPOINT
+	bool "Omit FlashPoint support"
+	depends on SCSI_BUSLOGIC
+	help
+	  This option allows you to omit the FlashPoint support from the
+	  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
+	  substantial, so users of MultiMaster Host Adapters may wish to omit
+	  it.
+
+config SCSI_DMX3191D
+	tristate "DMX3191D SCSI support"
+	depends on PCI && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is support for Domex DMX3191D SCSI Host Adapters.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called dmx3191d.
+
+config SCSI_DTC3280
+	tristate "DTC3180/3280 SCSI support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	select CHECK_SIGNATURE
+	help
+	  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
+	  the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>, and the file
+	  <file:Documentation/scsi/dtc3x80.txt>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called dtc.
+
+config SCSI_EATA
+	tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
+	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
+	---help---
+	  This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
+	  ISA and all EISA I/O addresses are probed looking for the "EATA"
+	  signature. The addresses of all the PCI SCSI controllers reported
+          by the PCI subsystem are probed as well.
+
+	  You want to read the start of <file:drivers/scsi/eata.c> and the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called eata.
+
+config SCSI_EATA_TAGGED_QUEUE
+	bool "enable tagged command queueing"
+	depends on SCSI_EATA
+	help
+	  This is a feature of SCSI-2 which improves performance: the host
+	  adapter can send several SCSI commands to a device's queue even if
+	  previous commands haven't finished yet.
+	  This is equivalent to the "eata=tc:y" boot option.
+
+config SCSI_EATA_LINKED_COMMANDS
+	bool "enable elevator sorting"
+	depends on SCSI_EATA
+	help
+	  This option enables elevator sorting for all probed SCSI disks and
+	  CD-ROMs. It definitely reduces the average seek distance when doing
+	  random seeks, but this does not necessarily result in a noticeable
+	  performance improvement: your mileage may vary...
+	  This is equivalent to the "eata=lc:y" boot option.
+
+config SCSI_EATA_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on SCSI_EATA
+	default "16"
+	help
+	  This specifies how many SCSI commands can be maximally queued for
+	  each probed SCSI device. You should reduce the default value of 16
+	  only if you have disks with buggy or limited tagged command support.
+	  Minimum is 2 and maximum is 62. This value is also the window size
+	  used by the elevator sorting option above. The effective value used
+	  by the driver for each probed SCSI device is reported at boot time.
+	  This is equivalent to the "eata=mq:8" boot option.
+
+config SCSI_EATA_PIO
+	tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
+	depends on (ISA || EISA || PCI) && SCSI && BROKEN
+	---help---
+	  This driver supports all EATA-PIO protocol compliant SCSI Host
+	  Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
+	  host adapters could also use this driver but are discouraged from
+	  doing so, since this driver only supports hard disks and lacks
+	  numerous features.  You might want to have a look at the SCSI-HOWTO,
+	  available from <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called eata_pio.
+
+config SCSI_FUTURE_DOMAIN
+	tristate "Future Domain 16xx SCSI/AHA-2920A support"
+	depends on (ISA || PCI) && SCSI
+	select CHECK_SIGNATURE
+	---help---
+	  This is support for Future Domain's 16-bit SCSI host adapters
+	  (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
+	  other adapters based on the Future Domain chipsets (Quantum
+	  ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
+	  It is explained in section 3.7 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
+	  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
+	  controller support"). This Future Domain driver works with the older
+	  Adaptec AHA-2920A boards with a Future Domain chip on them.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called fdomain.
+
+config SCSI_FD_MCS
+	tristate "Future Domain MCS-600/700 SCSI support"
+	depends on MCA_LEGACY && SCSI
+	---help---
+	  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
+	  Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
+	  is identical to the MCS 700 and hence also supported by this driver.
+	  This driver also supports the Reply SB16/SCSI card (the SCSI part).
+	  It supports multiple adapters in the same system.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called fd_mcs.
+
+config SCSI_GDTH
+	tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
+	depends on (ISA || EISA || PCI) && SCSI && ISA_DMA_API
+	---help---
+	  Formerly called GDT SCSI Disk Array Controller Support.
+
+	  This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 
+	  manufactured by Intel Corporation/ICP vortex GmbH. It is documented
+	  in the kernel source in <file:drivers/scsi/gdth.c> and
+	  <file:drivers/scsi/gdth.h.>
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called gdth.
+
+config SCSI_GENERIC_NCR5380
+	tristate "Generic NCR5380/53c400 SCSI PIO support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This is a driver for the old NCR 53c80 series of SCSI controllers
+	  on boards using PIO. Most boards such as the Trantor T130 fit this
+	  category, along with a large number of ISA 8bit controllers shipped
+	  for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
+	  you should select the specific driver for that card rather than
+	  generic 5380 support.
+
+	  It is explained in section 3.8 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/g_NCR5380.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called g_NCR5380.
+
+config SCSI_GENERIC_NCR5380_MMIO
+	tristate "Generic NCR5380/53c400 SCSI MMIO support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This is a driver for the old NCR 53c80 series of SCSI controllers
+	  on boards using memory mapped I/O. 
+	  It is explained in section 3.8 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/g_NCR5380.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called g_NCR5380_mmio.
+
+config SCSI_GENERIC_NCR53C400
+	bool "Enable NCR53c400 extensions"
+	depends on SCSI_GENERIC_NCR5380
+	help
+	  This enables certain optimizations for the NCR53c400 SCSI cards.
+	  You might as well try it out.  Note that this driver will only probe
+	  for the Trantor T130B in its default configuration; you might have
+	  to pass a command line option to the kernel at boot time if it does
+	  not detect your card.  See the file
+	  <file:Documentation/scsi/g_NCR5380.txt> for details.
+
+config SCSI_IBMMCA
+	tristate "IBMMCA SCSI support"
+	depends on MCA && SCSI
+	---help---
+	  This is support for the IBM SCSI adapter found in many of the PS/2
+	  series computers.  These machines have an MCA bus, so you need to
+	  answer Y to "MCA support" as well and read
+	  <file:Documentation/mca.txt>.
+
+	  If the adapter isn't found during boot (a common problem for models
+	  56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
+	  option, where <pun> is the id of the SCSI subsystem (usually 7, but
+	  if that doesn't work check your reference diskette).  Owners of
+	  model 95 with a LED-matrix-display can in addition activate some
+	  activity info like under OS/2, but more informative, by setting
+	  'ibmmcascsi=display' as an additional kernel parameter.  Try "man
+	  bootparam" or see the documentation of your boot loader about how to
+	  pass options to the kernel.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ibmmca.
+
+config IBMMCA_SCSI_ORDER_STANDARD
+	bool "Standard SCSI-order"
+	depends on SCSI_IBMMCA
+	---help---
+	  In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
+	  are assigned to the drive letters, starting with the lowest SCSI-id
+	  (physical number -- pun) to be drive C:, as seen from DOS and
+	  similar operating systems. When looking into papers describing the
+	  ANSI-SCSI-standard, this assignment of drives appears to be wrong.
+	  The SCSI-standard follows a hardware-hierarchy which says that id 7
+	  has the highest priority and id 0 the lowest. Therefore, the host
+	  adapters are still today everywhere placed as SCSI-id 7 by default.
+	  In the SCSI-standard, the drive letters express the priority of the
+	  disk. C: should be the hard disk, or a partition on it, with the
+	  highest priority. This must therefore be the disk with the highest
+	  SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
+	  original definition of the SCSI-standard as also industrial- and
+	  process-control-machines, like VME-CPUs running under realtime-OSes
+	  (e.g. LynxOS, OS9) do.
+
+	  If you like to run Linux on your MCA-machine with the same
+	  assignment of hard disks as seen from e.g. DOS or OS/2 on your
+	  machine, which is in addition conformant to the SCSI-standard, you
+	  must say Y here. This is also necessary for MCA-Linux users who want
+	  to keep downward compatibility to older releases of the
+	  IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
+	  June 1997).
+
+	  If you like to have the lowest SCSI-id assigned as drive C:, as
+	  modern SCSI-BIOSes do, which does not conform to the standard, but
+	  is widespread and common in the PC-world of today, you must say N
+	  here. If unsure, say Y.
+
+config IBMMCA_SCSI_DEV_RESET
+	bool "Reset SCSI-devices at boottime"
+	depends on SCSI_IBMMCA
+	---help---
+	  By default, SCSI-devices are reset when the machine is powered on.
+	  However, some devices exist, like special-control-devices,
+	  SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
+	  not reset when switched on. If you say Y here, each device connected
+	  to your SCSI-bus will be issued a reset-command after it has been
+	  probed, while the kernel is booting. This may cause problems with
+	  more modern devices, like hard disks, which do not appreciate these
+	  reset commands, and can cause your system to hang. So say Y only if
+	  you know that one of your older devices needs it; N is the safe
+	  answer.
+
+config SCSI_IPS
+	tristate "IBM ServeRAID support"
+	depends on PCI && SCSI
+	---help---
+	  This is support for the IBM ServeRAID hardware RAID controllers.
+	  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
+	  for more information.  If this driver does not work correctly
+	  without modification please contact the author by email at
+	  <ipslinux@adaptec.com>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ips.
+
+config SCSI_IBMVSCSI
+	tristate "IBM Virtual SCSI support"
+	depends on PPC_PSERIES || PPC_ISERIES
+	help
+	  This is the IBM POWER Virtual SCSI Client
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ibmvscsic.
+
+config SCSI_IBMVSCSIS
+	tristate "IBM Virtual SCSI Server support"
+	depends on PPC_PSERIES && SCSI_TGT && SCSI_SRP
+	help
+	  This is the SRP target driver for IBM pSeries virtual environments.
+
+	  The userspace component needed to initialize the driver and
+	  documentation can be found:
+
+	  http://stgt.berlios.de/
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ibmvstgt.
+
+config SCSI_INITIO
+	tristate "Initio 9100U(W) support"
+	depends on PCI && SCSI
+	help
+	  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
+	  read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called initio.
+
+config SCSI_INIA100
+	tristate "Initio INI-A100U2W support"
+	depends on PCI && SCSI
+	help
+	  This is support for the Initio INI-A100U2W SCSI host adapter.
+	  Please read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called a100u2w.
+
+config SCSI_PPA
+	tristate "IOMEGA parallel port (ppa - older drives)"
+	depends on SCSI && PARPORT_PC
+	---help---
+	  This driver supports older versions of IOMEGA's parallel port ZIP
+	  drive (a 100 MB removable media device).
+
+	  Note that you can say N here if you have the SCSI version of the ZIP
+	  drive: it will be supported automatically if you said Y to the
+	  generic "SCSI disk support", above.
+
+	  If you have the ZIP Plus drive or a more recent parallel port ZIP
+	  drive (if the supplied cable with the drive is labeled "AutoDetect")
+	  then you should say N here and Y to "IOMEGA parallel port (imm -
+	  newer drives)", below.
+
+	  For more information about this driver and how to use it you should
+	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
+	  the SCSI-HOWTO, which is available from
+	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
+	  you will still be able to use the parallel port for other tasks,
+	  such as a printer; it is safe to compile both drivers into the
+	  kernel.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ppa.
+
+config SCSI_IMM
+	tristate "IOMEGA parallel port (imm - newer drives)"
+	depends on SCSI && PARPORT_PC
+	---help---
+	  This driver supports newer versions of IOMEGA's parallel port ZIP
+	  drive (a 100 MB removable media device).
+
+	  Note that you can say N here if you have the SCSI version of the ZIP
+	  drive: it will be supported automatically if you said Y to the
+	  generic "SCSI disk support", above.
+
+	  If you have the ZIP Plus drive or a more recent parallel port ZIP
+	  drive (if the supplied cable with the drive is labeled "AutoDetect")
+	  then you should say Y here; if you have an older ZIP drive, say N
+	  here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
+
+	  For more information about this driver and how to use it you should
+	  read the file <file:Documentation/scsi/ppa.txt>.  You should also read
+	  the SCSI-HOWTO, which is available from
+	  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
+	  you will still be able to use the parallel port for other tasks,
+	  such as a printer; it is safe to compile both drivers into the
+	  kernel.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called imm.
+
+config SCSI_IZIP_EPP16
+	bool "ppa/imm option - Use slow (but safe) EPP-16"
+	depends on SCSI_PPA || SCSI_IMM
+	---help---
+	  EPP (Enhanced Parallel Port) is a standard for parallel ports which
+	  allows them to act as expansion buses that can handle up to 64
+	  peripheral devices.
+
+	  Some parallel port chipsets are slower than their motherboard, and
+	  so we have to control the state of the chipset's FIFO queue every
+	  now and then to avoid data loss. This will be done if you say Y
+	  here.
+
+	  Generally, saying Y is the safe option and slows things down a bit.
+
+config SCSI_IZIP_SLOW_CTR
+	bool "ppa/imm option - Assume slow parport control register"
+	depends on SCSI_PPA || SCSI_IMM
+	help
+	  Some parallel ports are known to have excessive delays between
+	  changing the parallel port control register and good data being
+	  available on the parallel port data/status register. This option
+	  forces a small delay (1.0 usec to be exact) after changing the
+	  control register to let things settle out. Enabling this option may
+	  result in a big drop in performance but some very old parallel ports
+	  (found in 386 vintage machines) will not work properly.
+
+	  Generally, saying N is fine.
+
+config SCSI_NCR53C406A
+	tristate "NCR53c406a SCSI support"
+	depends on ISA && SCSI
+	help
+	  This is support for the NCR53c406a SCSI host adapter.  For user
+	  configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
+	  in the kernel source.  Also read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called NCR53c406.
+
+config SCSI_NCR_D700
+	tristate "NCR Dual 700 MCA SCSI support"
+	depends on MCA && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is a driver for the MicroChannel Dual 700 card produced by
+	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
+	  tries to negotiate sync and uses tag command queueing.
+
+	  Unless you have an NCR manufactured machine, the chances are that
+	  you do not have this SCSI card, so say N.
+
+config SCSI_LASI700
+	tristate "HP Lasi SCSI support for 53c700/710"
+	depends on GSC && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is a driver for the SCSI controller in the Lasi chip found in
+	  many PA-RISC workstations & servers.  If you do not know whether you
+	  have a Lasi chip, it is safe to say "Y" here.
+
+config SCSI_SNI_53C710
+	tristate "SNI RM SCSI support for 53c710"
+	depends on SNI_RM && SCSI
+	select SCSI_SPI_ATTRS
+	select 53C700_LE_ON_BE
+	help
+	  This is a driver for the onboard SCSI controller found in older
+	  SNI RM workstations & servers.
+
+config 53C700_LE_ON_BE
+	bool
+	depends on SCSI_LASI700
+	default y
+
+config SCSI_STEX
+	tristate "Promise SuperTrak EX Series support"
+	depends on PCI && SCSI
+	---help---
+	  This driver supports Promise SuperTrak EX series storage controllers.
+
+	  Promise provides Linux RAID configuration utility for these
+	  controllers. Please visit <http://www.promise.com> to download.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called stex.
+
+config 53C700_BE_BUS
+	bool
+	depends on SCSI_A4000T || SCSI_ZORRO7XX || MVME16x_SCSI || BVME6000_SCSI
+	default y
+
+config SCSI_SYM53C8XX_2
+	tristate "SYM53C8XX Version 2 SCSI support"
+	depends on PCI && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This driver supports the whole NCR53C8XX/SYM53C8XX family of
+	  PCI-SCSI controllers.  It also supports the subset of LSI53C10XX
+	  Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
+	  language.  It does not support LSI53C10XX Ultra-320 PCI-X SCSI
+	  controllers; you need to use the Fusion MPT driver for that.
+
+	  Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
+	  information.
+
+config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
+	int "DMA addressing mode"
+	depends on SCSI_SYM53C8XX_2
+	default "1"
+	---help---
+	  This option only applies to PCI-SCSI chips that are PCI DAC
+	  capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
+
+	  When set to 0, the driver will program the chip to only perform
+	  32-bit DMA.  When set to 1, the chip will be able to perform DMA
+	  to addresses up to 1TB.  When set to 2, the driver supports the
+	  full 64-bit DMA address range, but can only address 16 segments
+	  of 4 GB each.  This limits the total addressable range to 64 GB.
+
+	  Most machines with less than 4GB of memory should use a setting
+	  of 0 for best performance.  If your machine has 4GB of memory
+	  or more, you should set this option to 1 (the default).
+
+	  The still experimental value 2 (64 bit DMA addressing with 16
+	  x 4GB segments limitation) can be used on systems that require
+	  PCI address bits past bit 39 to be set for the addressing of
+	  memory using PCI DAC cycles.
+
+config SCSI_SYM53C8XX_DEFAULT_TAGS
+	int "Default tagged command queue depth"
+	depends on SCSI_SYM53C8XX_2
+	default "16"
+	help
+	  This is the default value of the command queue depth the
+	  driver will announce to the generic SCSI layer for devices
+	  that support tagged command queueing. This value can be changed
+	  from the boot command line.  This is a soft limit that cannot
+	  exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
+
+config SCSI_SYM53C8XX_MAX_TAGS
+	int "Maximum number of queued commands"
+	depends on SCSI_SYM53C8XX_2
+	default "64"
+	help
+	  This option allows you to specify the maximum number of commands
+	  that can be queued to any device, when tagged command queuing is
+	  possible. The driver supports up to 256 queued commands per device.
+	  This value is used as a compiled-in hard limit.
+
+config SCSI_SYM53C8XX_MMIO
+	bool "Use memory mapped IO"
+	depends on SCSI_SYM53C8XX_2
+	default y
+	help
+	  Memory mapped IO is faster than Port IO.  Most people should
+	  answer Y here, but some machines may have problems.  If you have
+	  to answer N here, please report the problem to the maintainer.
+
+config SCSI_IPR
+	tristate "IBM Power Linux RAID adapter support"
+	depends on PCI && SCSI && ATA
+	select FW_LOADER
+	---help---
+	  This driver supports the IBM Power Linux family RAID adapters.
+	  This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
+	  as IBM iSeries 5702, 5703, 5709, and 570A.
+
+config SCSI_IPR_TRACE
+	bool "enable driver internal trace"
+	depends on SCSI_IPR
+	default y
+	help
+	  If you say Y here, the driver will trace all commands issued
+	  to the adapter. Performance impact is minimal. Trace can be
+	  dumped using /sys/bus/class/scsi_host/hostXX/trace.
+
+config SCSI_IPR_DUMP
+	bool "enable adapter dump support"
+	depends on SCSI_IPR
+	default y
+	help
+	  If you say Y here, the driver will support adapter crash dump.
+	  If you enable this support, the iprdump daemon can be used
+	  to capture adapter failure analysis information.
+
+config SCSI_ZALON
+	tristate "Zalon SCSI support"
+	depends on GSC && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  The Zalon is a GSC/HSC bus interface chip that sits between the
+	  PA-RISC processor and the NCR 53c720 SCSI controller on C100,
+	  C110, J200, J210 and some D, K & R-class machines.  It's also
+	  used on the add-in Bluefish, Barracuda & Shrike SCSI cards.
+	  Say Y here if you have one of these machines or cards.
+
+config SCSI_NCR_Q720
+	tristate "NCR Quad 720 MCA SCSI support"
+	depends on MCA && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is a driver for the MicroChannel Quad 720 card produced by
+	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
+	  tries to negotiate sync and uses tag command queueing.
+
+	  Unless you have an NCR manufactured machine, the chances are that
+	  you do not have this SCSI card, so say N.
+
+config SCSI_NCR53C8XX_DEFAULT_TAGS
+	int "default tagged command queue depth"
+	depends on SCSI_ZALON || SCSI_NCR_Q720
+	default "8"
+	---help---
+	  "Tagged command queuing" is a feature of SCSI-2 which improves
+	  performance: the host adapter can send several SCSI commands to a
+	  device's queue even if previous commands haven't finished yet.
+	  Because the device is intelligent, it can optimize its operations
+	  (like head positioning) based on its own request queue. Some SCSI
+	  devices don't implement this properly; if you want to disable this
+	  feature, enter 0 or 1 here (it doesn't matter which).
+
+	  The default value is 8 and should be supported by most hard disks.
+	  This value can be overridden from the boot command line using the
+	  'tags' option as follows (example):
+	  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
+	  4, set queue depth to 16 for target 2 and target 3 on controller 0
+	  and set queue depth to 10 for target 0 / lun 2 on controller 1.
+
+	  The normal answer therefore is to go with the default 8 and to use
+	  a boot command line option for devices that need to use a different
+	  command queue depth.
+
+	  There is no safe option other than using good SCSI devices.
+
+config SCSI_NCR53C8XX_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on SCSI_ZALON || SCSI_NCR_Q720
+	default "32"
+	---help---
+	  This option allows you to specify the maximum number of commands
+	  that can be queued to any device, when tagged command queuing is
+	  possible. The default value is 32. Minimum is 2, maximum is 64.
+	  Modern hard disks are able to support 64 tags and even more, but
+	  do not seem to be faster when more than 32 tags are being used.
+
+	  So, the normal answer here is to go with the default value 32 unless
+	  you are using very large hard disks with large cache (>= 1 MB) that
+	  are able to take advantage of more than 32 tagged commands.
+
+	  There is no safe option and the default answer is recommended.
+
+config SCSI_NCR53C8XX_SYNC
+	int "synchronous transfers frequency in MHz"
+	depends on SCSI_ZALON || SCSI_NCR_Q720
+	default "20"
+	---help---
+	  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
+	  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
+	  are respectively the maximum data transfer rates in mega-transfers
+	  per second for each class.  For example, a FAST-20 Wide 16 device is
+	  able to transfer data at 20 million 16 bit packets per second for a
+	  total rate of 40 MB/s.
+
+	  You may specify 0 if you want to only use asynchronous data
+	  transfers. This is the safest and slowest option. Otherwise, specify
+	  a value between 5 and 80, depending on the capability of your SCSI
+	  controller.  The higher the number, the faster the data transfer.
+	  Note that 80 should normally be ok since the driver decreases the
+	  value automatically according to the controller's capabilities.
+
+	  Your answer to this question is ignored for controllers with NVRAM,
+	  since the driver will get this information from the user set-up.  It
+	  also can be overridden using a boot setup option, as follows
+	  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
+	  for FAST-20 synchronous data transfer (20 mega-transfers per
+	  second).
+
+	  The normal answer therefore is not to go with the default but to
+	  select the maximum value 80 allowing the driver to use the maximum
+	  value supported by each controller. If this causes problems with
+	  your SCSI devices, you should come back and decrease the value.
+
+	  There is no safe option other than using good cabling, right
+	  terminations and SCSI conformant devices.
+
+config SCSI_NCR53C8XX_NO_DISCONNECT
+	bool "not allow targets to disconnect"
+	depends on (SCSI_ZALON || SCSI_NCR_Q720) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
+	help
+	  This option is only provided for safety if you suspect some SCSI
+	  device of yours to not support properly the target-disconnect
+	  feature. In that case, you would say Y here. In general however, to
+	  not allow targets to disconnect is not reasonable if there is more
+	  than 1 device on a SCSI bus. The normal answer therefore is N.
+
+config SCSI_MCA_53C9X
+	tristate "NCR MCA 53C9x SCSI support"
+	depends on MCA_LEGACY && SCSI && BROKEN_ON_SMP
+	help
+	  Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
+	  controller based on the NCR 53C94.  This driver will allow use of
+	  the controller on the 3550, and very possibly others.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mca_53c9x.
+
+config SCSI_PAS16
+	tristate "PAS16 SCSI support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This is support for a SCSI host adapter.  It is explained in section
+	  3.10 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/pas16.h>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called pas16.
+
+config SCSI_PSI240I
+	tristate "PSI240i support"
+	depends on ISA && SCSI
+	help
+	  This is support for the PSI240i EIDE interface card which acts as a
+	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called psi240i.
+
+config SCSI_QLOGIC_FAS
+	tristate "Qlogic FAS SCSI support"
+	depends on ISA && SCSI
+	---help---
+	  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
+	  FastSCSI! cards as well as any other card based on the FASXX chip
+	  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
+
+	  This driver does NOT support the PCI versions of these cards. The
+	  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
+	  SCSI support"), below.
+
+	  Information about this driver is contained in
+	  <file:Documentation/scsi/qlogicfas.txt>.  You should also read the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called qlogicfas.
+
+config SCSI_QLOGIC_FC_FIRMWARE
+	bool "Include loadable firmware in driver"
+	depends on SCSI_QLOGIC_FC
+  	help
+	  Say Y to include ISP2X00 Fabric Initiator/Target Firmware, with
+	  expanded LUN addressing and FcTape (FCP-2) support, in the
+	  qlogicfc driver. This is required on some platforms.
+
+config SCSI_QLOGIC_1280
+	tristate "Qlogic QLA 1240/1x80/1x160 SCSI support"
+	depends on PCI && SCSI
+	help
+	  Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called qla1280.
+
+config SCSI_QLOGICPTI
+	tristate "PTI Qlogic, ISP Driver"
+	depends on SBUS && SCSI
+	help
+	  This driver supports SBUS SCSI controllers from PTI or QLogic. These
+	  controllers are known under Solaris as qpti and in the openprom as
+	  PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
+	  driven by a different driver.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called qlogicpti.
+
+source "drivers/scsi/qla2xxx/Kconfig"
+source "drivers/scsi/qla4xxx/Kconfig"
+
+config SCSI_LPFC
+	tristate "Emulex LightPulse Fibre Channel Support"
+	depends on PCI && SCSI
+	select SCSI_FC_ATTRS
+	help
+          This lpfc driver supports the Emulex LightPulse
+          Family of Fibre Channel PCI host adapters.
+
+config SCSI_SEAGATE
+	tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
+	depends on X86 && ISA && SCSI
+	select CHECK_SIGNATURE
+	---help---
+	  These are 8-bit SCSI controllers; the ST-01 is also supported by
+	  this driver.  It is explained in section 3.9 of the SCSI-HOWTO,
+	  available from <http://www.tldp.org/docs.html#howto>.  If it
+	  doesn't work out of the box, you may have to change some macros at
+	  compiletime, which are described in <file:drivers/scsi/seagate.c>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called seagate.
+
+# definitely looks not 64bit safe:
+config SCSI_SIM710
+	tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
+	depends on (EISA || MCA) && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  This driver for NCR53c710 based SCSI host adapters.
+
+	  It currently supports Compaq EISA cards and NCR MCA cards
+
+config SCSI_SYM53C416
+	tristate "Symbios 53c416 SCSI support"
+	depends on ISA && SCSI
+	---help---
+	  This is support for the sym53c416 SCSI host adapter, the SCSI
+	  adapter that comes with some HP scanners. This driver requires that
+	  the sym53c416 is configured first using some sort of PnP
+	  configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
+	  are using isapnp then you need to compile this driver as a module
+	  and then load it using insmod after isapnp has run. The parameters
+	  of the configured card(s) should be passed to the driver. The format
+	  is:
+
+	  insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called sym53c416.
+
+config SCSI_DC395x
+	tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support (EXPERIMENTAL)"
+	depends on PCI && SCSI && EXPERIMENTAL
+	---help---
+	  This driver supports PCI SCSI host adapters based on the ASIC
+	  TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
+
+	  This driver works, but is still in experimental status. So better
+	  have a bootable disk and a backup in case of emergency.
+
+	  Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called dc395x.
+
+config SCSI_DC390T
+	tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
+	depends on PCI && SCSI
+	---help---
+	  This driver supports PCI SCSI host adapters based on the Am53C974A
+	  chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
+	  PCscsi/PCnet (Am53/79C974) solutions.
+
+	  Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
+
+	  Note that this driver does NOT support Tekram DC390W/U/F, which are
+	  based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called tmscsim.
+
+config SCSI_T128
+	tristate "Trantor T128/T128F/T228 SCSI support"
+	depends on ISA && SCSI
+	select SCSI_SPI_ATTRS
+	select CHECK_SIGNATURE
+	---help---
+	  This is support for a SCSI host adapter. It is explained in section
+	  3.11 of the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
+	  Adaptec, and some former Trantor products are being sold under the
+	  Adaptec name.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called t128.
+
+config SCSI_U14_34F
+	tristate "UltraStor 14F/34F support"
+	depends on ISA && SCSI && ISA_DMA_API
+	---help---
+	  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
+	  The source at <file:drivers/scsi/u14-34f.c> contains some
+	  information about this hardware.  If the driver doesn't work out of
+	  the box, you may have to change some settings in
+	  <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  Note that there is also
+	  another driver for the same hardware: "UltraStor SCSI support",
+	  below.  You should say Y to both only if you want 24F support as
+	  well.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called u14-34f.
+
+config SCSI_U14_34F_TAGGED_QUEUE
+	bool "enable tagged command queueing"
+	depends on SCSI_U14_34F
+	help
+	  This is a feature of SCSI-2 which improves performance: the host
+	  adapter can send several SCSI commands to a device's queue even if
+	  previous commands haven't finished yet.
+	  This is equivalent to the "u14-34f=tc:y" boot option.
+
+config SCSI_U14_34F_LINKED_COMMANDS
+	bool "enable elevator sorting"
+	depends on SCSI_U14_34F
+	help
+	  This option enables elevator sorting for all probed SCSI disks and
+	  CD-ROMs. It definitely reduces the average seek distance when doing
+	  random seeks, but this does not necessarily result in a noticeable
+	  performance improvement: your mileage may vary...
+	  This is equivalent to the "u14-34f=lc:y" boot option.
+
+config SCSI_U14_34F_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on SCSI_U14_34F
+	default "8"
+	help
+	  This specifies how many SCSI commands can be maximally queued for
+	  each probed SCSI device. You should reduce the default value of 8
+	  only if you have disks with buggy or limited tagged command support.
+	  Minimum is 2 and maximum is 14. This value is also the window size
+	  used by the elevator sorting option above. The effective value used
+	  by the driver for each probed SCSI device is reported at boot time.
+	  This is equivalent to the "u14-34f=mq:8" boot option.
+
+config SCSI_ULTRASTOR
+	tristate "UltraStor SCSI support"
+	depends on X86 && ISA && SCSI
+	---help---
+	  This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
+	  adapter family.  This driver is explained in section 3.12 of the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/ultrastor.h>.
+
+	  Note that there is also another driver for the same hardware:
+	  "UltraStor 14F/34F support", above.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called ultrastor.
+
+config SCSI_NSP32
+	tristate "Workbit NinjaSCSI-32Bi/UDE support"
+	depends on PCI && SCSI && !64BIT
+	help
+	  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
+	  SCSI host adapter. Please read the SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called nsp32.
+
+config SCSI_DEBUG
+	tristate "SCSI debugging host simulator"
+	depends on SCSI
+	help
+	  This is a host adapter simulator that can simulate multiple hosts
+	  each with multiple dummy SCSI devices (disks). It defaults to one
+	  host adapter with one dummy SCSI disk. Each dummy disk uses kernel
+	  RAM as storage (i.e. it is a ramdisk). To save space when multiple
+	  dummy disks are simulated, they share the same kernel RAM for 
+	  their storage. See <http://www.torque.net/sg/sdebug.html> for more
+	  information. This driver is primarily of use to those testing the
+	  SCSI and block subsystems. If unsure, say N.
+
+config SCSI_MESH
+	tristate "MESH (Power Mac internal SCSI) support"
+	depends on PPC32 && PPC_PMAC && SCSI
+	help
+	  Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
+	  SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
+	  other Power Macintoshes do). Say Y to include support for this SCSI
+	  adaptor.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mesh.
+
+config SCSI_MESH_SYNC_RATE
+	int "maximum synchronous transfer rate (MB/s) (0 = async)"
+	depends on SCSI_MESH
+	default "5"
+	help
+	  On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
+	  drives a bus which is entirely internal to the machine (such as the
+	  7500, 7600, 8500, etc.), the MESH is capable of synchronous
+	  operation at up to 10 MB/s. On machines where the SCSI bus
+	  controlled by the MESH can have external devices connected, it is
+	  usually rated at 5 MB/s. 5 is a safe value here unless you know the
+	  MESH SCSI bus is internal only; in that case you can say 10. Say 0
+	  to disable synchronous operation.
+
+config SCSI_MESH_RESET_DELAY_MS
+	int "initial bus reset delay (ms) (0 = no reset)"
+	depends on SCSI_MESH
+	default "4000"
+
+config SCSI_MAC53C94
+	tristate "53C94 (Power Mac external SCSI) support"
+	depends on PPC32 && PPC_PMAC && SCSI
+	help
+	  On Power Macintoshes (and clones) with two SCSI buses, the external
+	  SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
+	  machines which only have one SCSI bus, such as the 7200, also use
+	  the 53C94. Say Y to include support for the 53C94.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mac53c94.
+
+source "drivers/scsi/arm/Kconfig"
+
+config JAZZ_ESP
+	bool "MIPS JAZZ FAS216 SCSI support"
+	depends on MACH_JAZZ && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is the driver for the onboard SCSI host adapter of MIPS Magnum
+	  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
+	  systems.
+
+config A3000_SCSI
+	tristate "A3000 WD33C93A support"
+	depends on AMIGA && SCSI
+	help
+	  If you have an Amiga 3000 and have SCSI devices connected to the
+	  built-in SCSI controller, say Y. Otherwise, say N.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called a3000.
+
+config A2091_SCSI
+	tristate "A2091/A590 WD33C93A support"
+	depends on ZORRO && SCSI
+	help
+	  If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
+	  say N.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called a2091.
+
+config GVP11_SCSI
+	tristate "GVP Series II WD33C93A support"
+	depends on ZORRO && SCSI
+	---help---
+	  If you have a Great Valley Products Series II SCSI controller,
+	  answer Y. Also say Y if you have a later model of GVP SCSI
+	  controller (such as the GVP A4008 or a Combo board). Otherwise,
+	  answer N. This driver does NOT work for the T-Rex series of
+	  accelerators from TekMagic and GVP-M.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called gvp11.
+
+config CYBERSTORM_SCSI
+	tristate "CyberStorm SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga with an original (MkI) Phase5 Cyberstorm
+	  accelerator board and the optional Cyberstorm SCSI controller,
+	  answer Y. Otherwise, say N.
+
+config CYBERSTORMII_SCSI
+	tristate "CyberStorm Mk II SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
+	  and the optional Cyberstorm SCSI controller, say Y. Otherwise,
+	  answer N.
+
+config BLZ2060_SCSI
+	tristate "Blizzard 2060 SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
+	  and want to use the onboard SCSI controller, say Y. Otherwise,
+	  answer N.
+
+config BLZ1230_SCSI
+	tristate "Blizzard 1230IV/1260 SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
+	  1260 accelerator, and the optional SCSI module, say Y. Otherwise,
+	  say N.
+
+config FASTLANE_SCSI
+	tristate "Fastlane SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
+	  one in the near future, say Y to this question. Otherwise, say N.
+
+config SCSI_A4000T
+	tristate "A4000T NCR53c710 SCSI support (EXPERIMENTAL)"
+	depends on AMIGA && SCSI && EXPERIMENTAL
+	select SCSI_SPI_ATTRS
+	help
+	  If you have an Amiga 4000T and have SCSI devices connected to the
+	  built-in SCSI controller, say Y. Otherwise, say N.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called a4000t.
+
+config SCSI_ZORRO7XX
+	tristate "Zorro NCR53c710 SCSI support (EXPERIMENTAL)"
+	depends on ZORRO && SCSI && EXPERIMENTAL
+	select SCSI_SPI_ATTRS
+	help
+	  Support for various NCR53c710-based SCSI controllers on Zorro
+	  expansion boards for the Amiga.
+	  This includes:
+	    - the Amiga 4091 Zorro III SCSI-2 controller,
+	    - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
+	      (info at
+	      <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
+	    - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
+	      accelerator card for the Amiga 1200,
+	    - the SCSI controller on the GVP Turbo 040/060 accelerator.
+
+config OKTAGON_SCSI
+	tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
+	depends on ZORRO && SCSI && EXPERIMENTAL
+	help
+	  If you have the BSC Oktagon SCSI disk controller for the Amiga, say
+	  Y to this question.  If you're in doubt about whether you have one,
+	  see the picture at
+	  <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
+
+config ATARI_SCSI
+	tristate "Atari native SCSI support"
+	depends on ATARI && SCSI
+	select SCSI_SPI_ATTRS
+	---help---
+	  If you have an Atari with built-in NCR5380 SCSI controller (TT,
+	  Falcon, ...) say Y to get it supported. Of course also, if you have
+	  a compatible SCSI controller (e.g. for Medusa).
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called atari_scsi.
+
+	  This driver supports both styles of NCR integration into the
+	  system: the TT style (separate DMA), and the Falcon style (via
+	  ST-DMA, replacing ACSI).  It does NOT support other schemes, like
+	  in the Hades (without DMA).
+
+config ATARI_SCSI_TOSHIBA_DELAY
+	bool "Long delays for Toshiba CD-ROMs"
+	depends on ATARI_SCSI
+	help
+	  This option increases the delay after a SCSI arbitration to
+	  accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
+	  use a Toshiba CD-ROM drive; otherwise, the option is not needed and
+	  would impact performance a bit, so say N.
+
+config ATARI_SCSI_RESET_BOOT
+	bool "Reset SCSI-devices at boottime"
+	depends on ATARI_SCSI
+	help
+	  Reset the devices on your Atari whenever it boots.  This makes the
+	  boot process fractionally longer but may assist recovery from errors
+	  that leave the devices with SCSI operations partway completed.
+
+config TT_DMA_EMUL
+	bool "Hades SCSI DMA emulator"
+	depends on ATARI_SCSI && HADES
+	help
+	  This option enables code which emulates the TT SCSI DMA chip on the
+	  Hades. This increases the SCSI transfer rates at least ten times
+	  compared to PIO transfers.
+
+config MAC_SCSI
+	bool "Macintosh NCR5380 SCSI"
+	depends on MAC && SCSI=y
+	select SCSI_SPI_ATTRS
+	help
+	  This is the NCR 5380 SCSI controller included on most of the 68030
+	  based Macintoshes.  If you have one of these say Y and read the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+config SCSI_MAC_ESP
+	tristate "Macintosh NCR53c9[46] SCSI"
+	depends on MAC && SCSI
+	help
+	  This is the NCR 53c9x SCSI controller found on most of the 68040
+	  based Macintoshes.  If you have one of these say Y and read the
+	  SCSI-HOWTO, available from
+	  <http://www.tldp.org/docs.html#howto>.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mac_esp.
+
+config MVME147_SCSI
+	bool "WD33C93 SCSI driver for MVME147"
+	depends on MVME147 && SCSI=y
+	select SCSI_SPI_ATTRS
+	help
+	  Support for the on-board SCSI controller on the Motorola MVME147
+	  single-board computer.
+
+config MVME16x_SCSI
+	tristate "NCR53C710 SCSI driver for MVME16x"
+	depends on MVME16x && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
+	  SCSI controller chip.  Almost everyone using one of these boards
+	  will want to say Y to this question.
+
+config BVME6000_SCSI
+	tristate "NCR53C710 SCSI driver for BVME6000"
+	depends on BVME6000 && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
+	  SCSI controller chip.  Almost everyone using one of these boards
+	  will want to say Y to this question.
+
+config SUN3_SCSI
+	tristate "Sun3 NCR5380 SCSI"
+	depends on SUN3 && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This option will enable support for the OBIO (onboard io) NCR5380
+	  SCSI controller found in the Sun 3/50 and 3/60, as well as for
+	  "Sun3" type VME scsi controllers also based on the NCR5380.
+	  General Linux information on the Sun 3 series (now discontinued)
+	  is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
+
+config SUN3X_ESP
+	bool "Sun3x ESP SCSI"
+	depends on SUN3X && SCSI=y
+	help
+	  The ESP was an on-board SCSI controller used on Sun 3/80
+	  machines.  Say Y here to compile in support for it.
+
+config SCSI_SUNESP
+	tristate "Sparc ESP Scsi Driver"
+	depends on SBUS && SCSI
+	select SCSI_SPI_ATTRS
+	help
+	  This is the driver for the Sun ESP SCSI host adapter. The ESP
+	  chipset is present in most SPARC SBUS-based computers.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called esp.
+
+config ZFCP
+	tristate "FCP host bus adapter driver for IBM eServer zSeries"
+	depends on S390 && QDIO && SCSI
+	select SCSI_FC_ATTRS
+	help
+          If you want to access SCSI devices attached to your IBM eServer
+          zSeries by means of Fibre Channel interfaces say Y.
+          For details please refer to the documentation provided by IBM at
+          <http://oss.software.ibm.com/developerworks/opensource/linux390>
+
+          This driver is also available as a module. This module will be
+          called zfcp. If you want to compile it as a module, say M here
+          and read <file:Documentation/kbuild/modules.txt>.
+
+config SCSI_SRP
+	tristate "SCSI RDMA Protocol helper library"
+	depends on SCSI && PCI
+	select SCSI_TGT
+	help
+	  If you wish to use SRP target drivers, say Y.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called libsrp.
+
+endif # SCSI_LOWLEVEL
+
+source "drivers/scsi/pcmcia/Kconfig"
+
+endmenu

-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

Re: [PATCH] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[Lennart Sorensen]

On Fri, Sep 14, 2007 at 06:01:53PM +0200, Stefan Richter wrote:
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
> ---
> 
> Applicable to 2.6.23-rc6 and to scsi-misc.
> 
>  drivers/scsi/Kconfig |   32 ++++++++++++++++++++------------
>  1 file changed, 20 insertions(+), 12 deletions(-)
> 
> Index: linux-2.6.23-rc6/drivers/scsi/Kconfig
> ===================================================================
> --- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig
> +++ linux-2.6.23-rc6/drivers/scsi/Kconfig
> @@ -12,23 +12,31 @@ config SCSI
>  	depends on BLOCK
>  	select SCSI_DMA if HAS_DMA
>  	---help---
> -	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
> -	  any other SCSI device under Linux, say Y and make sure that you know
> -	  the name of your SCSI host adapter (the card inside your computer
> -	  that "speaks" the SCSI protocol, also called SCSI controller),
> -	  because you will be asked for it.
> -
> -	  You also need to say Y here if you have a device which speaks
> -	  the SCSI protocol.  Examples of this include the parallel port
> -	  version of the IOMEGA ZIP drive, USB storage devices, Fibre
> -	  Channel, FireWire storage and the IDE-SCSI emulation driver.
> +	  This option enables core support for SCSI protocols.
> +	  You need it
> +	  - for classic parallel SCSI hardware,
> +	  - for newer SCSI transports such as Fibre Channel, FireWire storage,
> +	    or iSCSI,
> +	  - for non-SCSI hardware which speaks SCSI protocols, such as USB
> +	    storage devices or the parallel port version of Iomega Zip drive,
> +	  - for non-SCSI hardware whose drivers translate from and to SCSI
> +	    protocols, like the IDE-SCSI emulation driver and most notably
> +	    for all SATA drivers.
>  
>  	  To compile this driver as a module, choose M here and read
>  	  <file:Documentation/scsi/scsi.txt>.
>  	  The module will be called scsi_mod.
>  
>  	  However, do not compile this as a module if your root file system
> -	  (the one containing the directory /) is located on a SCSI device.
> +	  (the one containing the directory /) is located on a SCSI device
> +	  or on a device whose driver represents it as SCSI device, as
> +	  indicated above.  Choose Y in this case, or set up an initrd.
> +
> +	  Subsequent options in this menu enable specific SCSI command set
> +	  support for harddisks, CD/DVD-ROM/R/W, tapes etc..  This menu also
> +	  presents options for specific SCSI controllers, while options for
> +	  some other SCSI transports and all non-SCSI controllers are located
> +	  in other menus (SATA, USB, FireWire etc.).
>  
>  config SCSI_DMA
>  	bool
> @@ -120,7 +128,7 @@ config BLK_DEV_SR
>  	tristate "SCSI CDROM support"
>  	depends on SCSI
>  	---help---
> -	  If you want to use a SCSI or FireWire CD-ROM under Linux,
> +	  If you want to use a SCSI, SATA, USB or FireWire CD-ROM or DVD-ROM,
>  	  say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
>  	  <http://www.tldp.org/docs.html#howto>. Also make sure to say
>  	  Y or M to "ISO 9660 CD-ROM file system support" later.

You left out PATA running libata drivers.  Not just SATA is affected
there.  Looks pretty decent otherwise.

--
Len Sorensen

Re: [PATCH] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[Stefan Richter]

On 14 Sep, Lennart Sorensen wrote:
> On Fri, Sep 14, 2007 at 06:01:53PM +0200, Stefan Richter wrote:
...
>> +	  - for non-SCSI hardware whose drivers translate from and to SCSI
>> +	    protocols, like the IDE-SCSI emulation driver and most notably
>> +	    for all SATA drivers.
...
> You left out PATA running libata drivers.  Not just SATA is affected
> there.  Looks pretty decent otherwise.


From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: SCSI: update Kconfig help text to indicate SCSI core's widespread usage

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---
 drivers/scsi/Kconfig |   32 ++++++++++++++++++++------------
 1 file changed, 20 insertions(+), 12 deletions(-)

Index: linux-2.6.23-rc6/drivers/scsi/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig
+++ linux-2.6.23-rc6/drivers/scsi/Kconfig
@@ -12,23 +12,31 @@ config SCSI
 	depends on BLOCK
 	select SCSI_DMA if HAS_DMA
 	---help---
-	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
-	  any other SCSI device under Linux, say Y and make sure that you know
-	  the name of your SCSI host adapter (the card inside your computer
-	  that "speaks" the SCSI protocol, also called SCSI controller),
-	  because you will be asked for it.
-
-	  You also need to say Y here if you have a device which speaks
-	  the SCSI protocol.  Examples of this include the parallel port
-	  version of the IOMEGA ZIP drive, USB storage devices, Fibre
-	  Channel, FireWire storage and the IDE-SCSI emulation driver.
+	  This option enables core support for SCSI protocols.
+	  You need it
+	  - for classic parallel SCSI hardware,
+	  - for newer SCSI transports such as Fibre Channel, FireWire storage,
+	    or iSCSI,
+	  - for non-SCSI hardware which speaks SCSI protocols, such as USB
+	    storage devices or the parallel port version of Iomega Zip drive,
+	  - for non-SCSI hardware whose drivers translate from and to SCSI
+	    protocols, most notably all Serial ATA drivers, and Parallel ATA
+	    via the ATA configuration option.
 
 	  To compile this driver as a module, choose M here and read
 	  <file:Documentation/scsi/scsi.txt>.
 	  The module will be called scsi_mod.
 
 	  However, do not compile this as a module if your root file system
-	  (the one containing the directory /) is located on a SCSI device.
+	  (the one containing the directory /) is located on a SCSI device
+	  or on a device whose driver represents it as SCSI device, as
+	  indicated above.  Choose Y in this case, or set up an initrd.
+
+	  Subsequent options in this menu enable specific SCSI command set
+	  support for harddisks, CD/DVD-ROM/R/W, tapes etc..  This menu also
+	  presents options for specific SCSI controllers, while options for
+	  some other SCSI transports and all non-SCSI controllers are located
+	  in other menus (SATA, USB, FireWire etc.).
 
 config SCSI_DMA
 	bool
@@ -120,7 +128,7 @@ config BLK_DEV_SR
 	tristate "SCSI CDROM support"
 	depends on SCSI
 	---help---
-	  If you want to use a SCSI or FireWire CD-ROM under Linux,
+	  If you want to use a SCSI, SATA, USB or FireWire CD-ROM or DVD-ROM,
 	  say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
 	  <http://www.tldp.org/docs.html#howto>. Also make sure to say
 	  Y or M to "ISO 9660 CD-ROM file system support" later.

-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

Re: [PATCH] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[Lennart Sorensen]

On Fri, Sep 14, 2007 at 10:14:16PM +0200, Stefan Richter wrote:
> -	  If you want to use a SCSI or FireWire CD-ROM under Linux,
> +	  If you want to use a SCSI, SATA, USB or FireWire CD-ROM or DVD-ROM,
>  	  say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
>  	  <http://www.tldp.org/docs.html#howto>. Also make sure to say
>  	  Y or M to "ISO 9660 CD-ROM file system support" later.

How about that one for libata driven PATA CDROM drives?  Could replace
SATA with libata, or something similar.

--
Len Sorensen

Re: [PATCH] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[Stefan Richter]

On 14 Sep, Lennart Sorensen wrote:
> On Fri, Sep 14, 2007 at 10:14:16PM +0200, Stefan Richter wrote:
>> -	  If you want to use a SCSI or FireWire CD-ROM under Linux,
>> +	  If you want to use a SCSI, SATA, USB or FireWire CD-ROM or DVD-ROM,
>>  	  say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
>>  	  <http://www.tldp.org/docs.html#howto>. Also make sure to say
>>  	  Y or M to "ISO 9660 CD-ROM file system support" later.
> 
> How about that one for libata driven PATA CDROM drives?  Could replace
> SATA with libata, or something similar.


From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: SCSI: update Kconfig help text to indicate SCSI core's widespread usage

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---
 drivers/scsi/Kconfig |   67 ++++++++++++++++++++++---------------------
 1 file changed, 35 insertions(+), 32 deletions(-)

Index: linux-2.6.23-rc6/drivers/scsi/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig
+++ linux-2.6.23-rc6/drivers/scsi/Kconfig
@@ -12,23 +12,31 @@ config SCSI
 	depends on BLOCK
 	select SCSI_DMA if HAS_DMA
 	---help---
-	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
-	  any other SCSI device under Linux, say Y and make sure that you know
-	  the name of your SCSI host adapter (the card inside your computer
-	  that "speaks" the SCSI protocol, also called SCSI controller),
-	  because you will be asked for it.
-
-	  You also need to say Y here if you have a device which speaks
-	  the SCSI protocol.  Examples of this include the parallel port
-	  version of the IOMEGA ZIP drive, USB storage devices, Fibre
-	  Channel, FireWire storage and the IDE-SCSI emulation driver.
+	  This option enables core support for SCSI protocols.
+	  You need it
+	  - for classic parallel SCSI hardware,
+	  - for newer SCSI transports such as Fibre Channel, FireWire storage,
+	    or iSCSI,
+	  - for non-SCSI hardware which speaks SCSI protocols, such as USB
+	    storage devices or the parallel port version of Iomega Zip drive,
+	  - for non-SCSI hardware whose drivers translate from and to SCSI
+	    protocols, most notably all Serial ATA drivers, and Parallel ATA
+	    via the ATA configuration option.
 
 	  To compile this driver as a module, choose M here and read
 	  <file:Documentation/scsi/scsi.txt>.
 	  The module will be called scsi_mod.
 
 	  However, do not compile this as a module if your root file system
-	  (the one containing the directory /) is located on a SCSI device.
+	  (the one containing the directory /) is located on a SCSI device
+	  or on a device whose driver represents it as SCSI device, as
+	  indicated above.  Choose Y in this case, or set up an initrd.
+
+	  Subsequent options in this menu enable specific SCSI command set
+	  support for harddisks, CD/DVD-ROM/R/W, tapes etc..  This menu also
+	  presents options for specific SCSI controllers, while options for
+	  some other SCSI transports and all non-SCSI controllers are located
+	  in other menus (SATA, USB, FireWire etc.).
 
 config SCSI_DMA
 	bool
@@ -57,32 +65,27 @@ config SCSI_PROC_FS
 
 	  If unsure say Y.
 
-comment "SCSI support type (disk, tape, CD-ROM)"
+comment "SCSI command set drivers (disk, tape, CD-ROM)"
 	depends on SCSI
 
 config BLK_DEV_SD
-	tristate "SCSI disk support"
+	tristate "Harddisks and other Direct access devices"
 	depends on SCSI
 	---help---
-	  If you want to use SCSI hard disks, Fibre Channel disks,
-	  Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
-	  USB storage or the SCSI or parallel port version of
-	  the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
-	  the Disk-HOWTO and the Multi-Disk-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
-	  CD-ROMs.
+	  Say Y if you want to use harddisks and similar block-oriented devices
+	  via SCSI or via drivers which use SCSI command sets (e.g. the Serial
+	  and Parallel ATA kernel subsystem, USB, and more).
 
 	  To compile this driver as a module, choose M here and read
 	  <file:Documentation/scsi/scsi.txt>.
 	  The module will be called sd_mod.
 
-	  Do not compile this driver as a module if your root file system
-	  (the one containing the directory /) is located on a SCSI disk.
-	  In this case, do not compile the driver for your SCSI host adapter
-	  (below) as a module either.
+	  If your root file system (the one containing the directory /) is
+	  located on a disk which accessed via this driver, choose Y instead of
+	  M or set up a suitable initrd.
 
 config CHR_DEV_ST
-	tristate "SCSI tape support"
+	tristate "Tape drives"
 	depends on SCSI
 	---help---
 	  If you want to use a SCSI tape drive under Linux, say Y and read the
@@ -95,7 +98,7 @@ config CHR_DEV_ST
 	  <file:Documentation/scsi/scsi.txt>. The module will be called st.
 
 config CHR_DEV_OSST
-	tristate "SCSI OnStream SC-x0 tape support"
+	tristate "SCSI OnStream SC-x0 tape drives"
 	depends on SCSI
 	---help---
 	  The OnStream SC-x0 SCSI tape drives cannot be driven by the
@@ -117,13 +120,13 @@ config CHR_DEV_OSST
 	  <file:Documentation/scsi/scsi.txt>. The module will be called osst.
 
 config BLK_DEV_SR
-	tristate "SCSI CDROM support"
+	tristate "CD-ROMs, DVD-ROMs"
 	depends on SCSI
 	---help---
-	  If you want to use a SCSI or FireWire CD-ROM under Linux,
-	  say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
-	  <http://www.tldp.org/docs.html#howto>. Also make sure to say
-	  Y or M to "ISO 9660 CD-ROM file system support" later.
+	  Say Y if you want to use CD-ROMs or DVD-ROMs via SCSI or via drivers
+	  which use SCSI command sets (e.g. the Serial and Parallel ATA kernel
+	  subsystem, USB, and more). Also make sure to say Y or M to "ISO 9660
+	  CD-ROM file system support" later.
 
 	  To compile this driver as a module, choose M here and read
 	  <file:Documentation/scsi/scsi.txt>.
@@ -164,7 +167,7 @@ config CHR_DEV_SG
 	  If unsure, say N.
 
 config CHR_DEV_SCH
-	tristate "SCSI media changer support"
+	tristate "SCSI media changers"
 	depends on SCSI
 	---help---
 	  This is a driver for SCSI media changers.  Most common devices are

-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

Re: [PATCH] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[Lennart Sorensen]

On Fri, Sep 14, 2007 at 11:06:44PM +0200, Stefan Richter wrote:
> On 14 Sep, Lennart Sorensen wrote:
> > On Fri, Sep 14, 2007 at 10:14:16PM +0200, Stefan Richter wrote:
> >> -	  If you want to use a SCSI or FireWire CD-ROM under Linux,
> >> +	  If you want to use a SCSI, SATA, USB or FireWire CD-ROM or DVD-ROM,
> >>  	  say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
> >>  	  <http://www.tldp.org/docs.html#howto>. Also make sure to say
> >>  	  Y or M to "ISO 9660 CD-ROM file system support" later.
> > 
> > How about that one for libata driven PATA CDROM drives?  Could replace
> > SATA with libata, or something similar.
> 
> 
> From: Stefan Richter <stefanr@s5r6.in-berlin.de>
> Subject: SCSI: update Kconfig help text to indicate SCSI core's widespread usage
> 
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
> ---
>  drivers/scsi/Kconfig |   67 ++++++++++++++++++++++---------------------
>  1 file changed, 35 insertions(+), 32 deletions(-)
> 
> Index: linux-2.6.23-rc6/drivers/scsi/Kconfig
> ===================================================================
> --- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig
> +++ linux-2.6.23-rc6/drivers/scsi/Kconfig
> @@ -12,23 +12,31 @@ config SCSI
>  	depends on BLOCK
>  	select SCSI_DMA if HAS_DMA
>  	---help---
> -	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
> -	  any other SCSI device under Linux, say Y and make sure that you know
> -	  the name of your SCSI host adapter (the card inside your computer
> -	  that "speaks" the SCSI protocol, also called SCSI controller),
> -	  because you will be asked for it.
> -
> -	  You also need to say Y here if you have a device which speaks
> -	  the SCSI protocol.  Examples of this include the parallel port
> -	  version of the IOMEGA ZIP drive, USB storage devices, Fibre
> -	  Channel, FireWire storage and the IDE-SCSI emulation driver.
> +	  This option enables core support for SCSI protocols.
> +	  You need it
> +	  - for classic parallel SCSI hardware,
> +	  - for newer SCSI transports such as Fibre Channel, FireWire storage,
> +	    or iSCSI,
> +	  - for non-SCSI hardware which speaks SCSI protocols, such as USB
> +	    storage devices or the parallel port version of Iomega Zip drive,
> +	  - for non-SCSI hardware whose drivers translate from and to SCSI
> +	    protocols, most notably all Serial ATA drivers, and Parallel ATA
> +	    via the ATA configuration option.
>  
>  	  To compile this driver as a module, choose M here and read
>  	  <file:Documentation/scsi/scsi.txt>.
>  	  The module will be called scsi_mod.
>  
>  	  However, do not compile this as a module if your root file system
> -	  (the one containing the directory /) is located on a SCSI device.
> +	  (the one containing the directory /) is located on a SCSI device
> +	  or on a device whose driver represents it as SCSI device, as
> +	  indicated above.  Choose Y in this case, or set up an initrd.
> +
> +	  Subsequent options in this menu enable specific SCSI command set
> +	  support for harddisks, CD/DVD-ROM/R/W, tapes etc..  This menu also
> +	  presents options for specific SCSI controllers, while options for
> +	  some other SCSI transports and all non-SCSI controllers are located
> +	  in other menus (SATA, USB, FireWire etc.).
>  
>  config SCSI_DMA
>  	bool
> @@ -57,32 +65,27 @@ config SCSI_PROC_FS
>  
>  	  If unsure say Y.
>  
> -comment "SCSI support type (disk, tape, CD-ROM)"
> +comment "SCSI command set drivers (disk, tape, CD-ROM)"
>  	depends on SCSI
>  
>  config BLK_DEV_SD
> -	tristate "SCSI disk support"
> +	tristate "Harddisks and other Direct access devices"
>  	depends on SCSI
>  	---help---
> -	  If you want to use SCSI hard disks, Fibre Channel disks,
> -	  Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
> -	  USB storage or the SCSI or parallel port version of
> -	  the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
> -	  the Disk-HOWTO and the Multi-Disk-HOWTO, available from
> -	  <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
> -	  CD-ROMs.
> +	  Say Y if you want to use harddisks and similar block-oriented devices
> +	  via SCSI or via drivers which use SCSI command sets (e.g. the Serial
> +	  and Parallel ATA kernel subsystem, USB, and more).
>  
>  	  To compile this driver as a module, choose M here and read
>  	  <file:Documentation/scsi/scsi.txt>.
>  	  The module will be called sd_mod.
>  
> -	  Do not compile this driver as a module if your root file system
> -	  (the one containing the directory /) is located on a SCSI disk.
> -	  In this case, do not compile the driver for your SCSI host adapter
> -	  (below) as a module either.
> +	  If your root file system (the one containing the directory /) is
> +	  located on a disk which accessed via this driver, choose Y instead of
> +	  M or set up a suitable initrd.
>  
>  config CHR_DEV_ST
> -	tristate "SCSI tape support"
> +	tristate "Tape drives"
>  	depends on SCSI
>  	---help---
>  	  If you want to use a SCSI tape drive under Linux, say Y and read the
> @@ -95,7 +98,7 @@ config CHR_DEV_ST
>  	  <file:Documentation/scsi/scsi.txt>. The module will be called st.
>  
>  config CHR_DEV_OSST
> -	tristate "SCSI OnStream SC-x0 tape support"
> +	tristate "SCSI OnStream SC-x0 tape drives"
>  	depends on SCSI
>  	---help---
>  	  The OnStream SC-x0 SCSI tape drives cannot be driven by the
> @@ -117,13 +120,13 @@ config CHR_DEV_OSST
>  	  <file:Documentation/scsi/scsi.txt>. The module will be called osst.
>  
>  config BLK_DEV_SR
> -	tristate "SCSI CDROM support"
> +	tristate "CD-ROMs, DVD-ROMs"
>  	depends on SCSI
>  	---help---
> -	  If you want to use a SCSI or FireWire CD-ROM under Linux,
> -	  say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
> -	  <http://www.tldp.org/docs.html#howto>. Also make sure to say
> -	  Y or M to "ISO 9660 CD-ROM file system support" later.
> +	  Say Y if you want to use CD-ROMs or DVD-ROMs via SCSI or via drivers
> +	  which use SCSI command sets (e.g. the Serial and Parallel ATA kernel
> +	  subsystem, USB, and more). Also make sure to say Y or M to "ISO 9660
> +	  CD-ROM file system support" later.
>  
>  	  To compile this driver as a module, choose M here and read
>  	  <file:Documentation/scsi/scsi.txt>.
> @@ -164,7 +167,7 @@ config CHR_DEV_SG
>  	  If unsure, say N.
>  
>  config CHR_DEV_SCH
> -	tristate "SCSI media changer support"
> +	tristate "SCSI media changers"
>  	depends on SCSI
>  	---help---
>  	  This is a driver for SCSI media changers.  Most common devices are

Looks great.  I like it.

--
Len Sorensen

[PATCH update] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[Stefan Richter]

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---

And one more update:
There is SAS too, and I forgot 'is' in "on a disk which __ accessed via".

 drivers/scsi/Kconfig |   67 ++++++++++++++++++++++---------------------
 1 file changed, 35 insertions(+), 32 deletions(-)

Index: linux-2.6.23-rc6/drivers/scsi/Kconfig
===================================================================
--- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig
+++ linux-2.6.23-rc6/drivers/scsi/Kconfig
@@ -12,23 +12,31 @@ config SCSI
 	depends on BLOCK
 	select SCSI_DMA if HAS_DMA
 	---help---
-	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
-	  any other SCSI device under Linux, say Y and make sure that you know
-	  the name of your SCSI host adapter (the card inside your computer
-	  that "speaks" the SCSI protocol, also called SCSI controller),
-	  because you will be asked for it.
-
-	  You also need to say Y here if you have a device which speaks
-	  the SCSI protocol.  Examples of this include the parallel port
-	  version of the IOMEGA ZIP drive, USB storage devices, Fibre
-	  Channel, FireWire storage and the IDE-SCSI emulation driver.
+	  This option enables core support for SCSI protocols.
+	  You need it
+	  - for classic parallel SCSI hardware,
+	  - for newer SCSI transports such as Fibre Channel, FireWire storage,
+	    SAS, or iSCSI,
+	  - for non-SCSI hardware which speaks SCSI protocols, such as USB
+	    storage devices or the parallel port version of Iomega Zip drive,
+	  - for non-SCSI hardware whose drivers translate from and to SCSI
+	    protocols, most notably all Serial ATA drivers, and Parallel ATA
+	    via the ATA configuration option.
 
 	  To compile this driver as a module, choose M here and read
 	  <file:Documentation/scsi/scsi.txt>.
 	  The module will be called scsi_mod.
 
 	  However, do not compile this as a module if your root file system
-	  (the one containing the directory /) is located on a SCSI device.
+	  (the one containing the directory /) is located on a SCSI device
+	  or on a device whose driver represents it as SCSI device, as
+	  indicated above.  Choose Y in this case, or set up an initrd.
+
+	  Subsequent options in this menu enable specific SCSI command set
+	  support for harddisks, CD/DVD-ROM/R/W, tapes etc..  This menu also
+	  presents options for specific SCSI controllers, while options for
+	  some other SCSI transports and all non-SCSI controllers are located
+	  in other menus (SATA, USB, FireWire etc.).
 
 config SCSI_DMA
 	bool
@@ -57,32 +65,27 @@ config SCSI_PROC_FS
 
 	  If unsure say Y.
 
-comment "SCSI support type (disk, tape, CD-ROM)"
+comment "SCSI command set drivers (disk, tape, CD-ROM)"
 	depends on SCSI
 
 config BLK_DEV_SD
-	tristate "SCSI disk support"
+	tristate "Harddisks and other Direct access devices"
 	depends on SCSI
 	---help---
-	  If you want to use SCSI hard disks, Fibre Channel disks,
-	  Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
-	  USB storage or the SCSI or parallel port version of
-	  the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
-	  the Disk-HOWTO and the Multi-Disk-HOWTO, available from
-	  <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
-	  CD-ROMs.
+	  Say Y if you want to use harddisks and similar block-oriented devices
+	  via SCSI or via drivers which use SCSI command sets (e.g. the Serial
+	  and Parallel ATA kernel subsystem, USB, and more).
 
 	  To compile this driver as a module, choose M here and read
 	  <file:Documentation/scsi/scsi.txt>.
 	  The module will be called sd_mod.
 
-	  Do not compile this driver as a module if your root file system
-	  (the one containing the directory /) is located on a SCSI disk.
-	  In this case, do not compile the driver for your SCSI host adapter
-	  (below) as a module either.
+	  If your root file system (the one containing the directory /) is
+	  located on a disk which is accessed via this driver, choose Y rather
+	  than M or set up a suitable initrd.
 
 config CHR_DEV_ST
-	tristate "SCSI tape support"
+	tristate "Tape drives"
 	depends on SCSI
 	---help---
 	  If you want to use a SCSI tape drive under Linux, say Y and read the
@@ -95,7 +98,7 @@ config CHR_DEV_ST
 	  <file:Documentation/scsi/scsi.txt>. The module will be called st.
 
 config CHR_DEV_OSST
-	tristate "SCSI OnStream SC-x0 tape support"
+	tristate "SCSI OnStream SC-x0 tape drives"
 	depends on SCSI
 	---help---
 	  The OnStream SC-x0 SCSI tape drives cannot be driven by the
@@ -117,13 +120,13 @@ config CHR_DEV_OSST
 	  <file:Documentation/scsi/scsi.txt>. The module will be called osst.
 
 config BLK_DEV_SR
-	tristate "SCSI CDROM support"
+	tristate "CD-ROMs, DVD-ROMs"
 	depends on SCSI
 	---help---
-	  If you want to use a SCSI or FireWire CD-ROM under Linux,
-	  say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
-	  <http://www.tldp.org/docs.html#howto>. Also make sure to say
-	  Y or M to "ISO 9660 CD-ROM file system support" later.
+	  Say Y if you want to use CD-ROMs or DVD-ROMs via SCSI or via drivers
+	  which use SCSI command sets (e.g. the Serial and Parallel ATA kernel
+	  subsystem, USB, and more). Also make sure to say Y or M to "ISO 9660
+	  CD-ROM file system support" later.
 
 	  To compile this driver as a module, choose M here and read
 	  <file:Documentation/scsi/scsi.txt>.
@@ -164,7 +167,7 @@ config CHR_DEV_SG
 	  If unsure, say N.
 
 config CHR_DEV_SCH
-	tristate "SCSI media changer support"
+	tristate "SCSI media changers"
 	depends on SCSI
 	---help---
 	  This is a driver for SCSI media changers.  Most common devices are

-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

Re: [PATCH update] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[FUJITA Tomonori]

On Fri, 14 Sep 2007 23:14:21 +0200 (CEST)
Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:

> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
> ---
> 
> And one more update:
> There is SAS too, and I forgot 'is' in "on a disk which __ accessed via".
> 
>  drivers/scsi/Kconfig |   67 ++++++++++++++++++++++---------------------
>  1 file changed, 35 insertions(+), 32 deletions(-)
> 
> Index: linux-2.6.23-rc6/drivers/scsi/Kconfig
> ===================================================================
> --- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig
> +++ linux-2.6.23-rc6/drivers/scsi/Kconfig
> @@ -12,23 +12,31 @@ config SCSI
>  	depends on BLOCK
>  	select SCSI_DMA if HAS_DMA
>  	---help---
> -	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
> -	  any other SCSI device under Linux, say Y and make sure that you know
> -	  the name of your SCSI host adapter (the card inside your computer
> -	  that "speaks" the SCSI protocol, also called SCSI controller),
> -	  because you will be asked for it.
> -
> -	  You also need to say Y here if you have a device which speaks
> -	  the SCSI protocol.  Examples of this include the parallel port
> -	  version of the IOMEGA ZIP drive, USB storage devices, Fibre
> -	  Channel, FireWire storage and the IDE-SCSI emulation driver.
> +	  This option enables core support for SCSI protocols.
> +	  You need it
> +	  - for classic parallel SCSI hardware,
> +	  - for newer SCSI transports such as Fibre Channel, FireWire storage,
> +	    SAS, or iSCSI,

There is SRP too.

Re: [PATCH update] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[Stefan Richter]

FUJITA Tomonori wrote:
> On Fri, 14 Sep 2007 23:14:21 +0200 (CEST)
> Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
...
>> And one more update:
>> There is SAS too,
...
>> +	  You need it
>> +	  - for classic parallel SCSI hardware,
>> +	  - for newer SCSI transports such as Fibre Channel, FireWire storage,
>> +	    SAS, or iSCSI,
> 
> There is SRP too.

I think I'll rewrite it as "for newer SCSI transports such as FireWire
storage."  ;-)

If SRP was in, can 'such as' be omitted?  "for newer SCSI transports
(Fibre Channel, FireWire storage, iSCSI, SAS, SRP),"  Or would be "for
newer SCSI transports such as Fibre Channel, FireWire storage, iSCSI,
SAS, and more," be OK?
-- 
Stefan Richter
-=====-=-=== =--= -====
http://arcgraph.de/sr/

Re: [PATCH update] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[FUJITA Tomonori]

On Sat, 15 Sep 2007 08:16:03 +0200
Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:

> FUJITA Tomonori wrote:
> > On Fri, 14 Sep 2007 23:14:21 +0200 (CEST)
> > Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> ...
> >> And one more update:
> >> There is SAS too,
> ...
> >> +	  You need it
> >> +	  - for classic parallel SCSI hardware,
> >> +	  - for newer SCSI transports such as Fibre Channel, FireWire storage,
> >> +	    SAS, or iSCSI,
> > 
> > There is SRP too.
> 
> I think I'll rewrite it as "for newer SCSI transports such as FireWire
> storage."  ;-)
> 
> If SRP was in, can 'such as' be omitted?  "for newer SCSI transports
> (Fibre Channel, FireWire storage, iSCSI, SAS, SRP),"

It might be necessary to add SSA too.


> Or would be "for newer SCSI transports such as Fibre Channel,
> FireWire storage, iSCSI, SAS, and more," be OK?

scsi-ml has SPI, FC, iSCSI, SAS, and SRP transport classes (SRP is in
scsi-misc now). It's a bit strange to omit only SRP, I think. But I
might be too SRP-biased.

Re: [PATCH update] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[Stefan Richter]

FUJITA Tomonori wrote:
> On Sat, 15 Sep 2007 08:16:03 +0200
> Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>> Or would be "for newer SCSI transports such as Fibre Channel,
>> FireWire storage, iSCSI, SAS, and more," be OK?
> 
> scsi-ml has SPI, FC, iSCSI, SAS, and SRP transport classes (SRP is in
> scsi-misc now). It's a bit strange to omit only SRP, I think. But I
> might be too SRP-biased.

"such as... and more" suggests that there are indeed more SCSI
transports supported by Linux than mentioned in this help text.

We could also write "such as Fibre Channel, iSCSI, SAS, and more," if
you suspect bias on my side. ;-)  Help texts should be concise.
-- 
Stefan Richter
-=====-=-=== =--= -====
http://arcgraph.de/sr/

Re: [PATCH update] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[FUJITA Tomonori]

On Sat, 15 Sep 2007 14:30:10 +0200
Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:

> FUJITA Tomonori wrote:
> > On Sat, 15 Sep 2007 08:16:03 +0200
> > Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> >> Or would be "for newer SCSI transports such as Fibre Channel,
> >> FireWire storage, iSCSI, SAS, and more," be OK?
> > 
> > scsi-ml has SPI, FC, iSCSI, SAS, and SRP transport classes (SRP is in
> > scsi-misc now). It's a bit strange to omit only SRP, I think. But I
> > might be too SRP-biased.
> 
> "such as... and more" suggests that there are indeed more SCSI
> transports supported by Linux than mentioned in this help text.

I think that you can remove "such as" if you add SRP and SSA. "for
SCSI transports such as Fibre Channel, FireWire, SAS, iSCSI, SRP, or
SSA" should be fine. But I'm not sure that scsi-ml has a SSA hba
driver. If not, we could remove SSA.


> We could also write "such as Fibre Channel, iSCSI, SAS, and more," if
> you suspect bias on my side. ;-)  Help texts should be concise.
> -- 
> Stefan Richter
> -=====-=-=== =--= -====
> http://arcgraph.de/sr/

Re: [PATCH update] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[Adrian Bunk]

On Fri, Sep 14, 2007 at 11:14:21PM +0200, Stefan Richter wrote:
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
> ---
> 
> And one more update:
> There is SAS too, and I forgot 'is' in "on a disk which __ accessed via".
> 
>  drivers/scsi/Kconfig |   67 ++++++++++++++++++++++---------------------
>  1 file changed, 35 insertions(+), 32 deletions(-)
> 
> Index: linux-2.6.23-rc6/drivers/scsi/Kconfig
> ===================================================================
> --- linux-2.6.23-rc6.orig/drivers/scsi/Kconfig
> +++ linux-2.6.23-rc6/drivers/scsi/Kconfig
> @@ -12,23 +12,31 @@ config SCSI
>  	depends on BLOCK
>  	select SCSI_DMA if HAS_DMA
>  	---help---
> -	  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
> -	  any other SCSI device under Linux, say Y and make sure that you know
> -	  the name of your SCSI host adapter (the card inside your computer
> -	  that "speaks" the SCSI protocol, also called SCSI controller),
> -	  because you will be asked for it.
> -
> -	  You also need to say Y here if you have a device which speaks
> -	  the SCSI protocol.  Examples of this include the parallel port
> -	  version of the IOMEGA ZIP drive, USB storage devices, Fibre
> -	  Channel, FireWire storage and the IDE-SCSI emulation driver.
> +	  This option enables core support for SCSI protocols.
> +	  You need it
> +	  - for classic parallel SCSI hardware,
> +	  - for newer SCSI transports such as Fibre Channel, FireWire storage,
> +	    SAS, or iSCSI,
> +	  - for non-SCSI hardware which speaks SCSI protocols, such as USB
> +	    storage devices or the parallel port version of Iomega Zip drive,


but not for CONFIG_BLK_DEV_UB


> +	  - for non-SCSI hardware whose drivers translate from and to SCSI
> +	    protocols, most notably all Serial ATA drivers, and Parallel ATA
> +	    via the ATA configuration option.


but not for CONFIG_BLK_DEV_IDE_SATA


>  	  To compile this driver as a module, choose M here and read
>  	  <file:Documentation/scsi/scsi.txt>.
>  	  The module will be called scsi_mod.
>  
>  	  However, do not compile this as a module if your root file system
> -	  (the one containing the directory /) is located on a SCSI device.
> +	  (the one containing the directory /) is located on a SCSI device
> +	  or on a device whose driver represents it as SCSI device, as
> +	  indicated above.  Choose Y in this case, or set up an initrd.
> +
> +	  Subsequent options in this menu enable specific SCSI command set
> +	  support for harddisks, CD/DVD-ROM/R/W, tapes etc..  This menu also
> +	  presents options for specific SCSI controllers, while options for
> +	  some other SCSI transports and all non-SCSI controllers are located
> +	  in other menus (SATA, USB, FireWire etc.).
>...


You expect all kconfig users to read and completely understand this?

Although it's no longer required that the user sees the CONFIG_SCSI 
option at all since we can determine automaically when it's required
and when not?


> Stefan Richter

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: [PATCH update] SCSI: update Kconfig help text to indicate SCSI core's widespread usage

[Stefan Richter]

Adrian Bunk wrote:
> On Fri, Sep 14, 2007 at 11:14:21PM +0200, Stefan Richter wrote:
>> +	  You need it
>> +	  - for classic parallel SCSI hardware,
>> +	  - for newer SCSI transports such as Fibre Channel, FireWire storage,
>> +	    SAS, or iSCSI,
>> +	  - for non-SCSI hardware which speaks SCSI protocols, such as USB
>> +	    storage devices or the parallel port version of Iomega Zip drive,
> 
> 
> but not for CONFIG_BLK_DEV_UB
> 
> 
>> +	  - for non-SCSI hardware whose drivers translate from and to SCSI
>> +	    protocols, most notably all Serial ATA drivers, and Parallel ATA
>> +	    via the ATA configuration option.
> 
> 
> but not for CONFIG_BLK_DEV_IDE_SATA

Well, one could add a

	You don't need it
	- for x,
	- for y.

bullet list.

...
> You expect all kconfig users to read and completely understand this?

I occasionally write documentation without the expectation that every
potential user will read and understand it.

> Although it's no longer required that the user sees the CONFIG_SCSI 
> option at all since we can determine automaically when it's required
> and when not?

Maybe you can hide CONFIG_SCSI, but you still need to provide the above
information --- then under the sd, sr, st, sg options, which may
actually be the better places although it increases redundancy.
-- 
Stefan Richter
-=====-=-=== =--= -====
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Adrian Bunk]

On Fri, Sep 14, 2007 at 05:37:37PM +0200, Stefan Richter wrote:
> Adrian Bunk wrote:
> > On Fri, Sep 14, 2007 at 04:54:07PM +0200, Stefan Richter wrote:
> >> The patch which is discussed here is specifically targeted towards users
> >> who are convinced that they can migrate to different drivers without
> >> reading Kconfig help texts.
> > 
> > Nothing about the patch is only about migration.
> > 
> > The same applies if you configure a kernel from scratch.
> > 
> > Do "make menuconfig" with the .config you are normally using, count the 
> > number of options that are visible, and ask yourself whether we can 
> > really expect users to read the help texts for every single option shown.
> > 
> > People mostly read help texts for options where they don't understand 
> > what this option is about - and "Serial ATA" therefore is an option that 
> > is likely to get enabled without the user looking at the help text.
> 
> If you create .config from scratch, then you can get away without
> reading help texts if you have a target with minimal hardware and
> protocols requirements and you know all the subsystems involved.
> 
> In all other cases, you theoretically need to read all help texts (minus
> the ones that don't appear because you deselect entire subsystems).  In
> practice, this takes too much time, hence you take an existing .config
> (yours or somebody else's) and go from there.

Kconfig let's you start with the defconfig when doing "make menuconfig" 
without any .config present, so in practice users start from the 
defconfig and then go through all menus at once enabling and disabling 
options to adapt the configurations to their needs.

Or they start from the "includes everything" .config of their 
distribution and remove everything they don't need.

> Whenever one enables an option for the first time, it would IMO be
> foolish to ignore its help text.

Then the number of non-foolish users is quite near to 0...

If you expect people to read several hundreds or thousands of help texts 
only for configuring a kernel then you are expecting something that is 
simply not realistic.

It is intuitive for a user to enable the "Serial ATA" menu and he might 
not expect to have to read the help text when he has SATA drivers, while 
having to enable anything in the "SCSI device support" menu is highly 
unintuitively when the user does not have SCSI hardware.

> Stefan Richter

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

Adrian Bunk wrote:
> On Fri, Sep 14, 2007 at 05:37:37PM +0200, Stefan Richter wrote:
>> In
>> practice, this takes too much time, hence you take an existing .config
>> (yours or somebody else's) and go from there.
> 
> Kconfig let's you start with the defconfig when doing "make menuconfig" 
> without any .config present,
[...]

This is one of those "somebody else's .config".

>> Whenever one enables an option for the first time, it would IMO be
>> foolish to ignore its help text.
> 
> Then the number of non-foolish users is quite near to 0...

Perhaps.  Although I meant only options which one enables oneself, not
options which are taken over from somebody else's .config.

> If you expect people to read several hundreds or thousands of help texts 
> only for configuring a kernel then you are expecting something that is 
> simply not realistic.
> 
> It is intuitive for a user to enable the "Serial ATA" menu and he might 
> not expect to have to read the help text when he has SATA drivers, while 
> having to enable anything in the "SCSI device support" menu is highly 
> unintuitively when the user does not have SCSI hardware.

It surely is unintuitive, and it is one of the worse cases where the
current menu layout is unintuitive.  We have to improve that, even
though it is ultimately impossible to serve everyone's needs equally
well or, generally, make kernel configuration a piece of cake.

Note though, some suggestions which came up here don't actually make the
menus more intuitive.  Notably the patch "Select BLK_DEV_SD for all
SCSI/libata drivers" is counterintuitive in a different color:  It
follows the philosophy of "I know what's good for you and I act on your
behalf behind your back --- trust me, it's for your best".

I too am guilty of proposing the usage of 'select'
(http://lkml.org/lkml/2007/9/8/9) but I suggested a variant which lets
the user stay informed and in control (as far as this is possible with
'select' which always increases complexity, never reduces it).

But rather than adding multiple menu items which enable the same option,
a reorganization of the menus which better reflect the role of SCSI core
and SCSI highlevel might be more effective --- similar to "Networking"
which is separate from "Network device support"
(http://lkml.org/lkml/2007/9/10/5, http://lkml.org/lkml/2007/9/10/115).
-- 
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Paul Rolland]

Hello,

On Fri, 14 Sep 2007 17:15:22 +0200
Adrian Bunk <bunk@kernel.org> wrote:

> On Fri, Sep 14, 2007 at 04:54:07PM +0200, Stefan Richter wrote:
> > Adrian Bunk wrote:
> > > On Sun, Sep 09, 2007 at 05:11:44PM -0400, Jeff Garzik wrote:
> > >> Let's step back a moment and consider the actual scale and impact of
> > >> the problem at hand.
> Do "make menuconfig" with the .config you are normally using, count the 
> number of options that are visible, and ask yourself whether we can 
> really expect users to read the help texts for every single option shown.
> 
> People mostly read help texts for options where they don't understand 
> what this option is about - and "Serial ATA" therefore is an option that 
> is likely to get enabled without the user looking at the help text.
> 

As a "make menuconfig" user, let me say that I agree. Of course, I'm used
to rebuild kernel, but sometimes, some options are not clear, and the help
text is searched for. But, getting too much of "No help text available"
usually results in people no more reading the help text.

What about splitting the screen to have the top half with the menu, and the
bottom half with the help ?

Paul


-- 
Paul Rolland                                E-Mail : rol(at)witbe.net
Witbe.net SA                                Tel. +33 (0)1 47 67 77 77
Les Collines de l'Arche                     Fax. +33 (0)1 47 67 77 99
F-92057 Paris La Defense                    RIPE : PR12-RIPE

Please no HTML, I'm not a browser - Pas d'HTML, je ne suis pas un navigateur 
"Some people dream of success... while others wake up and work hard at it" 

"I worry about my child and the Internet all the time, even though she's too 
young to have logged on yet. Here's what I worry about. I worry that 10 or 15 
years from now, she will come to me and say 'Daddy, where were you when they 
took freedom of the press away from the Internet?'"
--Mike Godwin, Electronic Frontier Foundation 

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

Paul Rolland wrote:
> getting too much of "No help text available"
> usually results in people no more reading the help text.

I assert that a Kconfig prompt (a visible Kconfig variable) _without_
help text is a bug.
-- 
Stefan Richter
-=====-=-=== =--= -====
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Paul Rolland]

Hello Stefan,

On Sat, 15 Sep 2007 10:25:39 +0200
Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:

> Paul Rolland wrote:
> > getting too much of "No help text available"
> > usually results in people no more reading the help text.
> 
> I assert that a Kconfig prompt (a visible Kconfig variable) _without_
> help text is a bug.

Here is an example from 2.6.34-rc6 :
 .config - Linux Kernel v2.6.23-rc6 Configuration
------------------------------------------------------------------------------
 +------------------------- Provide RTC interrupt -------------------------+ 
 | There is no help available for this kernel option.                      |
 | Symbol: HPET_EMULATE_RTC [=y]                                           |
 | Prompt: Provide RTC interrupt                                           |
 |   Defined at arch/x86_64/Kconfig:471                                    |
 |   Depends on: HPET_TIMER && RTC=y                                       |
 |   Location:                                                             |
 |   -> Processor type and features |   

Regards,
Paul

x86_64 usability bug: Kconfig prompt without help text (was Re: sata & scsi suggestion for make menuconfig)

[Stefan Richter]

I take the liberty to modify the CC list.

Paul Rolland wrote:
> Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>> I assert that a Kconfig prompt (a visible Kconfig variable) _without_
>> help text is a bug.
> 
> Here is an example from 2.6.34-rc6 :
>  .config - Linux Kernel v2.6.23-rc6 Configuration
> ------------------------------------------------------------------------------
>  +------------------------- Provide RTC interrupt -------------------------+ 
>  | There is no help available for this kernel option.                      |
>  | Symbol: HPET_EMULATE_RTC [=y]                                           |
>  | Prompt: Provide RTC interrupt                                           |
>  |   Defined at arch/x86_64/Kconfig:471                                    |
>  |   Depends on: HPET_TIMER && RTC=y                                       |
>  |   Location:                                                             |
>  |   -> Processor type and features |   

The same prompt existed in arch/i386/Kconfig without help text too but
it was later made invisible and automatic by pre-2.6.13 patch "remove
special HPET_EMULATE_RTC config option", commit
c91096d85c95c6b7fe8d7065e2aa6825e0bdaca9: "We had a user whose apps
weren't working correctly because his "rtc" wasn't working fully.  For
the sake of simplicity, it seems sensible to always enable HPET RTC
emulation."

  - So, which criteria influence whether HPET_EMULATE_RTC should be
    enabled on x86_64 or not?

  - In case that there is no compelling reason to disable it if its
    dependencies are satisfied, shouldn't it rather be invisible and
    automatic like on i386?
-- 
Stefan Richter
-=====-=-=== =--= -====
http://arcgraph.de/sr/

Re: x86_64 usability bug: Kconfig prompt without help text (was Re: sata & scsi suggestion for make menuconfig)

[Andi Kleen]

>   - So, which criteria influence whether HPET_EMULATE_RTC should be
>     enabled on x86_64 or not?

If there is one it needs to be a runtime switch anyways.
> 
>   - In case that there is no compelling reason to disable it if its
>     dependencies are satisfied, shouldn't it rather be invisible and
>     automatic like on i386?

It should be automatic. Please send a patch.

-Andi

[PATCH] x86_64: configure HPET_EMULATE_RTC automatically

[Stefan Richter]

I don't know exactly what this option does...
Andi says it should be automatic rather than exposed as a prompt.

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---

--- linux.orig/arch/x86_64/Kconfig
+++ linux/arch/x86_64/Kconfig
@@ -469,8 +469,9 @@ config HPET_TIMER
 	  <http://www.intel.com/hardwaredesign/hpetspec.htm>.
 
 config HPET_EMULATE_RTC
-	bool "Provide RTC interrupt"
+	bool
 	depends on HPET_TIMER && RTC=y
+	default y
 
 # Mark as embedded because too many people got it wrong.
 # The code disables itself when not needed.

-- 
Stefan Richter
-=====-=-=== =--= -====
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[david]

On Sat, 15 Sep 2007, Paul Rolland wrote:

> On Fri, 14 Sep 2007 17:15:22 +0200
> Adrian Bunk <bunk@kernel.org> wrote:
>
>> On Fri, Sep 14, 2007 at 04:54:07PM +0200, Stefan Richter wrote:
>>> Adrian Bunk wrote:
>>>> On Sun, Sep 09, 2007 at 05:11:44PM -0400, Jeff Garzik wrote:
>>>>> Let's step back a moment and consider the actual scale and impact of
>>>>> the problem at hand.
>> Do "make menuconfig" with the .config you are normally using, count the
>> number of options that are visible, and ask yourself whether we can
>> really expect users to read the help texts for every single option shown.
>>
>> People mostly read help texts for options where they don't understand
>> what this option is about - and "Serial ATA" therefore is an option that
>> is likely to get enabled without the user looking at the help text.
>>
>
> As a "make menuconfig" user, let me say that I agree. Of course, I'm used
> to rebuild kernel, but sometimes, some options are not clear, and the help
> text is searched for. But, getting too much of "No help text available"
> usually results in people no more reading the help text.
>
> What about splitting the screen to have the top half with the menu, and the
> bottom half with the help ?

I useually have more screen space available to the side then above and 
below the list of options.

David Lang

Re: sata & scsi suggestion for make menuconfig

[Al Boldi]

Krzysztof Halasa wrote:
>> Ok, but that's not the most common situaties. What I'm suggesting is a
>> warning or a please note popup. Not neccessarily an error or refusing to
>> continue thing.
>
>What IMHO makes sense is changing all references to SCSI CDROM,
>SCSI DISK etc. to just CDROM, DISK, and changing SCSI (menu) to
>something like MASS STORAGE.

I once sent a patch to make libata a submenu of scsi.

[PATCH] libata Kconfig: Allow libata to be selected from within the SCSI submenu
From: Al Boldi <a1426z@gawab.com>
To: linux-ide@vger.kernel.org
CC: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Date: 08/01/07 07:22 am

Move libata Kconfig sourcing from the drivers Kconfig into the SCSI Kconfig.

This allows the user to quickly select additional disk/tape/cdrom support 
from within the same menu.

Signed-off-by: Al Boldi <a1426z@gawab.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
---
--- a/drivers/Kconfig   2007-05-02 17:25:30.000000000 +0300
+++ b/drivers/Kconfig   2007-08-01 06:33:13.000000000 +0300
@@ -22,8 +22,6 @@ source "drivers/ide/Kconfig"
 
 source "drivers/scsi/Kconfig"
 
-source "drivers/ata/Kconfig"
-
 source "drivers/cdrom/Kconfig"
 
 source "drivers/md/Kconfig"
--- a/drivers/scsi/Kconfig      2007-07-09 06:38:37.000000000 +0300
+++ b/drivers/scsi/Kconfig      2007-08-01 06:46:42.000000000 +0300
@@ -7,6 +7,8 @@ config RAID_ATTRS
        ---help---
          Provides RAID
 
+source "drivers/ata/Kconfig"
+
 config SCSI
        tristate "SCSI device support"
        depends on BLOCK



Thanks!

--
Al

Re: sata & scsi suggestion for make menuconfig

[Alan Cox]

> I once sent a patch to make libata a submenu of scsi.

Which is wrong

Nakked-by: Alan Cox <alan@redhat.com>

The general comments about moving this stuff around and making it clearer
what sd/sr etc are nowdays are good but hiding libata under SCSI will
cause even more confusion than it cures

Re: sata & scsi suggestion for make menuconfig

[Al Boldi]

Alan Cox wrote:
> > I once sent a patch to make libata a submenu of scsi.
>
> Which is wrong
>
> Nakked-by: Alan Cox <alan@redhat.com>
>
> The general comments about moving this stuff around and making it clearer
> what sd/sr etc are nowdays are good but hiding libata under SCSI will
> cause even more confusion than it cures

That's easy to fix:  just change the SCSI heading to include a libata hint.

Something like this:

[PATCH] libata Kconfig: Allow libata to be selected from within the SCSI submenu

Move libata Kconfig sourcing from the drivers Kconfig into the SCSI Kconfig,
and change the SCSI menu heading to indicate libata submenu inclusion.

This allows the user to quickly select additional disk/tape/cdrom support 
from within the same menu.

Signed-off-by: Al Boldi <a1426z@gawab.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
---
--- a/drivers/Kconfig   2007-05-02 17:25:30.000000000 +0300
+++ b/drivers/Kconfig   2007-08-01 06:33:13.000000000 +0300
@@ -22,8 +22,6 @@ source "drivers/ide/Kconfig"
 
 source "drivers/scsi/Kconfig"
 
-source "drivers/ata/Kconfig"
-
 source "drivers/cdrom/Kconfig"
 
 source "drivers/md/Kconfig"
--- a/drivers/scsi/Kconfig      2007-07-09 06:38:37.000000000 +0300
+++ b/drivers/scsi/Kconfig      2007-08-01 06:46:42.000000000 +0300
@@ -7,6 +7,8 @@ config RAID_ATTRS
        ---help---
          Provides RAID
 
+source "drivers/ata/Kconfig"
+
 config SCSI
-       tristate "SCSI device support"
+       tristate "SCSI and Libata device support"
        depends on BLOCK



Thanks!

--
Al

Re: sata & scsi suggestion for make menuconfig

[Jan Engelhardt]

On Sep 8 2007 17:03, Al Boldi wrote:
>Alan Cox wrote:
>> > I once sent a patch to make libata a submenu of scsi.
>>
>> Which is wrong
>>
>> Nakked-by: Alan Cox <alan@redhat.com>
>>
>> The general comments about moving this stuff around and making it clearer
>> what sd/sr etc are nowdays are good but hiding libata under SCSI will
>> cause even more confusion than it cures
>
>That's easy to fix:  just change the SCSI heading to include a libata hint.

Let's not. I am perfectly fine with how things currently are, plus optionally
Stefan Richter's suggestion.


	Jan
-- 

Re: sata & scsi suggestion for make menuconfig

[Al Boldi]

Al Boldi wrote:
> Alan Cox wrote:
> > > I once sent a patch to make libata a submenu of scsi.
> >
> > Which is wrong
> >
> > Nakked-by: Alan Cox <alan@redhat.com>
> >
> > The general comments about moving this stuff around and making it
> > clearer what sd/sr etc are nowdays are good but hiding libata under SCSI
> > will cause even more confusion than it cures
>
> That's easy to fix:  just change the SCSI heading to include a libata
> hint.
>
> Something like this:
>
> [PATCH] libata Kconfig: Allow libata to be selected from within the SCSI
> submenu
>
> Move libata Kconfig sourcing from the drivers Kconfig into the SCSI
> Kconfig, and change the SCSI menu heading to indicate libata submenu
> inclusion.
>
> This allows the user to quickly select additional disk/tape/cdrom support
> from within the same menu.
>
> Signed-off-by: Al Boldi <a1426z@gawab.com>
> Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
> ---
> --- a/drivers/Kconfig   2007-05-02 17:25:30.000000000 +0300
> +++ b/drivers/Kconfig   2007-08-01 06:33:13.000000000 +0300
> @@ -22,8 +22,6 @@ source "drivers/ide/Kconfig"
>
>  source "drivers/scsi/Kconfig"
>
> -source "drivers/ata/Kconfig"
> -
>  source "drivers/cdrom/Kconfig"
>
>  source "drivers/md/Kconfig"
> --- a/drivers/scsi/Kconfig      2007-07-09 06:38:37.000000000 +0300
> +++ b/drivers/scsi/Kconfig      2007-08-01 06:46:42.000000000 +0300
> @@ -7,6 +7,8 @@ config RAID_ATTRS
>         ---help---
>           Provides RAID
>
> +source "drivers/ata/Kconfig"
> +
>  config SCSI
> -       tristate "SCSI device support"
> +       tristate "SCSI and Libata device support"
>         depends on BLOCK

Actually, this should have read:

--- a/drivers/scsi/Kconfig	2007-07-09 06:38:37.000000000 +0300
+++ a/drivers/scsi/Kconfig	2007-09-09 06:48:11.000000000 +0300
@@ -1,4 +1,4 @@
-menu "SCSI device support"
+menu "SCSI and Libata (SATA/PATA/new IDE) device support"
 
 config RAID_ATTRS
        tristate "RAID Transport Class"
@@ -7,6 +7,8 @@ config RAID_ATTRS
        ---help---
          Provides RAID
 
+source "drivers/ata/Kconfig"
+
 config SCSI
        tristate "SCSI device support"
        depends on BLOCK


I would think that with this minimal change it would make it crystal clear, 
to anybody who can read, where to enable libata support, and at the same 
time not to forget/overlook sd/sr selection.


Thanks!

--
Al

Re: sata & scsi suggestion for make menuconfig

[Bodo Eggert]

Al Boldi <a1426z@gawab.com> wrote:
> Alan Cox wrote:

>> > I once sent a patch to make libata a submenu of scsi.
>>
>> Which is wrong
>>
>> Nakked-by: Alan Cox <alan@redhat.com>
>>
>> The general comments about moving this stuff around and making it clearer
>> what sd/sr etc are nowdays are good but hiding libata under SCSI will
>> cause even more confusion than it cures
> 
> That's easy to fix:  just change the SCSI heading to include a libata hint.

I think you're fixing the wrong problem.

The real problem is hiding devices attached to some controlers between
one kind of the controllers. This has been correct whern they were bus-
specific, but since they are now shared by three busses, they should get
their own menu called "(S)ATA/USB/SCSI attached devices" - or whatever a
native speaker would suggest.

Besides that, if I imagine being a semi-novice and searching for IDE
support, I would have a hard time finding the IDE menu, and asuming
PATA to be non-experimental one day, I'd have a hard time deciding
which of the drivers to use. Maybe the SATA-drivers should be put
above the old PATA menu, amd maybe both of the titles should include
"(E)IDE"?

BTW: For CONFIG_ATA, you can replace
"(!M32R && !M68K || BROKEN) && (!SUN4 || BROKEN)"
with "(!M32R && !M68K && !SUN4 || BROKEN)"

BTW2: I think that menu needs very much reordering. "Block devices" should
be renamed to "Other block devices", AGP support should belong into graphics
support, and many other things I don't even know need to be pushed around.
Even ordering by name would be better than the current situation! But it
should be done by someone knowing these devices, I could only do a part.
-- 
Top 100 things you don't want the sysadmin to say:
14. Any more trouble from you and your account gets moved to the 750

Friß, Spammer: NxeCk-fw6@5.7eggert.dyndns.org

Re: sata & scsi suggestion for make menuconfig

[Stefan Richter]

Bodo Eggert wrote:
> The real problem is hiding devices attached to some controlers between
> one kind of the controllers. This has been correct whern they were bus-
> specific, but since they are now shared by three busses, they should get
> their own menu called "(S)ATA/USB/SCSI attached devices" - or whatever a
> native speaker would suggest.

A side note:  SCSI is not a bus.  It is an architecture and a set of
implementation standards; including command set standards, transport
protocol standards and interconnect standards for a whole lot of
different applications, transports, and interconnects, and not all of
the latter are actual buses.  The oldest of SCSI interconnects, SCSI
Parallel Interconnect alias SPI, is often mistaken for all of SCSI even
though its role is diminishing.  There is much more:
http://www.t10.org/scsi-3.htm

You are right though that Linux' SCSI command set drivers and SCSI core
are used for non-SCSI transports too, and this is not very well
reflected by the configuration menu layout.  (But is there an ideal menu
layout?  I'm sure there isn't.)
-- 
Stefan Richter
-=====-=-=== =--= -=---
http://arcgraph.de/sr/

Re: sata & scsi suggestion for make menuconfig

[Randy Dunlap]

On Sat, 08 Sep 2007 18:52:35 +0200 Bodo Eggert wrote:

> BTW2: I think that menu needs very much reordering. "Block devices" should
> be renamed to "Other block devices", AGP support should belong into graphics
> support, and many other things I don't even know need to be pushed around.
> Even ordering by name would be better than the current situation! But it
> should be done by someone knowing these devices, I could only do a part.

how's this?

for 2.6.16-rc4:  consolidated graphics config:
http://marc.info/?l=linux-kernel&m=114101236918589&w=2

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***