Re: I request inclusion of SAS Transport Layer and AIC-94xx into the kernel

[Luben Tuikov <luben_tuikov@adaptec.com>]

On 10/04/05 11:26, Jeff Garzik wrote:
> You continue to misunderstand everyone else's opinion.

Internet mailing lists are one such thing where anyone
can write anything they want and sound smart.  Like
the statement above.

Did you talk to "everyone else"?  Or is this just you,
James B and Christoph?

How do you know everyone else's opinion?

Maybe because you're telling them what they should think?

> The claim is that the transport class is the method through which a 
> transport layer is plugged into the SCSI stack.  Pluggable transport 

No.  This isn't currently the case.  You're maybe making it now
to be like this, but it is currently not the case.

> classes means that SAS transport layer details go into the SAS transport 
> class (or a helper lib).  SPI (parallel/legacy SCSI) transport layer 
> details should move to the SPI transport class.

"should", "will".

The question is then: Where were you Jeff all this time?

Why did the SAS code had to be posted for SCSI Core to see how many
things it needs to repair.

I've been pointing those things out since, oh well, for many years
now.

> You misunderstood that everybody, but you, has moved on to the "what do 
> we do about this" phase.

If SCSI Core had seen the necessary over the years changes,
it wouldn't be in this situation now.

> Nothing is upside down.  Transport details plug into an obvious location 
> -- the transport class, and associated helper libs (if any).

USB/SAS/SBP:
HW -> LLDD -> Transport Layer -> SCSI Core

MPT:
HW -> Transport Layer (FW) -> LLDD -> SCSI Core.

	Luben


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/