I think this means 6.4.4 has a kernel with wl built-in, lacking b43;
whereas 6.4.3 has a kernel with b43 built-in, lacking wl.
Hint:
wl.ko shows up in 6.4.4 which I use, and b43.ko shows up in luther's 6.4.3
So, I think this means we have to consider not only offering (at least)
two drivers, but two kernels-to-match as well, for Broadcom users.
Interestingly so, this actually occurred with Knoppix 6.4.3 and 6.4.4
taken together as one distribution. One size does not fit all here.
I think this means 6.4.4 has a kernel with wl built-in, lacking b43;
whereas 6.4.3 has a kernel with b43 built-in, lacking wl.
Hint:
wl.ko shows up in 6.4.4 which I use, and b43.ko shows up in luther's 6.4.3
So, I think this means we have to consider not only offering (at least)
two drivers, but two kernels-to-match as well, for Broadcom users.
Interestingly so, this actually occurred with Knoppix 6.4.3 and 6.4.4
taken together as one distribution. One size does not fit all here.
In trying this on Klaus K, I think there's a better, more plausible explanation:
The kernel in 6.7.1 may not have been built to accept b43 modules,
whereas, it appears 6.4.3/6.4.4 if they contain the same kernel DO accept both wl & b43 modules.
If that's the case, 6.7.1 surely favors only wl at the expense of ALL potential b43 users.
This turns out to be easily remedied by making sure future kernels don't preclude using
all likely useful modules. It does NOT imply a proliferation of kernels.
If 7.0 + builds accept b43 modules, no Broadcom components should be
enabled, compared to 6.7.1 (30apc671). '30apcb43' is from Hotlink posted
earlier in thread.