Date: Tue, 14 Apr 1998 02:19:50 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: julian@whistle.com (Julian Elischer) Cc: brad@bleier.com, hackers@FreeBSD.ORG Subject: Re: Indus Drivers Message-ID: <199804140219.TAA08189@usr06.primenet.com> In-Reply-To: <3532AAAF.3F54BC7E@whistle.com> from "Julian Elischer" at Apr 13, 98 05:15:43 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> We use a driver for the DATAFIRE card, but we needed to sign > a non disclosure agreement to get the info to do it. So therefore > we can't release the driver! :-( I think we could, technically, release a binary driver for it, just as someone could sign an NDA on the Adaptec HIM code and release a binary driver for Adaptec's RAID controller. The FreeBSD infrastructure is not (currently) conducive to binary drivers from third parties, unfortunately, which clouds things more than a bit. Part of the problem is that there is a need to be able to statically link PIC-compiled objects into the kernel, and there is a need to conceptually, in the build process for the kernel, include binary driver objects without source dependencies being implied. This basically goes back to the fact that "config exists as something more than a list of object files to link together". 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804140219.TAA08189>