linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Simon Richter <Simon.Richter@hogyros.de>
To: Alessandro Zummo <azummo-lists@towertech.it>
Cc: linuxppc-dev@ozlabs.org, lm-sensors@lm-sensors.org,
	linuxppc-embedded@ozlabs.org
Subject: Re: [RFC] RTC subsystem
Date: Wed, 21 Dec 2005 17:02:55 +0100	[thread overview]
Message-ID: <43A97CAF.50301@hogyros.de> (raw)
In-Reply-To: <20051221160712.2d322f42@inspiron>

[-- Attachment #1: Type: text/plain, Size: 800 bytes --]

Hello,

Alessandro Zummo wrote:

>   the proposal actually had a fully-working patch attached :)

Ah, didn't see that, as I just skimmed over the web archive page you 
linked to, which has no link to the actual patch (or I'm too stupid to 
find it).

>  In my code, the first rtc that register is bound
>  to /proc/driver/rtc and /dev/rtc (if those interfaces
>  are compiled in, as they are all selectable).

It would be good to have a way to change which clock is the "primary" 
one from userspace later (userspace because this is clearly site policy).

>  You have full control of which functions you will provide
>  to the upper layer. Obivously if you try to set the
>  time on a read-only rtc, you will get an error.

Sure. I was thinking of the question which error that should be.

    Simon

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 307 bytes --]

  reply	other threads:[~2005-12-21 16:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-20 21:00 [RFC] RTC subsystem Alessandro Zummo
2005-12-21 12:18 ` Simon Richter
2005-12-21 15:07   ` Alessandro Zummo
2005-12-21 16:02     ` Simon Richter [this message]
2005-12-21 17:41       ` Alessandro Zummo
2005-12-21 23:18         ` Simon Richter
2005-12-22  6:48           ` Alessandro Zummo
  -- strict thread matches above, loose matches on Subject: below --
2005-12-26 19:22 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=43A97CAF.50301@hogyros.de \
    --to=simon.richter@hogyros.de \
    --cc=azummo-lists@towertech.it \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=lm-sensors@lm-sensors.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;
as well as URLs for NNTP newsgroup(s).