mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bob McElrath <bob+linux-kernel@mcelrath.org>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /dev/rtc on alpha
Date: Sun, 9 Nov 2003 09:44:36 -0800	[thread overview]
Message-ID: <20031109174436.GA24812@mcelrath.org> (raw)
In-Reply-To: <20031109142435.A4596@jurassic.park.msu.ru>

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

Ivan Kokshaysky [ink@jurassic.park.msu.ru] wrote:
> On Sat, Nov 08, 2003 at 01:33:57PM -0800, Bob McElrath wrote:
> > Why is the alpha kernel code grabbing the rtc interrupt?  Is it possible
> > it share its use with a user program?  Would reprogramming the interrupt
> > rate by a user program do violence to some internel kernel timing?
> 
> On most Alphas RTC is the system timer (running at 1024 Hz).
> So changing the interrupt rate from user space wouldn't be a good idea.

Then I propose CONFIG_RTC be set to "n" in the arch/alpha files, and the
/dev/rtc driver be disabled on alpha.  There seems to be confusion on
this point in the config files.  CONFIG_RTC is for the /dev/rtc driver.

Since the timer can only be set to powers of 2, it should be possible to
simulate getting the interrupt by calling the rtc.c interrupt handler
every 2^n interrupts...that way the user could program the timer for any
interval less than 1024 Hz.

Cheers,
Bob McElrath [Univ. of California at Davis, Department of Physics]

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-11-09 17:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-08 21:33 Bob McElrath
2003-11-09 11:24 ` Ivan Kokshaysky
2003-11-09 17:44   ` Bob McElrath [this message]
2003-11-09 19:05     ` Geert Uytterhoeven

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=20031109174436.GA24812@mcelrath.org \
    --to=bob+linux-kernel@mcelrath.org \
    --cc=ink@jurassic.park.msu.ru \
    --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

all inboxes | Powered by JetHome®