All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luciano Coelho <luciano.coelho@intel.com>
To: "Joel Bjurström" <maxxflow@gmail.com>,
	linux-wireless@vger.kernel.org, assaf.krauss@intel.com,
	johannes.berg@intel.com, emmanuel.grumbach@intel.com
Cc: linuxwifi@intel.com
Subject: Re: iwlwifi: ToF usage
Date: Wed, 04 Oct 2017 07:52:21 +0300	[thread overview]
Message-ID: <1507092741.908.56.camel@intel.com> (raw)
In-Reply-To: <d3356a70-b90e-d0cc-6328-17f055b2ed1c@maxxflow.com>

Hi Joel,

Unfortunately we don't have full support for ToF on the mainline kernel
yet.  But you can try to use one of our Core releases (which is a
backports-based tree) that you can find here:

You could try the release/Core30 branch, for example.

--
Cheers,
Luca.

On Thu, 2017-09-21 at 21:35 +0200, Joel Bjurström wrote:
> Including some people I've seen mentioned in ToF-related e-mails...
> 
> This is what I've tried:
> 
> 
> -- Responder --
> 
> * hostapd running, hostapd.conf:
> 	driver=nl80211
> 	interface=wlan1
> 	hw_mode=g
> 	channel=1
> 	wmm_enabled=1
> 	ssid=tof_test
> 	ftm_responder=1
> 	ftm_initiator=1
> 
> $ cd /sys/kernel/debug/iwlwifi/0000:06:00.0/iwlmvm/netdev:wlan1
> $ echo channel_num=1 > tof_responder_params
> $ echo bssid=bb:bb:bb:bb:bb:bb > tof_responder_params
> $ echo rate=1 > tof_responder_params
> $ echo ftm_per_burst=5 > tof_responder_params
> 
> $ echo send_responder_cfg=1 > tof_responder_params
> 
> 
> -- Initiator --
> 
> $ cd /sys/kernel/debug/iwlwifi/0000:06:00.0/iwlmvm/netdev:wlan1
> $ echo send_tof_cfg=1 > tof_enable
> $ echo 'num_of_ap=1' > tof_range_request
> $ echo 'ap=0 1 0 0 bb:bb:bb:bb:bb:bb 0 10 0 5 5 0 0 0 0 -40' \
> 	> tof_range_request
> 
> $ echo 'send_range_request=1' > tof_range_request
> 
> $ cat tof_range_response
> request_id = 0
> status = 2
> last_in_batch = 1
> num_of_aps = 0
> 
> 
> 
> (bb:bb:bb:bb:bb:bb is the responder's BSSID)
> 
> Am I even close? Fumbling in the dark here.
> 
> The 'status = 2' from tof_range_response comes directly from the FW, 
> AFAICT. What do different values mean?
> 
> Cheers,
> Joel
> 
> 
> On 09/14/2017 09:44 PM, Joel B wrote:
> > Hi,
> > 
> > Starting to play around with the FTM/ToF support in iwlwifi, but 
> > documentation is (understandably) scarce at this point. Using a
> > pair of 
> > 8260:s I had lying around.
> > 
> > Can someone give me some hints on how to work the debugfs API for
> > a 
> > successful measurement?
> > 
> > I've set up one card as AP with hostapd (with ftm_responder=1 and 
> > ftm_initiator=1 in hostapd.conf), the other as a STA.
> > 
> >  From the STA, I've played with 'tof_range_request' in debugfs.
> > Writing 
> > send_range_request=1, which it doesn't choke on or anything, but
> > nothing 
> > seems to happen. Guess I need to set things up a bit first, but
> > how?
> > 
> > If it's possible to get this to work at all at this stage, some
> > hints on 
> > how to do it would be great.
> > 
> > 
> > Thanks,
> > Joel

  reply	other threads:[~2017-10-04  4:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 19:44 iwlwifi: ToF usage Joel B
2017-09-21 19:35 ` Joel Bjurström
2017-10-04  4:52   ` Luciano Coelho [this message]
2017-10-11  8:05     ` Luca Coelho

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=1507092741.908.56.camel@intel.com \
    --to=luciano.coelho@intel.com \
    --cc=assaf.krauss@intel.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxwifi@intel.com \
    --cc=maxxflow@gmail.com \
    /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.