[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZEctFm4ZreZ5ToP9@hoboy.vegasvil.org>
Date: Mon, 24 Apr 2023 18:29:58 -0700
From: Richard Cochran <richardcochran@...il.com>
To: "Stern, Avraham" <avraham.stern@...el.com>
Cc: "Greenman, Gregory" <gregory.greenman@...el.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"johannes@...solutions.net" <johannes@...solutions.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: pull-request: wireless-next-2023-03-30
On Mon, Apr 24, 2023 at 03:04:07PM -0700, Richard Cochran wrote:
> On Sun, Apr 23, 2023 at 01:33:19PM +0000, Stern, Avraham wrote:
> > So obviously for ptp4l to support time sync over wifi, it will
> > need to implement the FTM protocol (sending FTM frames via nl80211
> > socket) and use the kernel APIs added here
"obviously" ?
In the past, I made quite some thougts about how to best implement PTP
over Wifi. I may have even written something about it.
In any case, "implement the FTM protocol (sending FTM frames via
nl80211 socket)" was definitely NOT one of the approaches.
Wouldn't it have great to start a discussion before plowing ahead and
hacking something into the kernel?
Oh well.
Thanks,
Richard
Powered by blists - more mailing lists