From: "Jónatan Muñoz" <jmunoz@umh.es>
To: <linux-wireless@vger.kernel.org>
Subject: [ath9k]: Beaconing process in ad-hoc mode
Date: Thu, 5 Aug 2010 13:55:05 +0200 [thread overview]
Message-ID: <002c01cb3495$0ff49610$2fddc230$@es> (raw)
Dear All,
I am working in a project where I need to modified the currently beaconing
system for adhoc mode in ath9k, what I want to achieve is that each station
in an adhoc network send periodically a beacon. As I know, when a station in
the network receives a beacon before sending its own beacon, cancels the
transmission, updates its hw tsf based on the received beacon and waits for
a chance to send the beacon during next TBTT.
For my goal, I think that I should comment the part where the transmission
of the beacon is cancelled. In this way, each station will send a beacon
each 100TU (~100 ms). I know that this mean a increased traffic load on the
network, but it is so much important for the project to obtain a beacon for
each station each 100ms.
Right now, I am looking at the source code of ath9k, I am trying to modify
the file beacon.c, but I dont find the way to get my purpose. Could anyone
help me to find the right place at the code that I have to modify? I am a
bit lost and any help would be greatly appreciated.
Thanks in advance.
PD: Please excuse my poor English
John
------------------------------------------
Jónatan Muñoz
Email: jmunoz@umh.es
Ubiquitous Wireless Communications Research Laboratory
Uwicore, http://www.uwicore.umh.es
Signal Theory and Communications Division
University Miguel Hernández of Elche
Avenida de la Universidad s/n
Edificio Quorum V P2 012
03202, Elche (Alicante)
Spain
Tel: +34 96522 2031 /+34 669256708
Fax: +34 96665 8903
------------------------------------------
next reply other threads:[~2010-08-05 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 11:55 Jónatan Muñoz [this message]
2010-08-05 13:45 ` [ath9k]: Beaconing process in ad-hoc mode John W. Linville
2010-08-06 10:48 ` Jónatan Muñoz
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='002c01cb3495$0ff49610$2fddc230$@es' \
--to=jmunoz@umh.es \
--cc=linux-wireless@vger.kernel.org \
/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