From: David Brownell <david-b@pacbell.net>
To: mingo@elte.hu
Cc: rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [patch 2.6.24-rc3] rtc-cmos alarm acts as oneshot
Date: Sat, 01 Dec 2007 00:20:46 -0800 [thread overview]
Message-ID: <20071201082046.554C622A3A6@adsl-69-226-248-13.dsl.pltn13.pacbell.net> (raw)
In-Reply-To: <20071201074400.GA14709@elte.hu>
> Cool. I'm still wondering about:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=7014
>
> basically, we had universally working /dev/rtc before, now it appears we
> dont have it anymore. Or were the problems in this bugzilla present with
> the old code too?
That bug is filed against that legacy /dev/rtc driver, not rtc-cmos.
The submitter hasn't tried the rtc-cmos code, but since the issue
currently appears to be related to using the HPET in "legacy mode"
(what I call "broken mode"), I'd expect similar problems would show
up with the rtc-cmos code too.
- Dave
prev parent reply other threads:[~2007-12-01 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 22:18 [patch 2.6.24-rc3] rtc-cmos alarm acts as oneshot David Brownell
2007-12-01 7:44 ` Ingo Molnar
2007-12-01 8:20 ` David Brownell [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=20071201082046.554C622A3A6@adsl-69-226-248-13.dsl.pltn13.pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).