mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "rae l" <crquan@gmail.com>
To: "David Brownell" <david-b@pacbell.net>
Cc: rtc-linux@googlegroups.com,
	"Luca Tettamanti" <kronos.it@gmail.com>,
	"Linux Kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: Does the kernel HPET support has problems or the hwclock from util-linux?
Date: Fri, 6 Jul 2007 10:06:37 +0800	[thread overview]
Message-ID: <91b13c310707051906l94be14u795a058bd838ef3d@mail.gmail.com> (raw)
In-Reply-To: <200707032302.52612.david-b@pacbell.net>

On 7/3/07, Luca Tettamanti <kronos.it@gmail.com> wrote:
> rae l <crquan@gmail.com> ha scritto:
> > from this address, I know util-linux-2.12r is the latest:
> > http://www.kernel.org/pub/linux/utils/util-linux/util-linux-2.12r.lsm
> >
> > My Dell OptiPlex 320 has 4 HPET timers and no RTC, so the execution of
> > hwclock has errors:
> >
> > gektop@tux ~ $ /sbin/hwclock --show
> > select() to /dev/rtc to wait for clock tick timed out
> > gektop@tux ~ $ /sbin/hwclock --version
> > hwclock from util-linux-2.12r
>
> I think that the problem is that HPET and the CMOS RTC (list in CC)
> share the same interrupt line.
> I suppose that you should enable CONFIG_HPET_RTC_IRQ (my hardware has
> the same "feature"); in this way /dev/rtc correcly reports that it
> cannot deliver the interrupt (when HPET is enabled) and hwclock uses
> direct ISA access.
I searched the CONFIG_HPET_RTC_IRQ, it's conflict with
HPET_EMULATE_RTC, that I've enabled.
so while HPET_RTC_IRQ is the good way, EMULATE_RTC is a bad way.

>
> Luca
> --
> Windows NT crashed.
> I'm the Blue Screen of Death.
> No one hears your screams.
>


-- 
Denis Cheng
Linux Application Developer

  reply	other threads:[~2007-07-06  2:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04  6:02 David Brownell
2007-07-06  2:06 ` rae l [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-02 10:15 rae l
2007-07-02 10:21 ` Ismail Dönmez
2007-07-02 20:13 ` Luca Tettamanti

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=91b13c310707051906l94be14u795a058bd838ef3d@mail.gmail.com \
    --to=crquan@gmail.com \
    --cc=david-b@pacbell.net \
    --cc=kronos.it@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.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

all inboxes | Powered by JetHome®