Re: [ANNOUNCE] MPT Fusion driver 3.02.06 update

[Jeremy Higdon <jeremy@sgi.com>]

On Tue, Oct 26, 2004 at 06:15:25PM +0100, Christoph Hellwig wrote:
> > > hooks it needs (e.g. the sas device list)
> > > 
> > 
> > We have to ship with these IOCTLS. Are there any compromise?
> > Sounds like you shot down my backup idea; e.g putting this code into 
> > seperate file which isn't provided for inclusion, but can be recompiled 
> > to link into mptctl?  I don't think we time to pursue your the idea of 
> > re-invent everything into the sas-transport layer.
> 
> No way.  This is similar to the hbaapi situation with qlogic and emulex.
> If you had worked with us early on on an API like I told you multiple times
> we'd have something sane now.
> 
> Btw, what part of HP badly wants this?  I'm sure Grant and Matthew
> could explain them internally what a bad idea this is.
> 
> >
> > Jeremy Higdon asked me to add this, not SuSE.
> 
> Jeremy, can you make sure SuSE has an uptodate transport attribute
> implementation ?

I doubt it.  It was recently updated from the 2.6.5 to 2.6.9 version,
and I don't think they'll be updating to the 2.6.10 version.

Eric, I guess you'll have to convert to the new 2.6.10 API.  Once
it's in the tree, any API changes should be made for you.  For the
drivers that you deliver (as opposed to the distribution), you can
just #ifdef it out, in much the same way that the drivers on Qlogic's
website have more #ifdefs.

It is annoying to have these API changes come in asynchronously.  I
would have preferred something that didn't break backward compatibility,
but linking it to the target instead of the lun probably doesn't allow
that.  Hopefully it will settle down a bit now.

jeremy