From: "John W. Linville" <linville@tuxdriver.com>
To: "Jónatan Muñoz" <jmunoz@umh.es>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [ath9k]: Beaconing process in ad-hoc mode
Date: Thu, 5 Aug 2010 09:45:31 -0400 [thread overview]
Message-ID: <20100805134531.GA2779@tuxdriver.com> (raw)
In-Reply-To: <002c01cb3495$0ff49610$2fddc230$@es>
On Thu, Aug 05, 2010 at 01:55:05PM +0200, Jónatan Muñoz wrote:
> 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 don’t 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
I think you should be looking in net/mac80211/ibss.c.
Hth!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-08-05 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 11:55 [ath9k]: Beaconing process in ad-hoc mode Jónatan Muñoz
2010-08-05 13:45 ` John W. Linville [this message]
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=20100805134531.GA2779@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.