Date: Wed, 28 May 2003 11:47:53 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: David Leimbach <leimy2k@mac.com>, Wilko Bulte <wkb@freebie.xs4all.nl> Cc: freebsd-current@freebsd.org Subject: Re: policy on GPL'd drivers? Message-ID: <200305281147.53271.doconnor@gsoft.com.au> In-Reply-To: <C90CF9CA-9040-11D7-941E-0003937E39E0@mac.com> References: <C90CF9CA-9040-11D7-941E-0003937E39E0@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 27 May 2003 22:13, David Leimbach wrote: > > However the idea is that all GPL infected stuff be isolated, allowing a > > fully working kernel without GPL stuff in there. > > Sounds like a "kernel module" is the way to go then. Perhaps it could > exist in the ports tree instead of the mainline kernel sources :). I > know > I'd be happy with that... the problem is hosting the driver since I am > sure > "patching" it won't be enough to map the linux innards to freebsd's. There are already a number of kernel modules in the ports tree (eg nvidia drivers, ltmdm modem driver, aureal sound driver, etc). The only downside is that there are no hooks into the build process so you have to be VERY careful when you update your kernel, or you get panics :( (I found this recently, some change broke all of my 3rd party modules and caused panics when I tried to load them). I would really like some way of getting external modules rebuilt at the same time as buildkernel and friends, otherwise you have to remember to rebuild the affected ports, and it is a pain in the ass. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305281147.53271.doconnor>