Re: [ath9k-devel] Is there a way to connect pairs of wifi cards to achieve full duplex

2013-06-20 Thread David Goodenough
On Thursday 20 Jun 2013, Felix Fietkau wrote:
 On 2013-06-20 12:26 PM, David Goodenough wrote:
  On Wednesday 19 Jun 2013, Ben Greear wrote:
  On 06/19/2013 03:56 PM, Adrian Chadd wrote:
   .. just keep in mind that adjacent high power transmitters can
   actually leak enough RF to trigger ADC saturation and thus the device
   may actually not try to decode anything.
   
   Thus, whilst your TX is TXing, the RX side may be unhappy. :-)
  
  We've had decent multi-NIC throughput when there is a mostly-solid
  aluminium chassis plate between the NICs, and when one is on 2.4
  and the other is on 5Ghz.
  
  Pretty much anything else is pushing your luck though :)
  
  Ben
  
  The only place I have noticed that do this with wifi kit is Microtik
  who say they can do setups like this - but as usual with them there is
  no indication of how it is done under the covers.
 
 They're doing it with hacked up proprietary protocol modifications.
 
 So I get why you would want to do combine two links to get full-duplex.
 But why would you want to mess around with things like ACKs?
 
 - Felix
Most of my links are quite long, so removing any turnaround had got to
be a good thing (hasn't it?).  I presume that every time the link turns
around you have to turn off the receive path (or at least disconnect it)
and then power up the transmitter, and allow time for the receiver at 
the other end to sync.  Then at the receiving end if it was transmitting
before (this is point to point) it has to shut down the transmit path
in an orderly fashion so that it remains loaded while active. Surely that has 
to take a significant time?

By quite long I am talking up to 7km.

David
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


[ath9k-devel] Is there a way to connect pairs of wifi cards to achieve full duplex

2013-06-19 Thread David Goodenough
I would like to have a point to point full duplex link (outdoors).  I realise
that this can not be done with a single wifi card/antenna, I will need a pair.

I only need a single point to point link, not a master/slave setup.

I would want the low level protocol bits to work this way as well so that ACKS
and management responses to work this way as well as data packets.

Any ideas?

David
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] Change frequency feature

2013-03-04 Thread David Goodenough
On Monday 04 Mar 2013, Tokarenko Roman wrote:
 Hello for everyone!
 
 I have RouterBoard433AH device under OpenWrt OS. Also I have
 communication module RouberBoard R52N-m with chip atheros9220. I would
 like to know if there are some approaches to change working frequency for
 this chip. I ask it here, because I suppose that this feature is made
 within driver. Please, correct me, if I wrong somewhere.
 
 Thanx in advance.
 ___
 ath9k-devel mailing list
 ath9k-devel@lists.ath9k.org
 https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Setting the frequency is done using the /etc/config/wireless file, either
by editing it directly or using the LUA web interface.  I suggest you ask
on the openwrt user list as they will be more familiar with the interface
than this list.

David
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] [RFC 1/2] ath9k: add DFS pattern detector

2012-01-26 Thread David Goodenough
On Thursday 26 Jan 2012, Zefir Kurtisi wrote:
 This adds a DFS pattern detector to the common ath module. It takes
 pulse events reported by ath9k and reports in place whether a
 pattern was detected. On detection, caller must report a radar event
 to the DFS management component in the upper layer.
 
 Currently the ETSI DFS domain is supported with detector lines for
 the patterns defined by EN-301-893 v1.5.1. Support for FCC and JP
 will be added gradually.
 
 The detector is independent of the underlying HW, but located in
 the ath driver since so far it is used by ath9k only. It might
 move up to mac80211 as soon as other non-Atheros drivers start
 using it.
I notice in the wireless list that Victor Goldenshtein vict...@ti.com has
proposed a bunch of updates to the generic mac80211 code to support this,
presumably because he is adding support for a TI chip.

David
 
 NOTE: since DFS requires some more components on different layers
 that are currently missing, the detector is not functionally
 integrated yet. When ath9k is build with a certified DFS config
 option, the detector is included in ath.ko. All it does there is
 wasting kernel memory and waiting to be used by ath9k.
 
 USAGE: to use the detector, wiphy drivers must
  - use dfs_pattern_detector.h as interface
  - have a struct dfs_pattern_detector *dpd per wiphy
  - on wiphy creation, instantiate a detector with
