linux.git/drivers/net/wireless/rt2x00, branch v2.6.28

rt2x00: Fix build error when mac80211=M rt2x00=Y

2008-10-29T21:54:35+00:00

Make menuconfig RT2X00 a tristate instead of boolean,
otherwise we do not correctly inherit the mac80211 value
on which RT2X00 depends, and makes it possible to
compile rt2x00 into the kernel while mac80211 is a
module.

Signed-off-by: Ivo van Doorn 
Signed-off-by: John W. Linville

rt2x00: fix regression introduced by "mac80211: free up 2 bytes in skb->cb"

2008-10-15T01:12:39+00:00

The hw_key pointer is used (and obviously NULL) after skb->cb is
memset to 0. This patch grabs the iv_len before the memset call.

Signed-off-by: Felix Fietkau 
Signed-off-by: Stephen Blackheath 
Acked-by: Johannes Berg 
Signed-off-by: John W. Linville

mac80211: free up 2 bytes in skb->cb

2008-10-06T22:14:57+00:00

Free up 2 bytes in skb->cb to be used for multi-rate retry later.
Move iv_len and icv_len initialization into key alloc.

Signed-off-by: Felix Fietkau 
Signed-off-by: John W. Linville

rt2x00: Fix rfkill structure initialization to prevent rfkill WARN_ON.

2008-10-06T22:14:57+00:00

The state field of the rfkill structure was incorrectly initialized to -1, which results in rfkill
issueing a WARN_ON. Fix this by initializing the state field to the proper value as indicated by
the driver.

Signed-off-by: Gertjan van Wingerde 
Signed-off-by: Ivo van Doorn 
Signed-off-by: John W. Linville

rt2x00: Fix build errors due to modularized rfkill or leds and built-in rt2x00.

2008-09-30T18:07:25+00:00

Fix by disabling rt2x00 rfkill support when rt2x00 is built-in and rfkill has been modularized, and
a similar scheme for the relationship between leds_class and rt2x00..
Also, give a warning to the end-user when rfkill-/leds-support is disabled this way, so that the
end-user has at least some clues on what is going on.

Proper fixing required some general updates of the Kconfig-structure for the rt2x00 driver, whereby
internal configuration symbols had to be moved to after the user-visible configuration symbols.

Signed-off-by: Gertjan van Wingerde 
Signed-off-by: Ivo van Doorn 
Signed-off-by: John W. Linville

rt2x00: Fix HW crypto key handling

2008-09-24T20:18:03+00:00

When a crypto key is being removed, rt2x00mac should not
reset the key->hw_key_idx value because that will prevent
the driver from removing the correct key from the hardware.

Furthermore ffz() starts counting at 0 instead of 1, so we don't
need to substract 1 from the resulting value.

Signed-off-by: Stephen Blackheath 
Signed-off-by: Ivo van Doorn 
Signed-off-by: John W. Linville

mac80211: fix virtual interfaces vs. injection

2008-09-15T20:48:25+00:00

Currently, virtual interface pointers passed to drivers might be
from monitor interfaces and as such completely uninitialised
because we do not tell the driver about monitor interfaces when
those are created. Instead of passing them, we should therefore
indicate to the driver that there is no information; do that by
passing a NULL value and adjust drivers to cope with it.

As a result, some mac80211 API functions also need to cope with
a NULL vif pointer so drivers can still call them unconditionally.

Also, when injecting frames we really don't want to pass NULL all
the time, if we know we are the source address of a frame and have
a local interface for that address, we can to use that interface.
This also helps with processing the frame correctly for that
interface which will help the 802.11w implementation. It's not
entirely correct for VLANs or WDS interfaces because there the MAC
address isn't unique, but it's already a lot better than what we
do now.

Finally, when injecting without a matching local interface, don't
assign sequence numbers at all.

Signed-off-by: Johannes Berg 
Signed-off-by: John W. Linville

mac80211: use nl80211 interface types

2008-09-15T20:48:23+00:00

There's really no reason for mac80211 to be using its
own interface type defines. Use the nl80211 types and
simplify the configuration code a bit: there's no need
to translate them any more now.

Signed-off-by: Johannes Berg 
Signed-off-by: John W. Linville

rt2x00: Make rt2x00 LEDS invisible config option

2008-09-11T19:53:38+00:00

There isn't really a good reason to have the LED
configuration options selectable per driver, lets
make it default 'y' and make it depend on the
NEW_LEDS and LEDS_CLASS interface.

Signed-off-by: Ivo van Doorn

rt2x00: Make RFKILL enabled by default

2008-09-11T19:53:38+00:00

RFKILL should be enabled for _all_ hardware whether
or not they feature a rfkill button or not.

Remove driver specific RFKILL configuration options
and make the rt2x00lib version depend on CONFIG_RFKILL
and defaulting to 'y' to make sure it will always
be enabled when RFKILL was enabled.

This also fixes some bugs where RFKILL wasn't initialized
and didn't respond to RFKILL key presses.

Signed-off-by: Ivo van Doorn 
Signed-off-by: John W. Linville