* Andrew Gallatin <[EMAIL PROTECTED]> [2006-07-12 10:35]: > Hi, > > I'm preparing to contribute a driver for my company's hardware to > OpenSolaris. The code > is currently proprietary, closed source. I have a few "newbie" questions. > > Are there any generic linked-list/queue macros in the Solaris kernel? Or does > each component role his own? My driver currently uses the BSD queue.h > macros from FreeBSD > (http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/sys/queue.h). > Would my driver be allowed to bring in that file, or would I have to re-write > all my linked-list manipulations due to the BSD license on that file? > Is there any chance of OpenSolaris importing this file? It is quite useful > to have those macros available to everybody. You might look at either of <sys/list.h> or <sys/avl.h>. I haven't looked at queue.h, myself.
> Can the initial contribution be a tarball which can be extracted and > build stand-alone, or must it be a diff against the kernel? (Eg, do I need > to figure out how to build an OpenSolaris kernel). If you are looking to integrate, then yes, but for getting a standalone binary (which you could host as a project here, if you like), you can develop a driver independently of the kernel. > I have read the style guidelines. Given that my driver was not written to > conform to "Bill Joy Normal Form", hand conversion would be painful. > Does anybody have an indent recipe, or sed/perl/etc script to re-format > C code into something which can pass cstyle.pl? Once upon a time, I found that indent -br -bs -ce -ci4 -cli0 -d0 -nlp -psl -sc wasn't too bad. Others may have improvements. - Stephen -- Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems [EMAIL PROTECTED] http://blogs.sun.com/sch/ _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
