public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Alessandro Zummo <alessandro.zummo@towertech.it>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: [patch 2.6.19-rc6 0/6] more rtc framework/driver updates
Date: Mon, 20 Nov 2006 10:14:41 -0800	[thread overview]
Message-ID: <200611201014.41980.david-b@pacbell.net> (raw)

Here are more RTC framework updates, basically for the 2.6.20 queue:

 - /proc/driver/rtc update ... display the 'struct rtc_wkalrm' status
   bits more sensibly (though the EFI "irq pending" flag is nonsense
   with an OS running)

 - rtc-sa1100 update ... wasn't reporting "alarm enabled", and its
   extra procfs info duplicated information already found there

 - X86_PC updates ... create an rtc_cmos platform device when PNPACPI
   isn't available do make one through PNP.  (Non-PC platforms can do
   similar things if they have a "cmos" RTC.)

 - Export ACPI RTC extensions through platform_data to the PNP device
   or the platform device, as appropriate.

 - New "rtc-cmos" driver, for the RTC on most PCs.  For most folk this
   seems like it should be able to replace drivers/char/rtc.c ...

 - Newish "rtc-omap" driver, for the RTC on OMAP1 processors.  No point
   in having this just live in the OMAP tree.

Folk wanting to try "rtc-cmos" will likely be wanting to tweak their
/dev/rtc node to become a symlink to /dev/rtc0, at least until the
new version of util-linux comes out (with updated "hwclock" knowing
about the new RTC class devices).

- Dave


             reply	other threads:[~2006-11-20 22:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 18:14 David Brownell [this message]
2006-11-20 18:17 ` [patch 2.6.19-rc6 1/6] rtc class /proc/driver/rtc update David Brownell
2006-11-20 23:13   ` Alessandro Zummo
2006-11-21  2:47     ` [Bulk] " David Brownell
2006-11-22 20:37       ` Alessandro Zummo
2006-11-23  0:39         ` David Brownell
2006-11-20 18:19 ` [patch 2.6.19-rc6 2/6] rtc-sa1100 tweaks David Brownell
2006-11-20 22:48   ` Russell King
2006-11-21  1:46     ` David Brownell
2006-11-20 18:22 ` [patch 2.6.19-rc6 3/6] X86_PC optionally creates rtc_cmos platform device David Brownell
2006-11-20 18:27 ` [patch 2.6.19-rc6 5/6] rtc-cmos driver David Brownell
2006-11-20 18:27 ` [patch 2.6.19-rc6 4/6] ACPI exports RTC extensions through platform_data David Brownell
2006-11-20 18:28 ` [patch 2.6.19-rc6 6/6] rtc-omap driver David Brownell
2006-11-20 23:09   ` Alessandro Zummo
2006-11-22  1:19   ` Andrew Morton
2006-11-22  2:15     ` David Brownell
2006-11-22  2:28       ` Andrew Morton
2006-11-23  0:09         ` David Brownell
2006-11-22 20:34       ` Alessandro Zummo

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=200611201014.41980.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=alessandro.zummo@towertech.it \
    --cc=linux-kernel@vger.kernel.org \
    /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