it.
The deferred processing function now queries the SSID, as it changes..
and the periodic timer now queries the BSSID/SSID all the time, and
linkqual only in STA modes.
Hi,
I fixed up some of the issues that sparse warns about when building the
prism2_usb. I don't think that any of these patches change the generated
modules and I've been running them on my laptop with no problems so far,
1+ days.
I've not seen anything that looks to be a problem, so these patches are
just to align the wlan code with the kernel best practises.
With a couple of changes to ensure compilation against older kernels.
1) Remove the last of the old MODULE_PARM parameters (2.6 in general)
2) irq_mask/irq_list are irrelevant (2.6.11)
3) event handler moved (2.6.13)
4) pcmcia/version.h is obselete (2.6.13)
5) driver model integration -- SET_NETDEV_DEV (2.6.11)
6) client->Attributes is obselete (2.6.11)
More will follow.
sprintf(nsdname, "NSDNAME=%s", wlandev->nsdname);
if (wlan_wext_write)
sprintf(nsdname, "WLAN_WEXT=y");
"WLAN_WEXT=y" overwrites the original string (not to mention that
sprintf() is unneeded for a simple string copy). The result is that
enabling wlan_wext_write disables hotplug functionality.
This patch fixes hotplug support if wlan_wext_write is enabled. I think
it's safer to provide WLAN_WEXT always, so that new environment
variables are not accidentally added after a variable that can be NULL.
Signed-off-by: Pavel Roskin <proski@gnu.org>
I'm assuming that the offending entry was restored unintentionally,
probably because the version strings were misspelled, so one had to
resort to numeric manfids. Indeed, search for "I-GATE 11M PC Card / PC
Card Plus" (with quotes) shows that "Plus" should be replaced with
"plus":
Here's the rest of Eric Koenders' patch: a fix for a memory leak, and
silencing the "Causality Violation" warning. We put the warning there to
see if it appears in the Real World, and now we know that it does. I've
demoted the message to a DEBUG rather than remove it entirely, just so
that we can remind ourselves that "Yes, it really does happen!" :-).
This patch reduces both the stack usage and the amount of copying in the
RX path +still further. The trick is to use "memmove", which allows
copying between overlapping sections +of memory.
I've also tidied up some of the whitespace and improved the Causality
Violation +error message so that we're more likely to hear about any
occurrences. After all, having users +*tell* us about any instances that
do occur is really the point :-).