dpd = dfs_pattern_detector_init(enum dfs_domain)
  - forward any radar pulse detected to dpd-add_pulse()
  - report radar event if add_pulse() returns RADAR_DETECTED
  - on wiphy destruction call dpd-exit()
 
 Signed-off-by: Zefir Kurtisi zefir.kurt...@neratec.com
 ---
  drivers/net/wireless/ath/Makefile  |   10 +
  .../ath/dfs_pattern_detector/detector_elem.c   |   92 ++
  .../ath/dfs_pattern_detector/detector_elem.h   |   45 +++
  .../dfs_pattern_detector/dfs_pattern_detector.h|   92 ++
  .../ath/dfs_pattern_detector/pattern_detector.c|  294
  .../ath/dfs_pattern_detector/pulse_queue.c | 
 168 +++ .../ath/dfs_pattern_detector/pulse_queue.h |   77
 +
  .../ath/dfs_pattern_detector/pulse_sequence.c  |  280
 +++ .../ath/dfs_pattern_detector/pulse_sequence.h  |  
 89 ++
  .../ath/dfs_pattern_detector/radar_types.c |   52 
  .../ath/dfs_pattern_detector/radar_types.h |   95 +++
  .../net/wireless/ath/dfs_pattern_detector/utils.c  |   45 +++
  .../net/wireless/ath/dfs_pattern_detector/utils.h  |   30 ++
  13 files changed, 1369 insertions(+), 0 deletions(-)
  create mode 100644
 drivers/net/wireless/ath/dfs_pattern_detector/detector_elem.c create mode
 100644 drivers/net/wireless/ath/dfs_pattern_detector/detector_elem.h
 create mode 100644
 drivers/net/wireless/ath/dfs_pattern_detector/dfs_pattern_detector.h
 create mode 100644
 drivers/net/wireless/ath/dfs_pattern_detector/pattern_detector.c create
 mode 100644 drivers/net/wireless/ath/dfs_pattern_detector/pulse_queue.c
 create mode 100644
 drivers/net/wireless/ath/dfs_pattern_detector/pulse_queue.h create mode
 100644 drivers/net/wireless/ath/dfs_pattern_detector/pulse_sequence.c
 create mode 100644
 drivers/net/wireless/ath/dfs_pattern_detector/pulse_sequence.h create mode
 100644 drivers/net/wireless/ath/dfs_pattern_detector/radar_types.c create
 mode 100644 drivers/net/wireless/ath/dfs_pattern_detector/radar_types.h
 create mode 100644 drivers/net/wireless/ath/dfs_pattern_detector/utils.c
 create mode 100644 drivers/net/wireless/ath/dfs_pattern_detector/utils.h
 
 diff --git a/drivers/net/wireless/ath/Makefile
 b/drivers/net/wireless/ath/Makefile index d716b74..10f9554 100644
 --- a/drivers/net/wireless/ath/Makefile
 +++ b/drivers/net/wireless/ath/Makefile
 @@ -11,4 +11,14 @@ ath-objs :=main.o \
   key.o
 
  ath-$(CONFIG_ATH_DEBUG) += debug.o
 +
 +# include DFS pattern detector if we have certified HW
 +ath-$(CONFIG_ATH9K_DFS_CERTIFIED)+= \
 + dfs_pattern_detector/pulse_queue.o \
 + dfs_pattern_detector/pulse_sequence.o \
 + dfs_pattern_detector/detector_elem.o \
 + dfs_pattern_detector/pattern_detector.o \
 + dfs_pattern_detector/radar_types.o \
 + dfs_pattern_detector/utils.o
 +
  ccflags-y += -D__CHECK_ENDIAN__
 diff --git a/drivers/net/wireless/ath/dfs_pattern_detector/detector_elem.c
 b/drivers/net/wireless/ath/dfs_pattern_detector/detector_elem.c new file
 mode 100644
 index 000..ea5ae34
 --- /dev/null
 +++ b/drivers/net/wireless/ath/dfs_pattern_detector/detector_elem.c
 @@ -0,0 +1,92 @@
 +/*
 + * Copyright (c) 2012 Neratec Solutions AG
 + *
 + * Permission to use, copy, modify, and/or distribute this software for
 any + * purpose with or without fee is hereby granted, provided that the
 above + * copyright notice and this permission notice appear in all
 copies. + *
 + * THE SOFTWARE IS 

Re: [ath9k-devel] change the ACK response time

2011-12-15 Thread David Goodenough
On Thursday 15 Dec 2011, subham das wrote:
 Hello Everyone,
   I would like to know how to change the ACK response time, RTS
 threshold value, Fragmentation threshold value on my Atheros ar928x chip. I
 am using Ubuntu-11.04 on my Laptop (Dell Inspiron 1525). I am connecting my
 laptop with a high gain directional antenna to connect to another machine
 at around 1-3 km distance. I think i would like to change the ACK response
 time. But how would i do that, can it done using iw, if yes then how and
 if not then what else to try and how.
 
 Please reply,
 Thanking you.
with iw you can set the distance, which under the covers equates to the
ACK time.  Its in the help, at least for current versions of iw.

David
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] (no subject)

2011-10-15 Thread David Goodenough
On Saturday 15 Oct 2011, sekharjyoti deka wrote:
 Thanx Adrian,
 
 For your valuable reply. but i was concentrating on modification of
 some sort of parameters like changing of slot timing and also the ack
 time to get maximal throughput of the network..Since i am trying to
 modify ath9k for long distance network like it should cover a distance
 about 3-4km with directional antenna( as wifi only covers upto 50m in
 default).. So this is my point. So if you can help me in modifying the
 code and also if you can provide some materials related it it'll be
 highly appreceated..
 
 
 your's sincerely
 Sekharjyoti
 ___
 ath9k-devel mailing list
 ath9k-devel@lists.ath9k.org
 https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Support for this already exists:-

iw phy phyname set distance distance

No need to change anything.

David
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] Wireless Card

2011-09-15 Thread David Goodenough
On Thursday 15 Sep 2011, Alex Hacker wrote:
 pci-e 3 antenna
that finds me lots of pcie wireless adapters, but no mini-pci to pcie
converters.

David
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] Wireless Card

2011-09-14 Thread David Goodenough
On Tuesday 13 Sep 2011, Adrian Chadd wrote:
 .. if in doubt:
 
 * buy a mini-PCIe - PCIe adaptor card off of ebay. They typically
 come with three antennas already.
Can you provide a pointer to one of these.  I tried searching ebay for
a minipci to pcie adapter and got zero items found.

David
 * buy one of the AR9280 (or later as Mohammed mentioned) NICs off of
 ebay that are dual-band. There's lots of them, many  $30.
 
 
 
 Adrian
 ___
 ath9k-devel mailing list
 ath9k-devel@lists.ath9k.org
 https://lists.ath9k.org/mailman/listinfo/ath9k-devel

___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] 'Superchannel'?

2011-08-28 Thread David Goodenough
On Sunday 28 Aug 2011, Adrian Chadd wrote:
 Guys (and girls, and fuzzy others..)
 
 I'll do some poking of my atheros contacts and see what can be found.
 Alex/Alex/Jerry, please follow up with me privately.
 
 
 
 Adrian
 ___
 ath9k-devel mailing list
 ath9k-devel@lists.ath9k.org
 https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Could I make a request.

One of the things that would be useful as a result of doing this work
would a standard way for people with licences to extend the range as
defined by CRDA.  In the case discussed here it is a HAM licence for
frequencies below 2.4GHz, in my case the area of interest is what is
known as Band C here in the UK at 5.8GHz.  You do need a licence (£1
per station per year to a minimum of £50 per year) from Ofcom (our FCC)
but it is easy to obtain.  The 5.8 band users are also allowed more
power than you would be in the normal 802.11a band.

Once that standard way (preferably without rebuilding the kernel) has
been defined it should be made public with lots of caviats written 
around it saying that this can only be used if you posess a licence 
and that you are personally liable for its misuse.

David
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel