2011-05-10 11:11:48

by Hauke Mehrtens

[permalink] [raw]
Subject: [PATCH 1/3] compat-wireless: make patches apply again

This part of the patch is now in wireless-testing.

Signed-off-by: Hauke Mehrtens <[email protected]>
---
patches/22-multiqueue.patch | 15 ++-------------
1 files changed, 2 insertions(+), 13 deletions(-)

diff --git a/patches/22-multiqueue.patch b/patches/22-multiqueue.patch
index 2090320..05129d5 100644
--- a/patches/22-multiqueue.patch
+++ b/patches/22-multiqueue.patch
@@ -44,17 +44,6 @@ are used for injecting frames so they have their own respective queue
handling, but mac80211 just always sends management frames on VO
queue by using skb_set_queue_mapping(skb, 0) through ieee80211_tx_skb()

---- a/drivers/net/wireless/wl12xx/main.c
-+++ b/drivers/net/wireless/wl12xx/main.c
-@@ -1272,7 +1272,7 @@ static struct sk_buff *wl12xx_alloc_dumm
- skb->priority = WL1271_TID_MGMT;
-
- /* Initialize all fields that might be used */
-- skb->queue_mapping = 0;
-+ skb_set_queue_mapping(skb, 0);
- memset(IEEE80211_SKB_CB(skb), 0, sizeof(struct ieee80211_tx_info));
-
- return skb;
--- a/net/mac80211/util.c
+++ b/net/mac80211/util.c
@@ -264,6 +264,18 @@ __le16 ieee80211_ctstoself_duration(stru
@@ -107,7 +96,7 @@ queue by using skb_set_queue_mapping(skb, 0) through ieee80211_tx_skb()

--- a/net/mac80211/tx.c
+++ b/net/mac80211/tx.c
-@@ -1598,6 +1598,10 @@ static void ieee80211_xmit(struct ieee80
+@@ -1587,6 +1587,10 @@ static void ieee80211_xmit(struct ieee80
return;
}

@@ -118,7 +107,7 @@ queue by using skb_set_queue_mapping(skb, 0) through ieee80211_tx_skb()
ieee80211_set_qos_hdr(local, skb);
ieee80211_tx(sdata, skb, false);
rcu_read_unlock();
-@@ -2090,7 +2094,14 @@ void ieee80211_tx_pending(unsigned long
+@@ -2079,7 +2083,14 @@ void ieee80211_tx_pending(unsigned long

if (skb_queue_empty(&local->pending[i]))
list_for_each_entry_rcu(sdata, &local->interfaces, list)
--
1.7.4.1



2011-05-10 15:23:50

by Walter Goldens

[permalink] [raw]
Subject: Re: [PATCH 3/3] compat-wireless: enable RT33XX and RT53XX support.


> The following config options are all marked as unstable
> (they depend
> on EXPERIMENTAL)
> RT2800PCI_RT35XX
> RT2800PCI_RT53XX
> RT2800USB_RT35XX
> RT2800USB_RT53XX

So this basically means everything above 33+ is experimental at this point. RT33xx should only be enabled now, per my original patch.

Walter
-------

// Side note to Luis,
compat-wireless tar balls aren't being uploaded to orbit and kernel, despite the successful emails from the cron bot. Last uploaded CW archive was 5 days ago, can you look that up? //

2011-05-10 14:44:39

by Walter Goldens

[permalink] [raw]
Subject: Re: [PATCH 3/3] compat-wireless: enable RT33XX and RT53XX support.


> This is based on a patch by Walter
> Goldens.

Hi Hauke,

I think RT53XX is still experimental, unlike the RT33XX. Should we enable it from config.mk now?

Walter

2011-05-10 15:05:22

by Hauke Mehrtens

[permalink] [raw]
Subject: Re: [PATCH 3/3] compat-wireless: enable RT33XX and RT53XX support.

On 05/10/2011 04:44 PM, Walter Goldens wrote:
>
>> This is based on a patch by Walter
>> Goldens.
>
> Hi Hauke,
>
> I think RT53XX is still experimental, unlike the RT33XX. Should we enable it from config.mk now?
>
> Walter

Hi Walter,

In the description of RT53XX there is no warning that this is not
working, like it is in the description of RT35XX. I do not have such a
device, but the rt2x00 guys could probably help on this questing. If we
enable it and it does not work it will not hurt people more that we do
not activate it.

@rt2x00 people: Are the RT53XX chips working with the most recent
version of the rt2x00 driver from wireless-testing?

Hauke

2011-05-10 15:13:27

by Ivo Van Doorn

[permalink] [raw]
Subject: Re: [PATCH 3/3] compat-wireless: enable RT33XX and RT53XX support.

Hi,

On Tue, May 10, 2011 at 5:05 PM, Hauke Mehrtens <[email protected]> wrote:
> On 05/10/2011 04:44 PM, Walter Goldens wrote:
>>
>>> This is based on a patch by Walter
>>> Goldens.
>>
>> Hi Hauke,
>>
>> I think RT53XX is still experimental, unlike the RT33XX. Should we enable it from config.mk now?
>>
>> Walter
>
> Hi Walter,
>
> In the description of RT53XX there is no warning that this is not
> working, like it is in the description of RT35XX. I do not have such a
> device, but the rt2x00 guys could probably help on this questing. If we
> enable it and it does not work it will not hurt people more that we do
> not activate it.
>
> @rt2x00 people: Are the RT53XX chips working with the most recent
> version of the rt2x00 driver from wireless-testing?

The following config options are all marked as unstable (they depend
on EXPERIMENTAL)
RT2800PCI_RT35XX
RT2800PCI_RT53XX
RT2800USB_RT35XX
RT2800USB_RT53XX

Since recently I have an RT53xx USB device, but I haven't tested it yet.
As far as I heard from other reports the status is the same as 35xx.

Ivo

2011-05-10 11:11:50

by Hauke Mehrtens

[permalink] [raw]
Subject: [PATCH 3/3] compat-wireless: enable RT33XX and RT53XX support.

This is based on a patch by Walter Goldens.

CC: Walter Goldens <[email protected]>
Signed-off-by: Hauke Mehrtens <[email protected]>
---
config.mk | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/config.mk b/config.mk
index 3411743..76044a5 100644
--- a/config.mk
+++ b/config.mk
@@ -326,9 +326,9 @@ CONFIG_RT2400PCI=m
CONFIG_RT2500PCI=m
ifdef CONFIG_CRC_CCITT
CONFIG_RT2800PCI=m
-# CONFIG_RT2800PCI_RT33XX=y
+CONFIG_RT2800PCI_RT33XX=y
# CONFIG_RT2800PCI_RT35XX=y
-# CONFIG_RT2800PCI_RT53XX=y
+CONFIG_RT2800PCI_RT53XX=y
endif #CONFIG_CRC_CCITT
NEED_RT2X00=y

@@ -451,8 +451,9 @@ CONFIG_ATH9K_HTC=m
CONFIG_RT2500USB=m
ifdef CONFIG_CRC_CCITT
CONFIG_RT2800USB=m
-# CONFIG_RT2800USB_RT33XX=y
+CONFIG_RT2800USB_RT33XX=y
# CONFIG_RT2800USB_RT35XX=y
+CONFIG_RT2800USB_RT53XX=y
CONFIG_RT2800USB_UNKNOWN=y
endif #CONFIG_CRC_CCITT
CONFIG_RT2X00_LIB_USB=m
--
1.7.4.1


2011-05-10 21:55:10

by Luis R. Rodriguez

[permalink] [raw]
Subject: Re: [PATCH 3/3] compat-wireless: enable RT33XX and RT53XX support.

On Tue, May 10, 2011 at 8:23 AM, Walter Goldens
<[email protected]> wrote:
>
>> The following config options are all marked as unstable
>> (they depend
>> on EXPERIMENTAL)
>>  RT2800PCI_RT35XX
>>  RT2800PCI_RT53XX
>>  RT2800USB_RT35XX
>>  RT2800USB_RT53XX
>
> So this basically means everything above 33+ is experimental at this point. RT33xx should only be enabled now, per my original patch.
>
> Walter
> -------
>
> // Side note to Luis,
> compat-wireless tar balls aren't being uploaded to orbit and kernel, despite the successful emails from the cron bot. Last uploaded CW archive was 5 days ago, can you look that up? //

Hauke -- Applied your 2 patches. I did not apply this last one though
as it seems it requires some modifications. Walter, the releases
likely stopped as ./scripts/admin-update.sh was failing, after the new
patches it should pick up.

Luis

2011-05-10 11:11:51

by Hauke Mehrtens

[permalink] [raw]
Subject: [PATCH 2/3] compat-wireless: add RTL8192SE driver


Signed-off-by: Hauke Mehrtens <[email protected]>
---
config.mk | 1 +
scripts/admin-update.sh | 1 +
2 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/config.mk b/config.mk
index f4cf832..3411743 100644
--- a/config.mk
+++ b/config.mk
@@ -368,6 +368,7 @@ endif #CONFIG_PCMCIA
endif #CONFIG_WIRELESS_EXT

CONFIG_RTL8192CE=m
+CONFIG_RTL8192SE=m

endif #CONFIG_PCI
## end of PCI
diff --git a/scripts/admin-update.sh b/scripts/admin-update.sh
index 3310278..ea123ca 100755
--- a/scripts/admin-update.sh
+++ b/scripts/admin-update.sh
@@ -235,6 +235,7 @@ DRIVERS="$DRIVERS drivers/net/wireless/rtlwifi"
DRIVERS="$DRIVERS drivers/net/wireless/rtlwifi/rtl8192c"
DRIVERS="$DRIVERS drivers/net/wireless/rtlwifi/rtl8192ce"
DRIVERS="$DRIVERS drivers/net/wireless/rtlwifi/rtl8192cu"
+DRIVERS="$DRIVERS drivers/net/wireless/rtlwifi/rtl8192se"
DRIVERS="$DRIVERS drivers/net/wireless/libertas_tf"
DRIVERS="$DRIVERS drivers/net/wireless/ipw2x00"
DRIVERS="$DRIVERS drivers/net/wireless/wl12xx"
--
1.7.4.1