sub-directory kernel module compilations

[Matt Paine]

Hi Matt.


> I think is too complicated a MAKE line.  You really want Kbuild files
> that handle all this for you, just as it does in the kernel tree
> itself.

To be honest I just pulled it straight from the make that zaptel has in 
its makefile (when you run make modules).

> 
> If I were doing this, I would have a Kbuild file at the top of your
> tree containing something like:
> 
> 
> obj-m += pciradio.o tor2.o torisa.o wcfxo.o wct1xxp.o wctdm.o \
>          wcte11xp.o wcusb.o zaptel.o ztd-eth.o ztd-loc.o ztdummy.o \
>          ztdynamic.o zttranscode.o \
> 	 wct4xxp/ wctc4xxp/ xpp/ wctdm24xxp/ wcte12xp/
> 
> and in each of those last 5 dirs, a Kbuild file that has like:
> 
> obj-m += wct4xpp.o
> 
> 
> and in dkms.conf, have no MAKE= line at all, so it defaults to the
> standard build process.


Let me try that.

> It's also not clear what the HOTPLUG_FIRMWARE=yes is supposed to do.



As I said, straight from the makefile that is in the zaptel library. I 
belive it makes a disinction between 2.6 and 2.4 kernels and applies 
that environment variable with yes or no respectively.


Having said all that - i did hack the dkms script to create the 
directories for both the build and install targets, and it appears to 
work for the moment. A hack I would say and without further testing i'm 
not 100% sure it actually works, but dkms builds and installs now with 
no errors. Are you interested in seeing these hacks (possibly to include 
in releases in the future) or shall I keep them to myself (thus avoiding 
any ridicule from my peers :)


But I will try modifying the Kbuild script to see if I have luck with 
that also.


Thankyou
Matt.