From: Kalle Valo <kvalo@adurom.com>
To: Pierre Bourdon <delroth@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: Exporting the TSF to userland
Date: Tue, 14 Jan 2014 08:36:36 +0200 [thread overview]
Message-ID: <87k3e3nk7f.fsf@purkki.adurom.net> (raw)
In-Reply-To: <CA+V6dmjoLx90vEwGZa8vRNHp0yWqKQnae+GcvEZHsCxR-oHnhg@mail.gmail.com> (Pierre Bourdon's message of "Mon, 6 Jan 2014 12:37:34 +0100")
Pierre Bourdon <delroth@gmail.com> writes:
> On Mon, Jan 6, 2014 at 12:23 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
>> On Tue, 2013-12-31 at 05:24 +0100, Pierre Bourdon wrote:
>>> Hello linux-wireless,
>>>
>>> I'm a developer of libdrc, a project that allows Linux computers to
>>> control a Wii U GamePad. Because of how the device operates, our
>>> library needs to be able to read the TSF value of the access point
>>> device from userland.
>>>
>>> We currently have a hacky patch that works for our use cases, but it
>>> would be a lot more convenient if that feature could be upstreamed.
>>> What would be the best way to proceed?
>>
>> That patch ... let's say I think "hacky" is almost lauding it. :)
>>
>> sysfs is a really bad place for this too, no other wireless APIs use
>> sysfs.
>
> What do you recommend as the best place to export this kind of information?
Either nl80211 or debugfs. Maybe debugfs is better because this is more
or less a hack?
--
Kalle Valo
next prev parent reply other threads:[~2014-01-14 6:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 4:24 Exporting the TSF to userland Pierre Bourdon
2013-12-31 8:23 ` Kalle Valo
2013-12-31 8:28 ` Pierre Bourdon
2014-01-03 1:07 ` Pierre Bourdon
2014-01-03 11:48 ` David Herrmann
2014-01-06 11:23 ` Johannes Berg
2014-01-06 11:37 ` Pierre Bourdon
2014-01-14 6:36 ` Kalle Valo [this message]
2014-01-14 8:15 ` David Herrmann
2014-01-14 8:26 ` Kalle Valo
2014-01-14 8:34 ` David Herrmann
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=87k3e3nk7f.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=delroth@gmail.com \
--cc=johannes@sipsolutions.net \
--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