From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, Jesse Barnes <jbarnes@engr.sgi.com>,
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 10:54:51 -0600 [thread overview]
Message-ID: <200409161054.51467.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409160930300.6765@schroedinger.engr.sgi.com>
On Thursday 16 September 2004 10:32 am, Christoph Lameter wrote:
> On Thu, 16 Sep 2004, 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.
>
> The Intel Multimedia Standard is a earlier and different timer spec.
I have a spec that's labelled "IA-PC Multimedia Timers", preliminary
draft of June 2000, revision 0.97, which looks like the one mentioned
in your patch.
I also have something labelled "IA-PC HPET (High Precision Event
Timers) Specification", draft of February 2002, revision 0.98,
which is what drivers/char/hpet.c supports.
I admit I haven't compared them in great detail, but they certainly
*look* like they're close enough that the same driver could support
both, and the 0.98 revision history only mentions fairly cosmetic
changes (like the name :)).
Is there something specific that drivers/char/hpet.c expects that
your hardware doesn't implement?
next prev parent reply other threads:[~2004-09-16 16:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=200409161054.51467.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=Robert.Picco@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 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®