* [RFC 11/53] wireless-regdb: PH, Philippines - enable VHT80
From: Luis R. Rodriguez @ 2013-07-04 1:04 UTC (permalink / raw)
To: linville; +Cc: wireless-regdb, linux-wireless, Luis R. Rodriguez
In-Reply-To: <1372899889-19183-1-git-send-email-mcgrof@do-not-panic.com>
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
This enables 80 MHz bandwidth usage the existing only
5 GHz band but also adds 3 other new 5 GHz bands with
80 MHz bandwidth support.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/db.txt b/db.txt
index 00e5993..c37c3d6 100644
--- a/db.txt
+++ b/db.txt
@@ -610,7 +610,10 @@ country PG:
country PH:
(2402 - 2482 @ 40), (N/A, 20)
- (5735 - 5835 @ 40), (N/A, 30)
+ (5170 - 5250 @ 80), (3, 17)
+ (5250 - 5330 @ 80), (3, 24), DFS
+ (5490 - 5710 @ 80), (3, 24), DFS
+ (5735 - 5835 @ 80), (3, 30)
country PK:
(2402 - 2482 @ 40), (N/A, 20)
--
1.7.10.4
^ permalink raw reply related
* [RFC 10/53] wireless-regdb: PE, Peru - enable VHT80
From: Luis R. Rodriguez @ 2013-07-04 1:04 UTC (permalink / raw)
To: linville; +Cc: wireless-regdb, linux-wireless, Luis R. Rodriguez
In-Reply-To: <1372899889-19183-1-git-send-email-mcgrof@do-not-panic.com>
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
This enables 80 MHz bandwidth usage the existing only
5 GHz band but also adds 3 other new 5 GHz bands with
80 MHz bandwidth support.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/db.txt b/db.txt
index 570a951..00e5993 100644
--- a/db.txt
+++ b/db.txt
@@ -597,7 +597,10 @@ country PA:
country PE:
(2402 - 2482 @ 40), (N/A, 20)
- (5735 - 5835 @ 40), (N/A, 30)
+ (5170 - 5250 @ 80), (3, 17)
+ (5250 - 5330 @ 80), (3, 24), DFS
+ (5490 - 5710 @ 80), (3, 24), DFS
+ (5735 - 5835 @ 80), (3, 30)
country PG:
(2402 - 2482 @ 40), (N/A, 20)
--
1.7.10.4
^ permalink raw reply related
* [RFC 09/53] wireless-regdb: MX, Mexico - enable VHT80
From: Luis R. Rodriguez @ 2013-07-04 1:04 UTC (permalink / raw)
To: linville; +Cc: wireless-regdb, linux-wireless, Luis R. Rodriguez
In-Reply-To: <1372899889-19183-1-git-send-email-mcgrof@do-not-panic.com>
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
This enables 80 MHz bandwidth usage on all 5 GHz
frequencies and update the max EIRP. This also adds
a new DFS 5 GHz band: 5490 - 5710 MHz.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/db.txt b/db.txt
index 4b1cf8e..570a951 100644
--- a/db.txt
+++ b/db.txt
@@ -550,9 +550,10 @@ country MY:
country MX:
(2402 - 2472 @ 40), (3, 27)
- (5170 - 5250 @ 40), (3, 17)
- (5250 - 5330 @ 40), (3, 23), DFS
- (5735 - 5835 @ 40), (3, 30)
+ (5170 - 5250 @ 80), (3, 17)
+ (5250 - 5330 @ 80), (3, 24), DFS
+ (5490 - 5710 @ 80), (3, 24), DFS
+ (5735 - 5835 @ 80), (3, 30)
country NL: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20)
--
1.7.10.4
^ permalink raw reply related
* [RFC 08/53] wireless-regdb: GU, Guam - enable VHT80
From: Luis R. Rodriguez @ 2013-07-04 1:04 UTC (permalink / raw)
To: linville; +Cc: wireless-regdb, linux-wireless, Luis R. Rodriguez
In-Reply-To: <1372899889-19183-1-git-send-email-mcgrof@do-not-panic.com>
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
This enables 80 MHz bandwidth usage on all 5 GHz
frequencies and update the max EIRP. This also adds
a new DFS 5 GHz band: 5490 - 5710 MHz.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/db.txt b/db.txt
index 6d7a762..4b1cf8e 100644
--- a/db.txt
+++ b/db.txt
@@ -337,9 +337,10 @@ country GT:
country GU:
(2402 - 2472 @ 40), (3, 27)
- (5170 - 5250 @ 20), (3, 17)
- (5250 - 5330 @ 20), (3, 23), DFS
- (5735 - 5835 @ 20), (3, 30)
+ (5170 - 5250 @ 80), (3, 17)
+ (5250 - 5330 @ 80), (3, 24), DFS
+ (5490 - 5710 @ 80), (3, 24), DFS
+ (5735 - 5835 @ 80), (3, 30)
country HN:
(2402 - 2482 @ 40), (N/A, 20)
--
1.7.10.4
^ permalink raw reply related
* [RFC 07/53] wireless-regdb: CO, Colombia - enable VHT80
From: Luis R. Rodriguez @ 2013-07-04 1:04 UTC (permalink / raw)
To: linville; +Cc: wireless-regdb, linux-wireless, Luis R. Rodriguez
In-Reply-To: <1372899889-19183-1-git-send-email-mcgrof@do-not-panic.com>
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
This enables 80 MHz bandwidth usage on all 5 GHz
frequencies and update the max EIRP. This also adds
a new DFS 5 GHz band: 5490 - 5710 MHz.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/db.txt b/db.txt
index b82b255..6d7a762 100644
--- a/db.txt
+++ b/db.txt
@@ -172,9 +172,10 @@ country CN:
country CO:
(2402 - 2472 @ 40), (3, 27)
- (5170 - 5250 @ 40), (3, 17)
- (5250 - 5330 @ 40), (3, 23), DFS
- (5735 - 5835 @ 40), (3, 30)
+ (5170 - 5250 @ 80), (3, 17)
+ (5250 - 5330 @ 80), (3, 24), DFS
+ (5490 - 5710 @ 80), (3, 24), DFS
+ (5735 - 5835 @ 80), (3, 30)
country CR:
(2402 - 2482 @ 40), (N/A, 20)
--
1.7.10.4
^ permalink raw reply related
* [RFC 06/53] wireless-regdb: AR, Argentina - enable VHT80
From: Luis R. Rodriguez @ 2013-07-04 1:04 UTC (permalink / raw)
To: linville; +Cc: wireless-regdb, linux-wireless, Luis R. Rodriguez
In-Reply-To: <1372899889-19183-1-git-send-email-mcgrof@do-not-panic.com>
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
This enables 80 MHz bandwidth usage on all 5 GHz
frequencies and increases the max EIRP on two
5 GHz bands.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/db.txt b/db.txt
index 1f16aff..b82b255 100644
--- a/db.txt
+++ b/db.txt
@@ -38,10 +38,10 @@ country AN:
country AR:
(2402 - 2482 @ 40), (N/A, 20)
- (5170 - 5250 @ 40), (3, 17)
- (5250 - 5330 @ 40), (3, 20), DFS
- (5490 - 5710 @ 40), (3, 20), DFS
- (5735 - 5835 @ 40), (3, 30)
+ (5170 - 5250 @ 80), (3, 17)
+ (5250 - 5330 @ 80), (3, 24), DFS
+ (5490 - 5710 @ 80), (3, 24), DFS
+ (5735 - 5835 @ 80), (3, 30)
country AT: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20)
--
1.7.10.4
^ permalink raw reply related
* [RFC 05/53] wireless-regdb: NZ, New Zealand - enable VHT80
From: Luis R. Rodriguez @ 2013-07-04 1:04 UTC (permalink / raw)
To: linville; +Cc: wireless-regdb, linux-wireless, Luis R. Rodriguez
In-Reply-To: <1372899889-19183-1-git-send-email-mcgrof@do-not-panic.com>
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
This enables 80 MHz bandwidth usage on all 5 GHz
frequencies and increases the max EIRP on two
5 GHz bands, decreases the max EIRP on the first
5 GHz band and adds a new band 5490 - 5710 MHz.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/db.txt b/db.txt
index bb846af..1f16aff 100644
--- a/db.txt
+++ b/db.txt
@@ -574,9 +574,10 @@ country NP:
country NZ:
(2402 - 2482 @ 40), (N/A, 30)
- (5170 - 5250 @ 20), (3, 23)
- (5250 - 5330 @ 20), (3, 23), DFS
- (5735 - 5835 @ 20), (3, 30)
+ (5170 - 5250 @ 80), (3, 17)
+ (5250 - 5330 @ 80), (3, 24), DFS
+ (5490 - 5710 @ 80), (3, 24), DFS
+ (5735 - 5835 @ 80), (3, 30)
country OM:
(2402 - 2482 @ 40), (N/A, 20)
--
1.7.10.4
^ permalink raw reply related
* [RFC 04/53] wireless-regdb: HK, Hong Kong - enable VHT80
From: Luis R. Rodriguez @ 2013-07-04 1:04 UTC (permalink / raw)
To: linville; +Cc: wireless-regdb, linux-wireless, Luis R. Rodriguez
In-Reply-To: <1372899889-19183-1-git-send-email-mcgrof@do-not-panic.com>
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
This enables 80 MHz bandwidth usage on all 5 GHz
frequencies and increases the max EIRP on two
5 GHz bands.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/db.txt b/db.txt
index 37a13c6..bb846af 100644
--- a/db.txt
+++ b/db.txt
@@ -349,10 +349,10 @@ country HN:
country HK:
(2402 - 2482 @ 40), (N/A, 20)
- (5170 - 5250 @ 40), (3, 17)
- (5250 - 5330 @ 40), (3, 20), DFS
- (5490 - 5710 @ 40), (3, 20), DFS
- (5735 - 5835 @ 40), (3, 30)
+ (5170 - 5250 @ 80), (3, 17)
+ (5250 - 5330 @ 80), (3, 24), DFS
+ (5490 - 5710 @ 80), (3, 24), DFS
+ (5735 - 5835 @ 80), (3, 30)
country HR: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20)
--
1.7.10.4
^ permalink raw reply related
* [RFC 03/53] wireless-regdb: CA, Canada - enable VHT80
From: Luis R. Rodriguez @ 2013-07-04 1:03 UTC (permalink / raw)
To: linville; +Cc: wireless-regdb, linux-wireless, Luis R. Rodriguez
In-Reply-To: <1372899889-19183-1-git-send-email-mcgrof@do-not-panic.com>
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
This enables 80 MHz bandwidth usage on all 5 GHz
frequencies and increases the max EIRP on two
5 GHz bands.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/db.txt b/db.txt
index a6c23bd..37a13c6 100644
--- a/db.txt
+++ b/db.txt
@@ -142,10 +142,10 @@ country BZ:
country CA:
(2402 - 2472 @ 40), (3, 27)
- (5170 - 5250 @ 40), (3, 17)
- (5250 - 5330 @ 40), (3, 20), DFS
- (5490 - 5710 @ 40), (3, 20), DFS
- (5735 - 5835 @ 40), (3, 30)
+ (5170 - 5250 @ 80), (3, 17)
+ (5250 - 5330 @ 80), (3, 24), DFS
+ (5490 - 5710 @ 80), (3, 24), DFS
+ (5735 - 5835 @ 80), (3, 30)
country CH: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20)
--
1.7.10.4
^ permalink raw reply related
* [RFC 02/53] wireless-regdb: BR, Brazil - enable VHT80
From: Luis R. Rodriguez @ 2013-07-04 1:03 UTC (permalink / raw)
To: linville; +Cc: wireless-regdb, linux-wireless, Luis R. Rodriguez
In-Reply-To: <1372899889-19183-1-git-send-email-mcgrof@do-not-panic.com>
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
This enables 80 MHz bandwidth usage on all 5 GHz
frequencies and increases the max EIRP on two
5 GHz bands.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/db.txt b/db.txt
index 0e7794e..a6c23bd 100644
--- a/db.txt
+++ b/db.txt
@@ -125,10 +125,10 @@ country BO:
country BR:
(2402 - 2482 @ 40), (N/A, 20)
- (5170 - 5250 @ 40), (3, 17)
- (5250 - 5330 @ 40), (3, 20), DFS
- (5490 - 5710 @ 40), (3, 20), DFS
- (5735 - 5835 @ 40), (3, 30)
+ (5170 - 5250 @ 80), (3, 17)
+ (5250 - 5330 @ 80), (3, 24), DFS
+ (5490 - 5710 @ 80), (3, 24), DFS
+ (5735 - 5835 @ 80), (3, 30)
country BY:
(2402 - 2482 @ 40), (N/A, 20)
--
1.7.10.4
^ permalink raw reply related
* [RFC 01/53] wireless-regdb: AU, Australia - enable VHT80
From: Luis R. Rodriguez @ 2013-07-04 1:03 UTC (permalink / raw)
To: linville; +Cc: wireless-regdb, linux-wireless, Luis R. Rodriguez
In-Reply-To: <1372899889-19183-1-git-send-email-mcgrof@do-not-panic.com>
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
This enables 80 MHz bandwidth usage on all 5 GHz
frequencies and updates the max EIRP. This also adds
a new DFS 5 GHz band: 5490 - 5710 MHz.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/db.txt b/db.txt
index c5861b8..0e7794e 100644
--- a/db.txt
+++ b/db.txt
@@ -53,9 +53,10 @@ country AT: DFS-ETSI
country AU:
(2402 - 2482 @ 40), (N/A, 20)
- (5170 - 5250 @ 40), (3, 23)
- (5250 - 5330 @ 40), (3, 23), DFS
- (5735 - 5835 @ 40), (3, 30)
+ (5170 - 5250 @ 80), (3, 17)
+ (5250 - 5330 @ 80), (3, 24), DFS
+ (5490 - 5710 @ 80), (3, 24), DFS
+ (5735 - 5835 @ 80), (3, 30)
country AW:
(2402 - 2482 @ 40), (N/A, 20)
--
1.7.10.4
^ permalink raw reply related
* [RFC 00/53] wireless-regdb: mostly VHT80 updates
From: Luis R. Rodriguez @ 2013-07-04 1:03 UTC (permalink / raw)
To: linville; +Cc: wireless-regdb, linux-wireless, Luis R. Rodriguez
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Here's a series of updates for wireless-regdb. Most of this is
to just enable VHT80 support to enable support for 802.11ac
where this has been verified to be usable. I cannot meet the
criteria of providing full documentation for sources for all
patches, only a few ones so what I recommend for the rest is
to let this sit on the list for a bit and I'd hope after
review if no one spots any issues I'd hope we can merge this.
I reviewed the idea of vendor namespaces on wireless-regdb
and at least through review with pkgadd on IRC we concluded
its best to try to take this approach instead of encouraging
divergence due to any lack of full source documentation or
inability to provide such documentation for whatever reason.
This seems to be better than not getting any updates at all
and keeps vendors hopefully encouraged to push changes upstream.
Luis R. Rodriguez (53):
wireless-regdb: AU, Australia - enable VHT80
wireless-regdb: BR, Brazil - enable VHT80
wireless-regdb: CA, Canada - enable VHT80
wireless-regdb: HK, Hong Kong - enable VHT80
wireless-regdb: NZ, New Zealand - enable VHT80
wireless-regdb: AR, Argentina - enable VHT80
wireless-regdb: CO, Colombia - enable VHT80
wireless-regdb: GU, Guam - enable VHT80
wireless-regdb: MX, Mexico - enable VHT80
wireless-regdb: PE, Peru - enable VHT80
wireless-regdb: PH, Philippines - enable VHT80
wireless-regdb: PR, Puerto Rico - enable VHT80
wireless-regdb: SA, Saudi Arabia - enable VHT80
wireless-regdb: SG, Singapore - enable VHT80
wireless-regdb: ZA, South Africa - enable VHT80
wireless-regdb: TH, Thailand - enable VHT80
wireless-regdb: AE, United Arab Emirates - enable VHT80
wireless-regdb: VN, Vietnam - enable VHT80
wireless-regdb: AT, Austria - enable VHT80
wireless-regdb: FR, France - enable VHT80
wireless-regdb: DE, Germany - enable VHT80
wireless-regdb: GB, United Kingdom - enable VHT80
wireless-regdb: BE, Belgium - enable VHT80
wireless-regdb: CZ, Czech Republic - enable VHT80
wireless-regdb: DK, Denmark - enable VHT80
wireless-regdb: FI, Finland - enable VHT80
wireless-regdb: GR, Greece- enable VHT80
wireless-regdb: IE, Ireland - enable VHT80
wireless-regdb: IT, Italy - enable VHT80
wireless-regdb: LU, Luxembourg - enable VHT80
wireless-regdb: NL, Netherlands - enable VHT80
wireless-regdb: PL, Poland - enable VHT80
wireless-regdb: PT, Portugal - enable VHT80
wireless-regdb: SK, Slovakia - enable VHT80
wireless-regdb: ES, Spain - enable VHT80
wireless-regdb: SE, Sweden - enable VHT80
wireless-regdb: CH, Switzerland - enable VHT80
wireless-regdb: TR, Turkey - enable VHT80
wireless-regdb: CN, China - enable VHT80
wireless-regdb: enable VHT80 and VHT160 for JP
wireless-regdb: US, United States - enable VHT80
wireless-regdb: ID, Indonesia - enable 5 GHz and VHT80
wireless-regdb: IL, Isreal - enable VHT80
wireless-regdb: KW, Kuwait - enable VHT80
wireless-regdb: MY, Malaysia - enable VHT80
wireless-regdb: MA, Morocco - enable 5 GHz and VHT80
wireless-regdb: enable HT40 in RU - Russian Federation
wireless-regdb: KR, Republic of Korea - enable VHT80
wireless-regdb: TW, Taiwan - enable VHT80
wireless-regdb: enable VHT80 when world roaming
wireless-regdb: add 802.11ad 60 GHz channels 1..3 to world regdom
wireless-regdb: CR, Costa Rica - enable VHT80
wireless-regdb: EC, Ecauador - enable VHT80
db.txt | 318 +++++++++++++++++++++++++++++++++++-----------------------------
1 file changed, 174 insertions(+), 144 deletions(-)
--
1.7.10.4
^ permalink raw reply
* Re: wireless-regdb: 5GHz rule for Indonesia regdomain
From: Luis R. Rodriguez @ 2013-07-04 0:22 UTC (permalink / raw)
To: Paul Stewart
Cc: John W. Linville, wireless-regdb@lists.infradead.org,
linux-wireless
In-Reply-To: <20130702172537.DC8F62006D3@clearcreek.mtv.corp.google.com>
On Tue, Jul 2, 2013 at 10:20 AM, Paul Stewart <pstew@chromium.org> wrote:
> Pursuant to
> http://www.postel.go.id/content/ID/regulasi/standardisasi/kepdir/bwa%205,8%20ghz.pdf, provide a 5GHz rule for Indonesian regulatory domain.
This looks good to me and matches QCA's work on this, but we also can
enable VHT80. Given that I am working on sending a huge series of
VHT80 patches I'll roll this into my series and modify your patch to
add VHT80 as well. Will send out shortly.
Luis
^ permalink raw reply
* Replacement for local->hw.conf.channel
From: Ben Greear @ 2013-07-04 0:01 UTC (permalink / raw)
To: linux-wireless@vger.kernel.org
I'm trying to port some patches forward to 3.10....
I am trying to find the current channel for a radio. Since
hw.conf.channel no longer exists, what is the best way to
go about this?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply
* Re: [PATCH] brcmfmac: Turn off ARP offloading when configured for AP.
From: Kamal Mostafa @ 2013-07-03 23:06 UTC (permalink / raw)
To: Rafał Miłecki, Arend van Spriel
Cc: Greg KH, stable, linux-wireless, Hante Meuleman, John W. Linville
In-Reply-To: <CACna6rzqjh0uC=qNThA=fsNmbLz+b0NUfkvFSLZ7GhRdGqOYug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
On Wed, 2013-07-03 at 06:54 +0200, Rafał Miłecki wrote:
> 2013/7/2 Arend van Spriel <arend@broadcom.com>:
> > Hi Greg,
> >
> > Forgot to ask, but it seems like Canonical is maintaining additional stable
> > kernel branches. I guess I should contact them for those kernel versions (if
> > I care), right?
>
> They track Greg's stables to pick up the patches. Know from my own
> experience, I didn't have to ping anyone :)
>
Yes, we're picking up cc: stable patches automatically when they apply
to the 3.8.y.z and 3.5.y.z "extended stable" branches[0], but we
certainly appreciate specific backports for those versions when they
don't apply cleanly.
-Kamal
[0] https://wiki.ubuntu.com/Kernel/Dev/ExtendedStable
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply
* RE: [PATCH] mwifiex: don't ignore SDIO interrupts during shutdown
From: Bing Zhao @ 2013-07-03 22:39 UTC (permalink / raw)
To: Daniel Drake, Amitkumar Karwar
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
In-Reply-To: <20130703015653.82651FAAD5@dev.laptop.org>
Hi Daniel,
> Make the driver continue to ack interrupts during shutdown to avoid
> this. This is harder than it might sound.
>
> We must be careful not to act upon the interrupt, only ack it.
> Otherwise, we end up setting int_status to something. And hw_status is
> set to MWIFIEX_HW_STATUS_CLOSING for obvious reasons. We would hit the
> following infinite loop in mwifiex_main_process:
>
> process_start:
> do {
> if ((adapter->hw_status == MWIFIEX_HW_STATUS_CLOSING) ||
> (adapter->hw_status == MWIFIEX_HW_STATUS_NOT_READY))
> break;
> [...]
> } while (true);
> if ((adapter->int_status) || IS_CARD_RX_RCVD(adapter))
> goto process_start;
>
> We must also observe that ACKing interrupts involves reading a load
> of data into the mp_regs buffer. The driver doesn't do much in the
> way of ensuring that interrupts are disabled before freeing buffers
> such as mp_regs, but we do need something here to make sure that we
> don't get any interrupts after mp_regs is freed.
>
> This whole thing feels rather fragile, but I couldn't see a clean
> way to do it, the driver seems a bit disorganised here. I would
> welcome a review from the designers.
Followings are the actions taken for driver unload.
a) If device is connected, sync deauth command is sent.
b) Auto deep sleep is cancelled by sending sync command
c) Sync shutdown command is queued and HW_STATUS is changed to reset.
d) Now no other command gets queued based on HW_STATUS.
e) Wait for shutdown command response and handle it.
f) Set surprise_removed flag which blocks SDIO interrupts
As per our design, we don't send any command to firmware after SHUTDOWN command. Also, firmware doesn't send any interrupt after SHUTDOWN command response.
The interrupt received after setting surprise_removed flag is unexpected. We need to get the exact procedure to replicate and figure out the root cause.
By thy way, I will be OOO for approximately two weeks. Amitkumar Karwar will continue to work with you to debug the issue.
Thanks,
Bing
^ permalink raw reply
* Re: compat-wireless is not avalaible ?
From: Sven-Haegar Koch @ 2013-07-03 22:28 UTC (permalink / raw)
To: Xavier; +Cc: linux-wireless
In-Reply-To: <8D046351240532F-1114-718F3@webmail-va009.sysops.aol.com>
On Wed, 3 Jul 2013, Xavier wrote:
> On Wed, Jul 03, 2013 at 08:02:31PM +0200, Sven-Haegar Koch wrote:
>
> Hi Sven-Haegar,
>
> > On Wed, 3 Jul 2013, Xavier wrote:
> >
> > > Why
> > >
> > >
> http://www.orbit-lab.org/kernel/compat-wireless-3-stable/v3.2/compat-wireless-3.2.5-1.tar.bz2
> > >
> > > is not avalilable ?
> > >
> > > Where it's available ?
> >
> > Have a look at
> > https://www.kernel.org/pub/linux/kernel/projects/backports/stable/
> for
> > newer versions.
> >
>
> Thanks for your answer.
>
> This is a good link, but I need compat-wireless stable for 3.2 version of
> Linux kernel.
"for 3.2 version", or "the wireless code as it was in the 3.2 version"?
Wsing compat-wireless (or now backports) from 3.2 with kernel 3.2 makes
no sense, at it is exactly the same code.
The backports package 3.10 works with a linux kernel 3.2 - after all,
thats the reason they are backports.
> In that link, there are all for >= 3.7 Linux kernel version.
Not "for" - FROM.
backports 3.10rcX is the wireless (plus now DRI) code from 3.10rcX to
use it on older kernels.
> Exist any site for 3.2 Linux kernel version of compat-wireless ?
I have no idea if there are still public archives of the older
compat-wireless around. At worst you can recreate them using the git
repositories and the kernel git yourself.
https://backports.wiki.kernel.org/ may have some documentation about how
to go about this.
c'ya
sven-haegar
--
Three may keep a secret, if two of them are dead.
- Ben F.
^ permalink raw reply
* RE: [PATCH] wireless: Convert mwifiex/pcie to dev_pm_ops from legacy pm_ops
From: Bing Zhao @ 2013-07-03 21:46 UTC (permalink / raw)
To: Shuah Khan, linville@tuxdriver.com, rjw@sisk.pl, hauke@hauke-m.de,
lars@metafoo.de
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, shuahkhan@gmail.com
In-Reply-To: <1372870030-2596-1-git-send-email-shuah.kh@samsung.com>
> Convert the mwifiex/pci driver to use dev_pm_ops for power management and
> remove Legacy PM handling. This change re-uses existing suspend and resume
> interfaces for dev_pm_ops, and changes CONFIG_PM ifdefs to CONFIG_PM_SLEEP
> as the driver does not support run-time PM.
>
> Signed-off-by: Shuah Khan <shuah.kh@samsung.com>
Acked-by: Bing Zhao <bzhao@marvell.com>
Thanks,
Bing
^ permalink raw reply
* interested in py80211?
From: Arend van Spriel @ 2013-07-03 20:57 UTC (permalink / raw)
To: linux-wireless
A common say in Linux arena is "when you have an itch, just scratch it".
My itch is that tools like ifconfig and iw are great, but in an
automated test environment it kind of sucks to parse output, which is
confirmed by blurb from iw: "Do NOT screenscrape this tool, we don't
consider its output stable.".
Ever since my first contact with Python I tend to favor it over other
scripting alternatives so I decided to scratch my itch with that and
another old acquaintance called SWIG. With those I went to create
py80211. A first attempt was to have SWIG create a wrapper API directly
exposing the libnl-3 API, but that did not feel comfortable in a
scripting environment. So the level of abstraction is a bit higher. It
is just in a kick-off state (eg. can only send u32 attributes), but I
decided to push it to github anyway.
https://github.com/arend/py80211
Regards,
Arend
^ permalink raw reply
* Re: [rt2x00-users] [PATCH 4/5] rt2x00: rt2800lib: introduce rt2800_eeprom_word_index helper
From: Gabor Juhos @ 2013-07-03 20:23 UTC (permalink / raw)
To: Stanislaw Gruszka; +Cc: John Linville, linux-wireless, users
In-Reply-To: <20130703192813.GD2245@localhost.localdomain>
Hi Stanislaw,
Thank you for the comments.
> On Wed, Jun 26, 2013 at 07:55:17PM +0200, Gabor Juhos wrote:
>> Instead of assign the offset value to the
>> enum directly use a new helper function to
>> convert a rt2800_eeprom_word enum into an
>> index of the rt2x00_dev->eeprom array.
>>
>> The patch does not change the existing
>> behaviour, but makes it possible to add
>> support for three-chain devices which are
>> using a different EEPROM layout.
>>
>> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
>
> Acked-by: Stanislaw Gruszka <stf_xl@wp.pl>
>
> I have two nit-picks, but they can be fixed later on top of your current
> patches.
>
>> + if (WARN_ON(word >= EEPROM_WORD_COUNT)) {
>> + rt2x00_warn(rt2x00dev, "invalid EEPROM word %d\n", word);
>> + return 0;
>> + }
>
> Since we take "enum rt2800_eeprom_word" as word argument, it can not
> have different values than already listed, so this warning is not needed.
EEPROM_WORD_COUNT is listed in the enums and the word argument can be equal to
that, however it is not a valid index for the EEPROM map. Additionally, if
someone puts a new enum value after EEPROM_WORD_COUNT by mistake that will be an
invalid index as well.
>
>> + map = rt2800_eeprom_map;
>> + index = map[word];
>> +
>> + if (WARN_ON(word != EEPROM_CHIP_ID && index == 0)) {
>> + /* Index 0 is valid only for EEPROM_CHIP_ID.
>> + * Otherwise it means that the offset of the
>> + * given word is not initialized in the map,
>> + * or that the field is not usable on the
>> + * actual chipset.
>> + */
>> + rt2x00_warn(rt2x00dev, "invalid access of EEPROM word %d\n",
>> + word);
>
> I prefer not to use WARN_ON() and rt2x00_warn() together, please use just
> one of them, i.e:
>
> WARN_ONCE(word != EEPROM_CHIP_ID && index == 0,
> "invalid access of EEPROM word %d\n", word);
My reason behind the rt2x00_warn call was that it shows the wiphy name. If you
are testing different devices in parallel it is good to know which one causes
the warning. However I can use 'wiphy_name(rt2x00dev->hw->wiphy)' to get that
information.
I will send a follow-up patch which removes the rt2x00_warn calls. Do you also
prefer WARN_ONCE instead of WARN?
-Gabor
^ permalink raw reply
* Re: [wireless-regdb] Updates to wireless-regdb review - vendor namespaces and VHT80
From: Luis R. Rodriguez @ 2013-07-03 20:18 UTC (permalink / raw)
To: Bjørn Mork; +Cc: linux-wireless, wireless-regdb@lists.infradead.org
In-Reply-To: <87wqp8uijf.fsf@nemi.mork.no>
On Wed, Jul 3, 2013 at 1:58 AM, Bjørn Mork <bjorn@mork.no> wrote:
> "Luis R. Rodriguez" <mcgrof@do-not-panic.com> writes:
>
>> In the meantime, while that gets developed, I'd still like to supply
>> patches to enable VHT80 for a few countries without hopefully such
>> high bar for documentation as I cannot get this information.
>
> I believe VHT80 (and VHT160) is allowed by current regulations in a
> large number of countries, and that the current db entries are in fact
> wrong by stating any upper channel width limits at all in the 5 GHz
> bands.
>
> For example, regulations in most CEPT countries are likely based on
>
> "ECC/DEC/(04)08 on the harmonised use of the 5 GHz frequency bands for
> the implementation of Wireless Access Systems including Radio Local
> Area Networks (WAS/RLANs)"
>
> or a previous version of that decision. Which is available here:
> http://www.erodocdb.dk/Docs/doc98/official/pdf/ECCDEC0408.PDF
>
> Quoting:
>
> "considering
> ..
>
> e. that the systems covered by this ECC Decision operate typically in a 20 MHz channel bandwidth, other
> values for the channel bandwidth are also feasible provided they comply with the relevant maximum mean
> e.i.r.p. and the corresponding maximum mean e.i.r.p. density limits;
> "
>
> and the continues deciding the mentioned power and power density limits
> only, without any specific channelization. This document clearly allows
> and anticipates both wider and narrower channels, and so does most
> likely the national regualations implementing the decision.
>
> The list of CEPT countries implementating this decision is here:
> http://www.erodocdb.dk/doks/implement_doc_adm.aspx?docid=2033
Thanks, this seems to be in agreement with the countries I was
considering update that fall under that group that I had updates for
except for one country alone: Russia.
I'll use the information you provided to update the CEPT ones though.
Luis
^ permalink raw reply
* Re: [rt2x00-users] [PATCH 5/5] rt2x00: rt2800lib: add EEPROM map for the RT3593 chipset
From: Stanislaw Gruszka @ 2013-07-03 19:28 UTC (permalink / raw)
To: Gabor Juhos; +Cc: John Linville, linux-wireless, users
In-Reply-To: <1372269318-30233-6-git-send-email-juhosg@openwrt.org>
On Wed, Jun 26, 2013 at 07:55:18PM +0200, Gabor Juhos wrote:
> Three-chain devices are using a different
> EEPROM layout than the rest of the chipsets.
> Add a new map which describes the new layout
> and use that for the RT3593 chipset.
>
> The index values has been computed from the
> EEPROM_EXT_* defines, which can be found in
> the 'include/chip/rt3593.h' file in the
> Ralink DPO_RT5572_LinuxSTA_2.6.0.1_20120629
> driver.
>
> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
Acked-by: Stanislaw Gruszka <stf_xl@wp.pl>
^ permalink raw reply
* Re: [rt2x00-users] [PATCH 4/5] rt2x00: rt2800lib: introduce rt2800_eeprom_word_index helper
From: Stanislaw Gruszka @ 2013-07-03 19:28 UTC (permalink / raw)
To: Gabor Juhos; +Cc: John Linville, linux-wireless, users
In-Reply-To: <1372269318-30233-5-git-send-email-juhosg@openwrt.org>
On Wed, Jun 26, 2013 at 07:55:17PM +0200, Gabor Juhos wrote:
> Instead of assign the offset value to the
> enum directly use a new helper function to
> convert a rt2800_eeprom_word enum into an
> index of the rt2x00_dev->eeprom array.
>
> The patch does not change the existing
> behaviour, but makes it possible to add
> support for three-chain devices which are
> using a different EEPROM layout.
>
> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
Acked-by: Stanislaw Gruszka <stf_xl@wp.pl>
I have two nit-picks, but they can be fixed later on top of your current
patches.
> + if (WARN_ON(word >= EEPROM_WORD_COUNT)) {
> + rt2x00_warn(rt2x00dev, "invalid EEPROM word %d\n", word);
> + return 0;
> + }
Since we take "enum rt2800_eeprom_word" as word argument, it can not
have different values than already listed, so this warning is not needed.
> + map = rt2800_eeprom_map;
> + index = map[word];
> +
> + if (WARN_ON(word != EEPROM_CHIP_ID && index == 0)) {
> + /* Index 0 is valid only for EEPROM_CHIP_ID.
> + * Otherwise it means that the offset of the
> + * given word is not initialized in the map,
> + * or that the field is not usable on the
> + * actual chipset.
> + */
> + rt2x00_warn(rt2x00dev, "invalid access of EEPROM word %d\n",
> + word);
I prefer not to use WARN_ON() and rt2x00_warn() together, please use just
one of them, i.e:
WARN_ONCE(word != EEPROM_CHIP_ID && index == 0,
"invalid access of EEPROM word %d\n", word);
Stanislaw
^ permalink raw reply
* Re: compat-wireless is not avalaible ?
From: Larry Finger @ 2013-07-03 19:16 UTC (permalink / raw)
To: Xavier; +Cc: linux-wireless
In-Reply-To: <8D046351240532F-1114-718F3@webmail-va009.sysops.aol.com>
On 07/03/2013 01:48 PM, Xavier wrote:
>
> Thanks for your answer.
>
> This is a good link, but I need compat-wireless stable for 3.2 version of Linux
> kernel.
>
> In that link, there are all for >= 3.7 Linux kernel version.
>
> Exist any site for 3.2 Linux kernel version of compat-wireless ?
>
> Thanks, see you.
You do not understand compat-wireless, now called backports.
The version listed, such as 3.7, is for the *source* of the code included. The
package includes *all* the necessary code for it to be built on kernel 2.6.24
*OR NEWER*. If you were to find a 3.2 version of compat-wireless, it would have
exactly the same drivers as were released with 3.2, and there would be no reason
for you to use it! The link you were given will work for 3.2.
Larry
^ permalink raw reply
* Re: [rt2x00-users] [PATCH 3/5] rt2x00: rt2800lib: introduce rt2800_eeprom_read_from_array helper
From: Stanislaw Gruszka @ 2013-07-03 19:15 UTC (permalink / raw)
To: Gabor Juhos; +Cc: John Linville, linux-wireless, users
In-Reply-To: <1372269318-30233-4-git-send-email-juhosg@openwrt.org>
On Wed, Jun 26, 2013 at 07:55:16PM +0200, Gabor Juhos wrote:
> Add a new helper function and use that for reading
> single elements of various arrays in the EEPROM.
>
> The patch does not change the current behaviour,
> but it allows to use sequential values for the
> rt2800_eeprom_word enums. The conversion will be
> implemented in a subsequent change.
>
> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
Acked-by: Stanislaw Gruszka <stf_xl@wp.pl>
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox