question about rtc command

[Joel Sherrill]

On Mon, Jun 4, 2018 at 9:36 AM, Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> ----- Am 4. Jun 2018 um 16:27 schrieb joel joel at rtems.org:
>
> > On Mon, Jun 4, 2018 at 9:14 AM, Gedare Bloom <gedare at rtems.org> wrote:
> >
> >> Indeed, this 'rtc' shell command seems to be a bit of a misnomer. It
> >> conflates access to two different clocks, the tod and rtc. Probably,
> >> it would be better to provide a separate 'tod' command that
> >> reads/writes the tod values, and refactor this 'rtc' to read/write the
> >> rtc. I'm not quite sure about the correctness of writing to the rtc
> >> without updating the tod, though.
> >>
> >
> > Speaking from RTEMS history here. We tended to use Time of Day
> > to refer to what RTEMS was maintaining and Real-Time Clock to
> > review to battery backed clocks that are ICs. This matches Wikipedia's
> > definition and example of a DS1307.
> >
> > The driver framework in RTEMS is referred to as RTC but some BSPs
> > call the driver TOD and name files and directories accordingly.
> >
> > Renaming TOD drivers to RTC derived names has been on my wish
> > list for a long time.
>
> All the RTC drivers should be now in an "rtc" directory.
>

Great! Did you rename the files at the same time? There were some
todcfg.c files as I recall and other variants.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180604/f90d5965/attachment-0001.html>