Hello there,
I'm working on EN 301 893 certification. There is a part regarding the
RF Output Power to make sure that the RF Output Power is within some
limits. Let's say 27 dBm at 5600 MHz for instance.
In 4.4.1.1, the RF Output Power is defined as the mean EIRP during a
transmission burst.
Le 12/06/2012 11:28, Holger Schurig a écrit :
To your question 2: are both the spectrum analyzer and the USB power
sensor calibrated?
The spectrum analyzer was bought with calibration certifications.
The USB power sensor has been Zero Calibrated once before all measures.
Also, do all
Le 22/04/2012 21:50, Zefir Kurtisi a écrit :
From: Zefir Kurtisizefir.kurt...@neratec.com
Signed-off-by: Zefir Kurtisizefir.kurt...@neratec.com
---
drivers/net/wireless/ath/ath9k/recv.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git
Le 10/07/2010 18:12, Lars Hardy a écrit :
It seems that there is a difference in signal strength between the ath9k
(latest openwrt-trunk with compat-wireless 08.07.2010) driver and the
latest dd-wrt (madwifi N?) driver.
The dd-wrt driver has better signal strength and performance when a STA
Le 11/07/2010 13:51, Peter Stuge a écrit :
Benoit Papillault wrote:
I know the ath9k is under development, so my question is if this is
known by the development team and therefor will be worked on?
[ignoring other not very informative post...]
Maybe not informative to you, but I wanted
Le 29/06/2010 13:45, Felix Fietkau a écrit :
On 2010-06-29 8:08 AM, Benoit Papillault wrote:
Le 29/06/2010 00:55, Felix Fietkau a écrit :
On 2010-06-29 12:31 AM, Björn Smedman wrote:
Hi all,
I'm getting weird values from the debugfs file ieee80211/phy0/tsf: the
value goes up and down rather
Anton Puolakka a écrit :
Hi,
recently we’ve been organising work that would happen in the area of
get_survey. Seems that Benoit is already working in the field pretty
much – we waited for Holger’s mac80211 patch to be publicly available…
and the waiting is paying off now, it seems.
but the chip has still the same amount of
noise. Am I correct?
Have fun,
Wiz
Regards,
Benoit
On Tue, 27 Apr 2010, Benoit PAPILLAULT wrote:
Hello,
In order to move forward with noise signal reporting, I'd like to
share my current understanding of the way ath9k HW is working before
Jouni Malinen a écrit :
On Tue, 2010-04-27 at 15:08 -0700, Benoit Papillault wrote:
+static int ath9k_get_survey(struct ieee80211_hw *hw, int idx,
+ struct survey_info *survey)
+struct ieee80211_conf *conf = hw-conf;
+
+ if (idx != 0
Lorenzo Bianconi a écrit :
Hi all,
I am using ath9k/mac80211 on a PC Engines Alix with a Mikrotik R52n
card (AR9280 chipset), OpenWrt r21030 (kernel 2.6.32.10) and
compat-wireless-2010-04-21. I am injecting packets using a VAP in
monitor mode.
I have a doubt on ath9k_hw_init_defaults() in
Hello,
In order to move forward with noise signal reporting, I'd like to
share my current understanding of the way ath9k HW is working before
sending patches (unfortunately, I did the work before the introduction
of ar9003... so I need to redo the work).
The ultimate purpose of this work is
Signed-off-by: Benoit Papillault benoit.papilla...@free.fr
---
drivers/net/wireless/ath/ath9k/main.c | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/main.c
b/drivers/net/wireless/ath/ath9k/main.c
index c03821e..f0b2aa2
Pavel Roskin a écrit :
On Fri, 2010-04-16 at 00:07 +0200, Benoit Papillault wrote:
It follows the logic mentionned by Derek, with only 2 register reads
needed at each additional steps instead of 3 (the minimum number of
register reads is still 3).
I would prefer an approach
mentionned by Derek, with only 2 register reads
needed at each additional steps instead of 3 (the minimum number of
register reads is still 3).
Signed-off-by: Benoit Papillault benoit.papilla...@free.fr
---
drivers/net/wireless/ath/ath5k/pcu.c | 31 +--
drivers/net
Mitul Modi a écrit :
hi,
I dont know is it right mailing list for this question or not.
i am using ar5312 and i am getting only 4.5 mbps in case of multicast
traffic and upto 13 mbps in case of unicast traffic. Any clue?
thanks,
Mitul Modi
What channel are you using?
What is your setup?
Johannes Berg a écrit :
On Fri, 2010-04-09 at 03:03 -0700, Joerg Pommnitz wrote:
Hello all,
the Atheros Windows drivers provide an option to enable 802.11n mode
for IBSS networks. I did not find any information in this regard for
mac80211 based drivers. So, is this supported and how would
Luca Niccoli a écrit :
On 23 March 2010 00:22, Luca Niccoli lultimou...@gmail.com wrote:
I tried twice, but the router once freezed and once rebooted instantly.
I guess it's worth saying that I can only log in through SSH, maybe
access to a serial console would let the error
Rakesh Kumar a écrit :
Hey Benoit,
Did you get the patch to work?
Yup, I work on it. However, i still miss some stuff to have an
interesting throughput. Moreover, ath5k/ath9k beaconing code needs to be
rewritten from scratch IMHO (I will probably use the madwifi code I did
to propose some
Luis R. Rodriguez a écrit :
On Mon, Jan 18, 2010 at 06:31:19PM -0800, Peter Stuge wrote:
Today when I came home and resumed my system I got these messages
from the driver:
[302214.156400] phy1: device no longer idle - scanning
[302214.341494] ath: ath_isr status=0009 imask=f4001071
rootki...@yahoo.it a écrit :
2009/12/24 Björn Smedman bjorn.smed...@venatech.se:
Do the stalls occur at regular intervals? I have a similar problem on
an AR9103 in AP mode. See my previous post 'Cyclic throughput at a
distance'.
/Björn
On Thu, Dec 24, 2009 at 2:31 PM,
From: Benoit Papillault benoit.papilla...@free.fr
First, we copy/paste the padding stuff from ath9k_tx to ath_tx_cabq since it
needs to same kind of padding, but for internally generated beacons.
Next, software padding done on TX needs to be removed before calling
ieee80211_tx_status. The code
802.11 frames
with every possible frame_control field and a varying length. This patch is
useful for analyzing non standard 802.11 frames going over the air
Signed-off-by: Benoit Papillault benoit.papilla...@free.fr
---
drivers/net/wireless/ath/ath9k/common.c | 24
Oops... Disregard this one, it has been already applied.
Regards, Benoit.
Benoit Papillault a écrit :
From: Benoit PAPILLAULT ben...@benoit-laptop.(none)
It has been tested with a 802.11 frame generator and by checking the FCS field
of each received frame with the value reported
Luis R. Rodriguez a écrit :
On Thu, Nov 19, 2009 at 1:19 PM, Benoit Papillault
benoit.papilla...@free.fr wrote:
From: Benoit PAPILLAULT ben...@benoit-laptop.(none)
It has been tested with a 802.11 frame generator and by checking the FCS
field
of each received frame with the value reported
John W. Linville a écrit :
On Thu, Nov 19, 2009 at 10:19:26PM +0100, Benoit Papillault wrote:
From: Benoit PAPILLAULT ben...@benoit-laptop.(none)
It has been tested with a 802.11 frame generator and by checking the FCS
field
of each received frame with the value reported by the Atheros
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jacob a écrit :
I have been running the latest wireless-testing for about 24 hours and
generally
the card has been very stable. I've tested it with and without WPA/1.
There are a few issues though, I also had the same issues with 2.6.27.1...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I'm currently testing an AR5416 minipci card in a laptop (using 1, 2 or
3 antennas does not make any difference). My configuration is:
- - laptop with the minipci card in STA mode
- - Linksys WRT350N in AP mode
- - another laptop wired to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luis R. Rodriguez a écrit :
On Tue, Oct 14, 2008 at 11:29:19PM -0700, Benoit PAPILLAULT wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Bonoit!
Hi there,
I'm currently testing an AR5416 minipci card in a laptop (using 1, 2 or
3
28 matches
Mail list logo
