I'm fed of people telling me that loading a BSD licenced module
will “taint” the kernel and the missing symbols issues we can't
seem to track down.
Some other fwrt developers agreed that the “tainted” bit is not
of importance other than with support issues, and for fwrt, the
linux kernel guys aren't these who'll have to do support for an
end user anyway.
In case this upsets someone:
• busybox and linux are GPL'd -> you can't prevent me from pat-
ching these files
• citing the GPL version 2:
- section 2, last paragraph:
| In addition, mere aggregation of another work not based on the Program
| with the Program (or with a work based on the Program) on a volume of
| a storage or distribution medium does not bring the other work under
| the scope of this License.
this is what makes wl.o distributable, assuming it is not a
work based on the Linux kernel (and it's not ours to deter-
mine this but Broadcom's)
- section 0:
| […] The act of running the Program is not restricted […]
(sections 1ff. only apply to distribution, and the brcm de-
vices don't even have enough storage to prepare a core dump
of the memory image of the kernel combined with the modules
anyway, so nobody's going to distribute the result)
This patch should solve some of the cases of missing symbols on
module load.
