[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <91b13c310707051906l94be14u795a058bd838ef3d@mail.gmail.com>
Date: Fri, 6 Jul 2007 10:06:37 +0800
From: "rae l" <crquan@...il.com>
To: "David Brownell" <david-b@...bell.net>
Cc: rtc-linux@...glegroups.com,
"Luca Tettamanti" <kronos.it@...il.com>,
"Linux Kernel list" <linux-kernel@...r.kernel.org>
Subject: Re: Does the kernel HPET support has problems or the hwclock from util-linux?
On 7/3/07, Luca Tettamanti <kronos.it@...il.com> wrote:
> rae l <crquan@...il.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists