Re: TOD Clock the same as the BIOS clock in PCs?

In <444BFAE8.6050206@xxxxxxxxxxxxx>, on 04/23/2006
at 06:08 PM, "John S. Giltner, Jr." <giltjr@xxxxxxxxxxxxx> said:

"Any OS can support the hardware clock for the platform it is running
on to be set to local time or UTC."

Where did I imply that a OS can support hardware that is not
there?

The text that you quoted above, because some hardware platforms do not
contain a hardware clock that can be set to either.

I said that it can support what the platform supplies.

You said more than that; you made a claim as to how it could be set.

Again, I stated that OS can support what the platform supplies.

Again, you stated more than that.

So a TOD clock does not supply the time of day?

Red herrings! Get your red herrings while they're fresh. I didn't say
that the TOD clock can't supply the time of day; I said that tw
different pieces of hardware weren't supplying the same function.

However that is one of the functions it does do and that function
can be compared with hardware clocks on other platforms (at least
those platforms that supply hardware clocks).

Only with some of the platforms that supply hardware clocks.

I did go and read the POP and it seems to imply that the TOD clock
only provides the time of day. That there are two other timers
that do the clock comparator and CPU synchronization and that these
three clocks together provide the timer functions for z/Series
hardware.

There are only two timing facilities; CPU and TOD. The clock
comparator compares the value in the TOD clock.

Again, according to the POP, some of the other functions you mention
are not provided by the TOD clock, but by other clocks all
considered part of the mainframe timer facilities.

There is nothing in the PoOps about a third clock.

Is the TOD clock like a RTC/CMOS clock?

Which? The PC has several different timing facilities.

--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.

Relevant Pages

  • Re: Coding style, wait statement, sensitivity list and synthesis.
    ... >> least assume that XST supports this style and create this hardware. ... >>>then the higher precedence clock must be coded first. ... For these very rare dual-edge sensitive register, yes, I think instantiation ... Dual-edge sensitive register elements is not common practice in hardware design. ...
    (comp.lang.vhdl)
  • Re: [PATCH 06/23 -v8] handle accurate time keeping over long delays
    ... which is the same as the underlying hardware counter. ... So you are saying that you can trivally make it work with a clock that is, ... will never change while I am in the preempt disabled code. ... it's called from an IPI running on each CPU. ...
    (Linux-Kernel)
  • Re: Using different timebase for ntpd
    ... modified Ethernet devices to support hardware time stamping. ... was doing hardware gated ntp packets in the 90s. ... hardware timestamping is available from us. ... software timestamping using a hardware clock. ...
    (comp.protocols.time.ntp)
  • Re: Coding style, wait statement, sensitivity list and synthesis.
    ... Or they decided collectively not to implement the double-edge hardware feature to was that 1076.6 recommended it. ... there is a standard for coding styles? ... modeling the IBM style separate master-slave register hardware, which also allowed some pretty exotic scan/functional clock designs. ... In a design review, I require all multiple clock and clock ...
    (comp.lang.vhdl)
  • Re: beginner synthesize question - my debounce process wont synthesize.
    ... for the clock edge from the if for the enabling condition. ... but rather use it to describe hardware. ... mycount:= mycount + ... Now my process only does something on a RISING edge of the clock ...
    (comp.arch.fpga)