As soon as my current workload settles, I've agreed to convert hme/qfe,
as well as several other drivers (eri, afe, mxfe) to Brussels. Its
likely to be about a month before I dedicate the time this project needs.
-- Garrett
James Carlson wrote:
> Volker A. Brandt writes:
>
>> However, I would guess that customer NIC installed base is 90%
>> hme eri qfe ge ce. The obvious question is answered only vaguely:
>> "Work continues to make other drivers become supported in the
>> Brussels implementation." :-( It would be helpful if this were
>> given a date, even in a negative way, i.e. "hme and qfe never,
>> ge and ce not before 2008Q4" (all facts made up just now by me :-).
>>
>
> Actually, I'd imagine it to be the other way around.
>
> In the current Nevada code, hme and qfe are supported by the same
> GLDv3 driver. Stepping up to Brussels ought to be fairly easy as long
> as someone interested in doing the work appears.
>
> The ce and ge drivers, though, are in the old NSPG/NSN/CS
> consolidation, which isn't open source, and which is unlikely to get
> attention. There's a project running to produce a new open driver for
> Cassini hardware (likely leaving only ge and gem out in the cold), but
> I don't know the current status of that. (Given the special
> interactions between 'ce' and Sun Cluster and other odd features, I
> wouldn't be surprised to hear that an open driver would not be usable
> on a regular Sun distribution. But that's just my guess.)
>
>
>> Also, you define build 88 to be the next version of OpenSolaris.
>> I would just say "snv_88". In a little while, the "next version"
>> will confuse people.
>>
>
> I think that refers to the OpenSolaris Developer Preview release,
> rather than a particular Nevada build.
>
> I agree that having the code base and one particular distribution
> having the same name ("OpenSolaris") is really confusing, but there's
> not much I can do about that. ;-}
>
>
