On Mon, 31 Dec 2007, John Plocher wrote:
> James C. McPherson wrote:
>> Plocher wrote:
>>> On SX, we currently have a mix of open and closed source
>>> components that includes a closed driver for this chipset.
>>
>> Actually, we do not already have a driver of any sort for
>> this chip and card in Open or closed Solaris.
>
> Ahhh - As I said, I wasn't up on the details. If there is no conflict
> with an existing driver, then the only real "ARC"hitectural question
> is the Sun/LSI plans - if any.
>
> I would suggest that you send a succinct note to William Franklin at
> Sun (the formal liaison between OS.o and Sun) with what you just wrote
> and ask him to provide a definitive answer to the question of whether
> and when Sun and/or LSI is going to provide an open source driver for
> LSI's MegaRAID SAS product for use in OS.o because we have a community
> member who wishes to contribute one, and there isn't room for two.
No - that does not make sense at all. Of course we should ensure that
William Franklin is fully aware of all on-going OpenSolaris activities
- but your suggestion to ask him if Sun/LSI "is going to provide an
open source driver" is like asking him if Sun has plans to integrate a
star lookalike, and make decisions based upon his answer!
We already have a "rule" that says - the first one to integrate is the
"leader" and "followers" must deal with the resulting fallout. And
rule #2 "no one is allowed to block an integration" - whether or not
they have *plans* for a particular driver or a particular version of
an improved tar (program).
And - secondly - we can't have an issue between the ready-to-integrate
driver (mfi) and some unknown/possibly-planned/wishful-thinking
"other" driver. Why? Because there is *only* the mfi driver that
*is* ready to integrate *now*.
We simply can't hold up an RTI for vapor-ware. And Sun should do
everything possible to convince the community that it will not attempt
to block a community member from integration because of some
*possible*, or even *likely* private/public plan(s) it may have.
When there is a 2nd driver available for the same hardware device,
then the 2nd RTI will have to resolve any technical issues that arise.
Is'nt that the way Solaris (before OpenSolaris) has always worked!?
The ARCs etc. do everything possible to prevent future and foreseeable
technical issues and make the best decisions with the information
available at that time. A future RTI that encounters technical
issues, because of previous integrations, must deal with those issues
at that time.
No one has a crystal ball that can see into the future or a mind
reading device that can predict the corporate intentions of LSI.
What we do have is a very worthwhile driver (mfi) ready to integrate
*now* and no technical issues identified that should prevent
integration.
"Lead, follow or get out of the way"!
> The answer you get will be one of three types:
No - the answer is irrelevant. In fact - its pure guesswork and an
attempt to predict the future.
.... snip .....
Even more rediculous:
----- Urgent Request -----
Hi - my name is Al Hopper and I have a future MegaSAS driver (which
I'm going to call mfi2) that will possibly be ready in 3 months or 6
months or sooner and .... could you possibly ensure that no-one else
integrates a similar driver ahead of me, because it would possibly
complicate my future RTI. Thanks!
---- end of Urgent Request ------
Yeah right - totally rediculous....
Regards,
Al Hopper Logical Approach Inc, Plano, TX. al at logical-approach.com
Voice: 972.379.2133 Fax: 972.379.2134 Timezone: US CDT
OpenSolaris Governing Board (OGB) Member - Apr 2005 to Mar 2007
http://www.opensolaris.org/os/community/ogb/ogb_2005-2007/
Graduate from "sugar-coating school"? Sorry - I never attended! :)
