On Mon, Feb 27, 2006 at 11:16:33AM -0700, Scott Long wrote: > Coleman Kane wrote: > > > > > >My impression was more that the current config format would stay the > >same, but there'd be separate modules (rather than incorporating it all > >into tdfx.ko): > >tdfx.ko > >tdfx_linux.ko > > > >Much like how wlan.ko and wlan_*.ko operate? > > > > Well, we are talking about different things here, I think. I absolutely > agree with having separate .ko files, regardless of what kernel options > or devices are specified. What I'm wondering about is when building the > tdfx driver into the kernel, does the tdfx-linux functionality come in > via an 'option' or a 'device'. If it's an 'option', does that mean that > you can load the tdfx_linux.ko module into a kernel that has the tdfx > device included? I see where you're going with this. As I recall, this was a hinderance back when I first wrote the driver (resulting in the default of TDFX_LINUX being defined in the kmod). I don't know these days, if the functionality can be divided between two kmods then I would hope one could be loaded into the kernel statically and one via kmod. > > Scott >Received on Mon Feb 27 2006 - 23:52:26 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:52 UTC