Cyril Plisko wrote: > On 10/12/07, Sebastien Roy <[EMAIL PROTECTED]> wrote: >> Cyril Plisko wrote: >>> I noticed that uts/common/sys/mac.h file is not delivered >>> by any package into final snv image. Does that mean >>> that 3rd party has no means to build Nemo-based >>> ethernet driver outside of the ON consolidation ? >>> If so is it on purpose ? >> This is the case, and it is on purpose. The Nemo driver interfaces are >> consolidation-private for now, and will remain so until the interfaces >> stabilize and are formally documented. > > I see. While it is not too convenient, it is still doable. I mean > I can compile my driver in ON environment, but not necessary > persue integration into ON (if for some reason opensourcing > won't be possible) . Of course in that case I would need to > follow the evolution of Nemo API closely and be prepared to > modify my sources accordingly. Right ? > I can live with that.
Yes, that's correct. You'll need to adjust to potential incompatible changes that may be made to the APIs between now and when they become committed. > And what about Solaris 10 ? What can be done there ? Not much, unfortunately. Practically speaking, since that's not open sourced, you really do need documentation in order to write a driver that will use the APIs in a sane way. You also need the APIs to be stable so that your driver won't break when a customer installs a kernel patch (for example.) > I reason I am asking is that I was approached by a > company that needs a driver for their 10 GbE card. > And I thought Nemo would be a natural choice for > that... One more justification to prioritize the publication of these interfaces highly. Thanks, -Seb _______________________________________________ networking-discuss mailing list [email protected]
