Re: [SAS ANNOUNCEMENT] MPT Fusion driver 3.02.07.02 update

[James Bottomley <James.Bottomley@SteelEye.com>]

On Fri, 2004-11-12 at 17:15, Moore, Eric Dean wrote:
> Highlights for this release:
> 
> In addition to SAS support =>
> 

Actually, before we begin on a SAS implementation, I'd rather like us to
get the architecture and design correct.  Reading all the SAS and SATA
documentation is still on my todo list.  However, this is my brief take
on the architecture:

SAS itself is a bit of a monster because the PHY layer characteristics
are identical to those of SATA.  Therefore, it seems like we need two
separate transport classes, one for the PHY layer which would control
the PHY transport characteristics and would be shareable with SATA and
one for SAS only which would cover a large swath of the SAS specific
ioctls and the useful bits of CMSI.

As far as the controller and expander protocols to which Doug Gilbert
has been referring, I really have no current idea how to do them, but if
anyone else does now would be a good time to say something.

So does the above look like an acceptable way to move forward? (having a
PHY transport class is going to mean changes in both SCSI and SATA and
probably block as well, since this may ultimately not be a SCSI specific
transport class).

James