mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com,
	przemyslaw.kitszel@intel.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Subject: Re: [PATCH net-next 1/2] ptp: add control over HW timestamp latch point
Date: Tue, 22 Oct 2024 19:12:46 -0700	[thread overview]
Message-ID: <ZxhbnvaxmV0njtMu@hoboy.vegasvil.org> (raw)
In-Reply-To: <20241021141955.1466979-2-arkadiusz.kubalewski@intel.com>

On Mon, Oct 21, 2024 at 04:19:54PM +0200, Arkadiusz Kubalewski wrote:
> Currently HW support of PTP/timesync solutions in network PHY chips can be
> implemented with two different approaches, the timestamp maybe latched
> either at the beginning or after the Start of Frame Delimiter (SFD) [1].

Why did 802.3-2012 change the definition of the time stamp position?

Thanks,
Richard

  parent reply	other threads:[~2024-10-23  2:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 14:19 [PATCH net-next 0/2] " Arkadiusz Kubalewski
2024-10-21 14:19 ` [PATCH net-next 1/2] " Arkadiusz Kubalewski
2024-10-21 15:20   ` [Intel-wired-lan] " Paul Menzel
2024-10-22 13:24     ` Kubalewski, Arkadiusz
2024-10-21 22:31   ` Jacob Keller
2024-10-22 14:51     ` Kubalewski, Arkadiusz
2024-10-23  2:12   ` Richard Cochran [this message]
2024-10-23  7:37     ` Kubalewski, Arkadiusz
2024-10-21 14:19 ` [PATCH net-next 2/2] ice: " Arkadiusz Kubalewski
2024-10-21 15:34   ` [Intel-wired-lan] " Paul Menzel
2024-10-22 13:24     ` Kubalewski, Arkadiusz
2024-10-22 13:40   ` Simon Horman
2024-10-22 14:52     ` Kubalewski, Arkadiusz

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=ZxhbnvaxmV0njtMu@hoboy.vegasvil.org \
    --to=richardcochran@gmail.com \
    --cc=aleksandr.loktionov@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.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
all inboxes | Powered by JetHome®