Re: [rfc] breaking out if_ath into ... lots of modules

2017-05-22 Thread Adrian Chadd
On 22 May 2017 at 13:17, John Baldwin wrote: > Why not have if_ath.ko just be a wrapper module that depends on everything > like dtraceall.ko? That would let 'kldload if_ath' and the auto-loading > code in ifconfig still DTRT. You could name the "only the driver" module > ath.ko or some such.

Re: [rfc] breaking out if_ath into ... lots of modules

2017-05-22 Thread Warner Losh
On Mon, May 22, 2017 at 2:17 PM, John Baldwin wrote: > On Monday, May 22, 2017 12:29:15 PM Adrian Chadd wrote: > > Hi, > > > > I've been putting this off for a few years, but now I've reached a > > point where I kind of need to do this. > > > > The TL;DR is this - I'd like to break the ath driver

Re: [rfc] breaking out if_ath into ... lots of modules

2017-05-22 Thread John Baldwin
On Monday, May 22, 2017 12:29:15 PM Adrian Chadd wrote: > Hi, > > I've been putting this off for a few years, but now I've reached a > point where I kind of need to do this. > > The TL;DR is this - I'd like to break the ath driver /back/ out into > separate modules, and then have them be run-time

[rfc] breaking out if_ath into ... lots of modules

2017-05-22 Thread Adrian Chadd
Hi, I've been putting this off for a few years, but now I've reached a point where I kind of need to do this. The TL;DR is this - I'd like to break the ath driver /back/ out into separate modules, and then have them be run-time loadable. It's part for space savings, and part for the upcoming ath1