RFC: madwifi-ng patch rationalisation and version update

[Rod Whitby <rod@whitby.id.au>]

There are currently some slugos-specific patches in madwifi-ng
(specifically to enable the Atheros wifi cards in devices like the
DSM-G600 and the Iomega NAS100d.

There are also some previous arm xscale patches which are almost identical.

>   -rw-r--r-- 1 rwhitby rwhitby  619 2007-01-26 04:12 10-xscale-be-elf-copts.patch
>   -rw-r--r-- 1 rwhitby rwhitby  553 2007-01-26 04:12 10-xscale-le-elf-copts.patch
>   -rw-r--r-- 1 rwhitby rwhitby  677 2007-01-06 14:32 slugos-VFP-wackelf.patch
>   -rw-r--r-- 1 rwhitby rwhitby  433 2007-01-06 14:32 slugos-xscale-be-elf-copts.patch
>   -rw-r--r-- 1 rwhitby rwhitby  367 2007-01-06 14:32 slugos-xscale-le-elf-copts.patch

We intend updating the 10-xscale patches with the contents of the
corresponding slugos-xscale patches, and unconditionally applying the
slugos-VFP-wackelf patch (after renaming it appropriately).

We also intend updating madwifi-ng to a later snapshot (e.g.
r2100-20070210), cause the current version won't build against 2.6.20
due to changes in the INIT_WORK kernel macro.

The difference between the 10-xscale patches and the slugos-xscale
patches is the removal of the "-msoft-float -mfp=2" compiler options.
This is required to match the binary HAL objects which come from madwifi.

The "wackelf" patch then edits the ELF headers on the proprietary HAL
stuff to match the floating point used in the kernel -- it can do that
because there's no actual FP performed.  It just needs to match to make
the linker happy.

If there are no objections in the next 24 hours, we will do this in the
next 48 hours.

If there are other people using the madwifi package, please contact me
so we can get this change tested by you before applying it.  Note that
we're referring to madwifi-ng (which I couldn't find any other reference
to in OE other than slugos and openprotium), not madwifi-modules (which
is used directly by a number of distros).

-- Rod