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/ - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
