From: Patrick Williams <patrick@stwcx.xyz>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Request for Feedback :: Time Mode setting in timemanager
Date: Tue, 18 Feb 2020 15:51:28 -0600 [thread overview]
Message-ID: <20200218215128.GF2219@patrickw3-mbp.lan.stwcx.xyz> (raw)
In-Reply-To: <329B2251-4BA2-425F-A8E1-886C4E2F686F@fuzziesquirrel.com>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
On Tue, Feb 18, 2020 at 04:01:00PM -0500, Brad Bishop wrote:
>
> >>> Please could you help with your thoughts on this ?.. What is the Industry norm on this ?
> >>
> >> FWIW on our (IBM) system designs we usually hook an RTC up to the BMC, and any host software needing a RTC has to get it via some in-band software interface. I think I heard somewhere though that often in other systems designs the RTC is connected to the host processors and the BMC doesn’t have access to it.
> >
> > FB's OCP designs all have the RTC to the Host, so I'm not sure any of
> > this is applicable to us.
>
> Are there any down sides to designs like this? I guess if NTP is not an option on the BMC, you are at the mercy of the host firmware if you want correct time. If NTP is in use on the BMC does an RTC still do anything for you?
There are times that the BMC doesn't know what time it is and reverts
back to 1970. At least until the network and NTP are up again. I'm not
sure the history at why we arrived at this design, honestly.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-18 21:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 12:56 Request for Feedback :: Time Mode setting in timemanager Vishwanatha Subbanna
2020-02-18 14:40 ` Brad Bishop
2020-02-18 16:46 ` Ryan Arnell
2020-02-18 20:25 ` Patrick Williams
2020-02-18 20:34 ` Brad Bishop
2020-02-18 20:52 ` Patrick Williams
2020-02-18 21:01 ` Brad Bishop
2020-02-18 21:48 ` Patrick Williams
2020-02-18 21:01 ` Brad Bishop
2020-02-18 21:51 ` Patrick Williams [this message]
2020-02-19 6:37 ` Vishwanatha Subbanna
2020-02-20 16:33 ` Patrick Williams
2020-02-24 6:08 ` Vishwanatha Subbanna
2020-02-24 20:36 ` Patrick Williams
2020-02-25 2:01 ` Lei YU
2020-02-25 2:23 ` Patrick Williams
2020-04-27 10:34 ` Vishwanatha Subbanna
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=20200218215128.GF2219@patrickw3-mbp.lan.stwcx.xyz \
--to=patrick@stwcx.xyz \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.