linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: "ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
	"Chadd, Adrian" <achadd@qca.qualcomm.com>,
	Benoit Papillault <benoit.papillault@free.fr>,
	Felix Fietkau <nbd@openwrt.org>,
	Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
	Christian Lamparter <chunkeey@googlemail.com>
Subject: [ANN] DFS testing: use USRP-Radar-Relay for SDR radar pattern generation
Date: Mon, 25 Jun 2012 12:46:28 +0200	[thread overview]
Message-ID: <4FE84184.4090601@neratec.com> (raw)

Hello DFS folks,

now that DFS support is emerging in linux-wireless, we have quite some
testing ahead.

Testing DFS towards certification at physical layer requires laboratory
equipment that is very expensive (often going into the 6-digit US$
range) and makes it non-affordable for independent developers or smaller
companies.

We evaluated a SDR (software defined radio) approach and found it to be
a very well usable alternative for exorbitant dedicated radar generating
equipment. Our approach uses an Ettus research USRP N200 device to
continuously stream radar patterns as waveforms in the time domain to be
radiated to the attached wiphy.

The SW that abstracts the SDR and the generation of samples for a given
radar pattern is open sourced and available at [1]. With the
'USRP-Radar-Relay' SW and SDR you can have a highly customizable and
flexible radar generating device for less than 2k$ - a definitely lower
barrier to decentralize DFS testing.


Cheers,
Zefir


[1] https://github.com/zefir-kurtisi/USRP-Radar-Relay

                 reply	other threads:[~2012-06-25 10:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FE84184.4090601@neratec.com \
    --to=zefir.kurtisi@neratec.com \
    --cc=achadd@qca.qualcomm.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=benoit.papillault@free.fr \
    --cc=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.org \
    --cc=simon.wunderlich@s2003.tu-chemnitz.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).