mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: device driver for the SGI system clock, mmtimer
Date: Wed, 8 Sep 2004 23:43:21 -0700	[thread overview]
Message-ID: <200409082343.21330.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409082210230.29080@schroedinger.engr.sgi.com>

[resending to lkml just for fun]

On Wednesday, September 8, 2004 8:59 pm, Christoph Lameter wrote:
> SGI has been using this driver under Linux since 2001 in the software
> that they distributed (ProPacks) but it wasnever included in the upstream
> kernel. SuSE did include the patch for mmtimerin SLES 9. The driver has
> been widely used for applications on the Altix platform.
>
> The timer hardware was designed around the multimedia timer specification
> by Intel but to my knowledge only SGI has implemented that standard. The
> driver was written by Jesse Barnes.
>
> Changelog:
>  * Add driver for Altix SHub system clock
> --- linux-2.6.9-rc1.orig/drivers/char/Makefile 2004-09-08
> 20:40:28.000000000 -0700 +++
> linux-2.6.9-rc1/drivers/char/Makefile 2004-09-08 20:40:39.000000000 -0700
> @@ -45,6 +45,7 @@
>  obj-$(CONFIG_HVC_CONSOLE) += hvc_console.o hvsi.o
>  obj-$(CONFIG_RAW_DRIVER) += raw.o
>  obj-$(CONFIG_SGI_SNSC)  += snsc.o
> +obj-$(CONFIG_MMTIMER)         += mmtimer.o
>  obj-$(CONFIG_VIOCONS) += viocons.o
>  obj-$(CONFIG_VIOTAPE)  += viotape.o
>  obj-$(CONFIG_HVCS)  += hvcs.o

Maybe it's just my mailer, but is the indentation in this file all messed up?

> +#ifdef MMTIMER_INTERRUPT_SUPPORT
> +static mmtimer_t timers[] = { { SPIN_LOCK_UNLOCKED, 0, 0,
> +    (unsigned long *)RTC_COMPARE_A_ADDR, 0 },
> +         { SPIN_LOCK_UNLOCKED, 0, 0,
> +    (unsigned long *)RTC_COMPARE_B_ADDR, 0 } };
> +#endif

We may as well kill anything under MMTIMER_INTERRUPT_SUPPORT.  IIRC, people 
use SHub timer interrupts, but not via this driver.  If you want to fix it, 
that's ok too, but you can kill the #ifdef in that case also.

Thanks,
Jesse

  reply	other threads:[~2004-09-09  6:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.58.0409082058140.28678@schroedinger.engr.sgi.com>
     [not found] ` <20040908210537.585120c1.akpm@osdl.org>
2004-09-09  5:12   ` Christoph Lameter
2004-09-09  6:43     ` Jesse Barnes [this message]
2004-09-10 19:54       ` Christoph Lameter
2004-09-11 10:50         ` Christoph Hellwig
2004-09-11 15:32           ` Christoph Lameter
2004-09-16 16:03 Bjorn Helgaas
2004-09-16 16:09 ` Jesse Barnes
2004-09-16 15:52   ` Alan Cox
2004-09-16 17:07     ` Jesse Barnes
2004-09-16 18:17       ` Robert Picco
2004-09-16 18:23         ` Jesse Barnes
2004-09-16 18:00     ` Robert Picco
2004-09-16 16:29   ` Marcello Barnaba
2004-09-16 16:30   ` Christoph Lameter
2004-09-16 18:14   ` Vojtech Pavlik
2004-09-16 18:35     ` Jesse Barnes
2004-09-16 20:34       ` Vojtech Pavlik
2004-09-16 18:46     ` Christoph Lameter
2004-09-20 21:53       ` Bjorn Helgaas
2004-09-16 16:32 ` Christoph Lameter
2004-09-16 16:54   ` Bjorn Helgaas
2004-09-16 18:07     ` Robert Picco
2004-09-16 20:05       ` Christoph Lameter
2004-09-17  1:34         ` Robert Picco
2004-09-16 18:17     ` Vojtech Pavlik

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=200409082343.21330.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --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

Powered by JetHome