From: Rohan Joyce <rojoyce.github@gmail.com>
To: johannes@sipsolutions.net
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] nl80211: add NL80211_CMD_GET_TSF
Date: Mon, 23 Feb 2015 23:38:05 +0800 [thread overview]
Message-ID: <1424705885-20987-1-git-send-email-rojoyce.github@gmail.com> (raw)
In-Reply-To: <1424701880.3075.0.camel@sipsolutions.net>
Hi,
The motivation for this patch is to assist using a WiiU Gamepad with Linux.
The WiiU Gamepad is an input device that also contains an LCD touchscreen,
speakers and a variety of sensors. The Gamepad connects to an access
point (usually the WiiU console itself, but it can be coerced to connect
to a properly configured hostap). The Gamepad provides five services over
UDP. Two of the services that are provided (audio and video streaming to
the device) use the TSF as a timestamp in the application layer. The
firmware on the Gamepad checks to make sure that incoming packets for
these services have timestamps within 1000us of its own internal clock,
which is synced to the TSF of the access point.
At the moment, users who want to use this device have to manually apply
a kernel patch similar to that which was first posted to this list a year
ago. This patch is my attempt to implement the functionality using a more
conventional API and make it easier for end users.
Should I include protocol implementation details specific to this device in
the documentation of the NL80211_CMD_GET_TSF command?
Thanks for your time,
Rohan
next prev parent reply other threads:[~2015-02-23 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 13:57 [PATCH 0/1] nl80211: add NL80211_CMD_GET_TSF Rohan Joyce
2015-02-23 13:57 ` [PATCH 1/1] " Rohan Joyce
2015-02-23 14:31 ` Johannes Berg
2015-02-23 15:38 ` Rohan Joyce [this message]
2015-02-24 20:11 ` Johannes Berg
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=1424705885-20987-1-git-send-email-rojoyce.github@gmail.com \
--to=rojoyce.github@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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).