public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luca Tettamanti <kronos.it@gmail.com>
To: rae l <crquan@gmail.com>
Cc: rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
	Adrian Bunk <bunk@stusta.de>
Subject: Re: Does the kernel HPET support has problems or the hwclock from util-linux?
Date: Mon, 2 Jul 2007 22:13:54 +0200	[thread overview]
Message-ID: <20070702201354.GA13313@dreamland.darkstar.lan> (raw)
In-Reply-To: <91b13c310707020315v54d19338u817d23d4380bde07@mail.gmail.com>

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.

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

  parent reply	other threads:[~2007-07-02 20:13 UTC|newest]

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

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=20070702201354.GA13313@dreamland.darkstar.lan \
    --to=kronos.it@gmail.com \
    --cc=bunk@stusta.de \
    --cc=crquan@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