From: Horms <horms@verge.net.au>
To: Paul Gortmaker <p_gortmaker@yahoo.com>
Cc: linux-kernel@vger.kernel.org, 277298@bugs.debian.org
Subject: Re: RTC problem on 8208CA
Date: Thu, 5 May 2005 12:34:49 +1000 [thread overview]
Message-ID: <20050505023447.GB3988@verge.net.au> (raw)
In-Reply-To: <20050504032541.58650.qmail@web60513.mail.yahoo.com>
On Tue, May 03, 2005 at 08:25:41PM -0700, Paul Gortmaker wrote:
> At a glance this sounds like the case of having the HPET enabled causes
> the RTC IRQ functionality to become crippled or non-functional. The
> concept of hwclock using alarm or similar to handle broken and
> misconfigured hardware is a sensible idea.
Thanks for the advice. I guess I was holding onto an idea
that it could be fixed in the kernel - but you are right,
the user-space work around is a simple solution to this
buggy hardware.
--
Horms
prev parent reply other threads:[~2005-05-05 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 5:16 Horms
2005-05-04 3:25 ` Paul Gortmaker
2005-05-05 2:34 ` Horms [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=20050505023447.GB3988@verge.net.au \
--to=horms@verge.net.au \
--cc=277298@bugs.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p_gortmaker@yahoo.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®