From: Andi Kleen <ak@suse.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <andi@firstfloor.org>,
mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [1/5] Only do century BCD conversion when we know the RTC is BCD
Date: Wed, 13 Feb 2008 14:49:33 +0100 [thread overview]
Message-ID: <47B2F56D.1070004@suse.de> (raw)
In-Reply-To: <alpine.LFD.1.00.0802122130280.12988@apollo.tec.linutronix.de>
Thomas Gleixner wrote:
> On Mon, 11 Feb 2008, Andi Kleen wrote:
>
>>> So the warning comes a bit late :)
>> I suspect if this was wrong before it would not have been noticed
>> because user space hwclock would work around it.
>
> And how exaclty does it work aroalund ? By setting the binary cmos clock
> with BCD values ?
By reading the value directly from CMOS I suppose and checking
the BCD bit and then setting the clock to the correct value [all
theoretical; i have not checked the hwclock code if
it does that or not. It might be wrong. Just a hypothesis.]
-Andi
prev parent reply other threads:[~2008-02-13 13:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 15:16 [PATCH] [1/5] Only do century BCD conversion when we know the RTC is BCD Andi Kleen
2008-02-09 15:16 ` [PATCH] [2/5] Use 2000 offset for 32bit kernels Andi Kleen
2008-02-16 19:24 ` Thomas Gleixner
2008-02-20 10:07 ` Thomas Gleixner
2008-02-20 10:23 ` Andi Kleen
2008-02-09 15:16 ` [PATCH] [3/5] Add warning when RTC clock reports binary Andi Kleen
2008-02-16 19:38 ` Thomas Gleixner
2008-02-09 15:17 ` [PATCH] [4/5] Fix wrong comment Andi Kleen
2008-02-09 15:17 ` [PATCH] [5/5] Enable ACPI extended century handling for 32bit too v2 Andi Kleen
2008-02-16 19:38 ` Thomas Gleixner
2008-02-11 8:30 ` [PATCH] [1/5] Only do century BCD conversion when we know the RTC is BCD Thomas Gleixner
2008-02-11 8:56 ` Andi Kleen
2008-02-11 22:08 ` Thomas Gleixner
2008-02-11 22:15 ` Andi Kleen
2008-02-12 20:36 ` Thomas Gleixner
2008-02-13 13:49 ` Andi Kleen [this message]
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=47B2F56D.1070004@suse.de \
--to=ak@suse.de \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.