James Bottomley wrote: > On Wed, 2007-11-07 at 15:37 -0500, Tony Battersby wrote: > >> This patch fixes the sym53c8xx "setflag" user command to control >> disconnect privilege, which has been broken for a long time. >> > > The first observation is that the sym specific setflags interface is > being replaced by the parallel transport specific sysfs interface. > However, as you've probably noticed, the SPI transport has no flag for > disconnect permission, so how important actually is this? If it's > important, then we can put it in scsi_transport_spi ... if not, then we > should probably just eliminate it from sym2. > > James Most people would probably just use the HBA's BIOS utility to configure the NVRAM to disallow disconnects if needed. However, in my case, the HBA is inside an embedded device sold by my company, and customers can attach their own SCSI devices to it. There is one type of SCSI device that we support which doesn't work with disconnect privilege enabled, so my code running in the embedded device needs to be able to enable/disable disconnect privilege dynamically based on whether or not the customer has attached this specific broken device. It would be nice to have a generic way to control it. That would save me the bother of sending my patch to control disconnect privilege for LSI MPT Fusion Ultra320 HBAs via mptctl. ;-) Tony - 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
