On Sat, Jul 09, 2005 at 07:06:56PM -0400, Ben Collins wrote: > I can understand that TYPE_RDC is what we had as TYPE_SDAD. Now, in our > tree for TYPE_RDC, we converted it to TYPE_DISK. We also did a lot of mode > conversions for DISK/RDC/ROM types. This isn't correct. RBC is a separate, valid disk type defined by the SCSI T10 committee. It has its own spec. Of course, SBP2 isn't wholly RBC compliant, even though it reports itself as an RBC device. > My question is, why were the conversions all removed? The conversions, as > far as I know, are related to SBP protocol, and not SCSI, so why would the > SCSI maintainers feel the need to rip out an important part of the SBP2 > driver? It's a standard conversion that we've been ripping out of all drivers, because it is unnecessary. I understand you're a bit hacked off by all these changes occurring, but how about debugging the failure you're seeing, before ripping out stuff? "doesn't work at all" is untrue. So who are the failure cases, and what makes them different from the working case(s)? Jeff - : 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
