From: Richard Cochran <richardcochran@gmail.com>
To: "Greenman, Gregory" <gregory.greenman@intel.com>
Cc: "kuba@kernel.org" <kuba@kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Stern, Avraham" <avraham.stern@intel.com>
Subject: Re: pull-request: wireless-next-2023-03-30
Date: Wed, 19 Apr 2023 20:43:46 -0700 [thread overview]
Message-ID: <ZEC08ivL3ngWFQBH@hoboy.vegasvil.org> (raw)
In-Reply-To: <ccc046c7e7db68915447c05726dd90654a7a8ffc.camel@intel.com>
On Tue, Apr 18, 2023 at 01:35:50PM +0000, Greenman, Gregory wrote:
> Just a few clarifications. These two notifications are internal to iwlwifi, sent
> by the firmware to the driver.
Obviously.
> Then, the timestamps are added to the rx/tx status
> via mac80211 api.
Where? I don't see that in the kernel anywhere.
Your WiFi driver would need to implement get_ts_info, no?
> Actually, we already have a functional implementation of ptp4l
> over wifi using this driver support.
Why are changes needed to user space at all?
Thanks,
Richard
next prev parent reply other threads:[~2023-04-20 3:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 20:56 pull-request: wireless-next-2023-03-30 Johannes Berg
2023-03-31 7:06 ` Jakub Kicinski
2023-04-03 22:45 ` Richard Cochran
2023-04-13 3:33 ` Richard Cochran
2023-04-18 13:35 ` Greenman, Gregory
2023-04-20 3:43 ` Richard Cochran [this message]
2023-04-23 13:33 ` Stern, Avraham
2023-04-24 22:04 ` Richard Cochran
2023-04-25 1:29 ` Richard Cochran
2023-04-25 7:03 ` Stern, Avraham
2023-04-26 2:43 ` Richard Cochran
2023-04-26 14:04 ` Richard Cochran
2023-05-07 16:32 ` Stern, Avraham
2023-03-31 7:10 ` patchwork-bot+netdevbpf
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=ZEC08ivL3ngWFQBH@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=avraham.stern@intel.com \
--cc=gregory.greenman@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).