From: davidm@mostang.com (David Mosberger-Tang)
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "David Mosberger-Tang" <David.Mosberger@acm.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCHSET][2.6-test4][0/6]Support for HPET based timer - Take 2
Date: Fri, 29 Aug 2003 21:59:46 -0700 [thread overview]
Message-ID: <16208.12098.248708.643581@panda.mostang.com> (raw)
In-Reply-To: <C8C38546F90ABF408A5961FC01FDBF1902C7D222@fmsmsx405.fm.intel.com>
>>>>> On Fri, 29 Aug 2003 09:12:52 -0700, "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> said:
Venkatesh> The part of the patch that does the HPET initialization
Venkatesh> for timer interrupt, and general HPET registers
Venkatesh> read/write/programming can be common across
Venkatesh> architectures. However, different archs diverge, when it
Venkatesh> comes to gettimeofday-timer implementation (tsc, pit,
Venkatesh> itc, hpet, ) and we may still have to keep that part
Venkatesh> architecture specific.
Is the time_interpolator interface provided by timex.h sufficient for
HPET timer-interrupt needs? I think It ought to be. If so, perhaps
all that's missing is that x86 needs to be switched over to that
interface?
--david
next prev parent reply other threads:[~2003-08-30 4:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 16:12 [PATCHSET][2.6-test4][0/6]Support for HPET based timer - Take 2 Pallipadi, Venkatesh
2003-08-30 4:59 ` David Mosberger-Tang [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-06 19:04 Pallipadi, Venkatesh
2003-09-07 17:57 ` George Anzinger
2003-08-30 16:26 Pallipadi, Venkatesh
2003-08-29 23:58 Pallipadi, Venkatesh
2003-09-05 22:26 ` George Anzinger
[not found] <pEGJ.73p.5@gated-at.bofh.it>
2003-08-29 3:40 ` David Mosberger-Tang
2003-08-28 23:41 Pallipadi, Venkatesh
2003-08-29 18:23 ` Andrew Morton
2003-08-29 21:03 ` Erik Andersen
2003-08-31 21:05 ` Linus Torvalds
2003-08-31 22:24 ` Erik Andersen
2003-08-31 22:48 ` Linus Torvalds
2003-09-05 22:19 ` George Anzinger
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=16208.12098.248708.643581@panda.mostang.com \
--to=davidm@mostang.com \
--cc=David.Mosberger@acm.org \
--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;
as well as URLs for NNTP newsgroup(s).