All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Christoph Lameter <clameter@sgi.com>,
	linux-kernel@vger.kernel.org, Bob Picco <Robert.Picco@hp.com>,
	venkatesh.pallipadi@intel.com
Subject: Re: device driver for the SGI system clock, mmtimer
Date: Thu, 16 Sep 2004 22:34:51 +0200	[thread overview]
Message-ID: <20040916203451.GA5260@ucw.cz> (raw)
In-Reply-To: <200409161135.52987.jbarnes@engr.sgi.com>

On Thu, Sep 16, 2004 at 11:35:52AM -0700, Jesse Barnes wrote:
> On Thursday, September 16, 2004 11:14 am, Vojtech Pavlik wrote:
> > On Thu, Sep 16, 2004 at 09:09:12AM -0700, Jesse Barnes wrote:
> > > On Thursday, September 16, 2004 9:03 am, Bjorn Helgaas wrote:
> > > > Christoph Lameter wrote:
> > > > > 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.
> > > >
> > > > As far as I can see, drivers/char/hpet.c talks to the same hardware.
> > > > HP sx1000 machines (and probably others) also implement the HPET.
> > >
> > > No, it's different hardware.
> >
> > mmtimer and hpet are the same hardware actually, just a different
> > specification revision, hpet being the newer one.
> 
> Well, the SHub RTC hardware (which mmtimer accesses) isn't really HPET or 
> mmtimer hardware, but I tried to make the mmtimer *API* useful for HPET style 
> hardware.  The idea was to have several drivers supporting the mmtimer API 
> with different hardware underneath.

Sorry, I got confused by the driver name.

> > HPET registers are MMIO so it's in theory possible, while not really
> > useful if you're using it as your system timer as well.
> 
> I don't think anyone does this.

x86-64 does if SMP is enabled and HPET is present.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2004-09-16 20:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 16:03 device driver for the SGI system clock, mmtimer 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 [this message]
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
     [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
2004-09-10 19:54       ` Christoph Lameter
2004-09-11 10:50         ` Christoph Hellwig
2004-09-11 15:32           ` Christoph Lameter

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=20040916203451.GA5260@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=Robert.Picco@hp.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=clameter@sgi.com \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.