[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20221202213026.11d898d0@kernel.org>
Date: Fri, 2 Dec 2022 21:30:26 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Horatiu Vultur <horatiu.vultur@...rochip.com>
Cc: <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <davem@...emloft.net>,
<edumazet@...gle.com>, <pabeni@...hat.com>,
<Steen.Hegelund@...rochip.com>, <lars.povlsen@...rochip.com>,
<daniel.machon@...rochip.com>, <richardcochran@...il.com>,
<UNGLinuxDriver@...rochip.com>, <olteanv@...il.com>
Subject: Re: [PATCH net-next v2 0/4] net: lan966x: Enable PTP on bridge
interfaces
On Fri, 2 Dec 2022 08:56:17 +0100 Horatiu Vultur wrote:
> Before it was not allowed to run ptp on ports that are part of a bridge
> because in case of transparent clock the HW will still forward the frames
> so there would be duplicate frames.
> Now that there is VCAP support, it is possible to add entries in the VCAP
> to trap frames to the CPU and the CPU will forward these frames.
> The first part of the patch series, extends the VCAP support to be able to
> modify and get the rule, while the last patch uses the VCAP to trap the ptp
> frames.
This no longer applies, probably the fix from Dan..
Powered by blists - more mailing lists