Le 22/04/2012 21:50, Zefir Kurtisi a écrit :
> From: Zefir Kurtisi
>
>
> Signed-off-by: Zefir Kurtisi
> ---
> drivers/net/wireless/ath/ath9k/recv.c |3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/recv.c
> b/drivers/net/wireless/ath/
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 compon
-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 t
-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 te
-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
Van de Velde Erwin a écrit :
> Hi all,
>
> `iwlist wlan0 channel` shows me the following output on my laptop (AR5418
> card):
>
> wlan0 24 channels in total; available frequencies :
> Channel 01 : 2.412 GHz
> Channel 02 : 2.
definitions.
Signed-off-by: Benoit Papillault <[EMAIL PROTECTED]>
diff --git a/drivers/net/wireless/ath9k/hw.c
b/drivers/net/wireless/ath9k/hw.c
index ded9453..f2916a5 100644
--- a/drivers/net/wireless/ath9k/hw.c
+++ b/drivers/net/wireless/ath9k/hw.c
@@ -382,8 +382,9 @@ static cons
From: Benoit PAPILLAULT
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 hardware. This
patch is useful if you are trying to analyze non standard 802.11 frame going
over the air.
Signed-off-by: Benoit
John W. Linville a écrit :
> On Thu, Nov 19, 2009 at 10:19:26PM +0100, Benoit Papillault wrote:
>> From: Benoit PAPILLAULT
>>
>> It has been tested with a 802.11 frame generator and by checking the FCS
>> field
>> of each received frame with the value repor
Luis R. Rodriguez a écrit :
> On Thu, Nov 19, 2009 at 1:19 PM, Benoit Papillault
> wrote:
>> From: Benoit PAPILLAULT
>>
>> 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
From: Benoit PAPILLAULT
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 hardware. This
patch is useful if you are trying to analyze non standard 802.11 frame going
over the air.
Signed-off-by: Benoit
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
---
drivers/net/wireless/ath/ath9k/common.c | 24 +++-
drivers/net/wireless/ath/ath9k
Oops... Disregard this one, it has been already applied.
Regards, Benoit.
Benoit Papillault a écrit :
> From: Benoit PAPILLAULT
>
> 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 ha
wrong. Fix it by using ath9k_cmn_padpos. This later code has been
tested by sending packets to a monitor interface and reading packets from the
same interface.
Signed-off-by: Benoit Papillault
---
drivers/net/wireless/ath/ath9k/xmit.c | 23 ---
1 files changed, 12 insertions
From: Benoit Papillault
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 was already there in
rootki...@yahoo.it a écrit :
> 2009/12/24 Björn Smedman :
>
>> 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, wrote:
>>
>>> On Thu
rootki...@yahoo.it a écrit :
> On Sat, Dec 26, 2009 at 10:27 AM, Benoit PAPILLAULT
> wrote:
>
>> rootki...@yahoo.it a écrit :
>>
>>> 2009/12/24 Björn Smedman :
>>>
>>>
>>>> Do the stalls occur at regular intervals? I
Stan Mullen a écrit :
> Hi all,
>
> I am interested in the current status of 802.11n support under ad-hoc mode.
>
> Reading the previous posts, I understand that currently only data rates up to
>
> 54M are supported in ad-hoc mode. Some posts also indicate that ad-hoc
>
> operation is not addressed
Lenin Ravindranath S a écrit :
> Hi,
>
> I am new to ath9k. I have a DWA-642 card and I am trying to set it in
> monitor mode to inject and receive packets.
>
> I did
>
> iw dev wlan0 interface add fish0 type monitor
> ifconfig fish0 up
>
>
> I have two problems
> 1. The interface is able to g
27;t seem to work. The packets are sent out at
> 1Mbps always.
Yup. These are patches from Matteo :
http://teknoraver.net/software/radiotap_mcs/
Regards,
Benoit
>
> On Sun, Jan 17, 2010 at 3:18 AM, Benoit PAPILLAULT
> mailto:benoit.papilla...@free.fr>> wrote:
>
>
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
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
Luca Niccoli a écrit :
> On 23 March 2010 00:22, Luca Niccoli 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 messages through.
Yongheng Qi a écrit :
> no one
>
I am working on it. It is mostly working in my tree, but is still
bleeding edge. There are two main area of work :
- getting proper adhoc support in ath9k (and ath5k)
- getting support for HT rates in ath9k (minstrel_ht and some work from
Sujith will help)
Regar
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
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
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
---
drivers/net/wireless/ath/ath5k/pcu.c | 31 +--
drivers/net/wireless/ath/ath9k/hw.c
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).
&g
Peter Stuge a écrit :
> Rodolphe Marques wrote:
>
>> The problem I think is that linux is not expecting to have several
>> interfaces connected to the same network
>>
>
> The problem is not with Linux, but with you seeming to misunderstand
> sockets and IP networks. (You'll get same results
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(
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
---
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 100644
--- a/drivers/net
So, if you put a low noise preamp, you are feeding the chip
with more signal at the input 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,
&
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
Robert Meschke a écrit :
> Hi,
>
> thank you for your immediate response, Luis. It's a pity that DFS is not
> supposed to work in the near future. A can provide more specific information.
> I am working on a project, where I really need the 5 Ghz band and have to
> respect national laws.
> I am
Tor Krill a écrit :
> On Thu, 2010-04-29 at 16:26 +0800, Daniel Yingqiang Ma wrote:
>
>> This patch indeed improve the link quality of my AP powered by ath9k.
>>
>> It seems there are plenty of this kind of corruptted packet. Any one
>> know it's reason?
>>
>
> FYI,
>
> This patch, in modif
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.
Le 05/05/2010 20:07, ligeo_geo...@denso-diam.com a écrit :
>
> After going through older posts - I found this one
> https://lists.ath9k.org/pipermail/ath9k-devel/2009-December/002808.html
>
> I use the config script in that post and can get the ad-hoc mode to work
> - the main reason why I think it
Le 05/05/2010 23:24, ligeo_geo...@denso-diam.com a écrit :
>
> Ok. Thanks. I will try that.
>
> Reading an earlier post,
> https://lists.ath9k.org/pipermail/ath9k-devel/2009-November/002670.html
> , I thought there was a problem with IBSS mode, but maybe its fixed now
> or I probably have an older
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 randomly and only the lower 24 bits or
>> so seem to ever be used (see below for detai
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 valu
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...]
>
44 matches
Mail list logo