tempestuous

Group: Members
Posts: 259
Joined: Aug. 2004 |
 |
Posted: Sep. 07 2007,05:50 |
 |
I just visited this forum for the first time since November last year, and I see that my ipw2100/2200 driver compiles from almost 2 years ago are still being used! From http://damnsmalllinux.org/cgi-bin....02;st=0
Quote | Changed kernel from 2.4.34.1 to 2.4.31 to gain user contributed modules, e.g., ipw2* and nvidia. |
and Robert is even going to revert to the 2.4.31 kernel to be compatible! Wow.
Quote | Here I'm assuming Tempestous did actually compile this on a livecd boot of dsl-2.1b, and not on eg Woody or Slackware or RH9 with the same kernel or something. |
I think I used Knoppix 3.4 as the build environment, with the DSL2.0-compatible kernel (k2.4.31) FULLY compiled. I can say that compiling 3rd-party drivers usually requires a full kernel build in place. By "full" I don't just mean having the kernel source present, but you need to do the complete make bzImage / make modules process.
The ipw2100/ipw2200 drivers failed to compile under the old 2.4.26 kernel, but since they compile OK under 2.4.31, I would speculate that 2.4.34 should be OK. But I won't be doing it, my time is tied up with other projects/distributions.
Generally, though, modules for modern devices are being developed only for 2.6 kernels. And there is little evidence of these being backported to 2.4.
|