From: Patrick Williams <patrick@stwcx.xyz>
To: Richard Hanley <rhanley@google.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"Velumani T-ERS, HCLTech" <velumanit@hcl.com>,
Patrick Williams <patrickw3@fb.com>
Subject: Re: adding sync method in phosphor-time-manager
Date: Tue, 6 Oct 2020 20:38:24 -0500 [thread overview]
Message-ID: <20201007013824.GF6152@heinlein> (raw)
In-Reply-To: <CAH1kD+b=4NhQ=XUmtGXov2WErqLB1T=ZZBYgYBkuVLT=-hdfvw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
On Tue, Oct 06, 2020 at 02:41:29PM -0700, Richard Hanley wrote:
> While we're on the subject, has anyone ever taken a look at using roughtime
> on a BMC? I imagine it could a really valuable extension to
> phosphor-time-manager some time in the future.
> https://blog.cloudflare.com/roughtime/
One of the problems I see is that there are a few different proposals
for "next generation time" protocols beyond NTP. Unless a project
member has an explicit requirement for one of them, it doesn't seem like
we should go out of our way to pick one of them. If someone is
especially interested in implementing one of them in their spare time
though, they're more than welcome.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-10-07 1:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 17:38 adding sync method in phosphor-time-manager Velumani T-ERS,HCLTech
2020-10-06 21:41 ` Richard Hanley
2020-10-07 1:38 ` Patrick Williams [this message]
2020-10-07 17:18 ` Velumani T-ERS,HCLTech
2020-10-07 1:34 ` Patrick Williams
2021-04-08 18:08 ` Alexander Amelkin
2021-04-08 19:36 ` Ed Tanous
2021-04-09 7:26 ` Lei Yu
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=20201007013824.GF6152@heinlein \
--to=patrick@stwcx.xyz \
--cc=openbmc@lists.ozlabs.org \
--cc=patrickw3@fb.com \
--cc=rhanley@google.com \
--cc=velumanit@hcl.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;
as well as URLs for NNTP newsgroup(s).