From: Andi Kleen <ak@muc.de>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Bob Picco <bob.picco@hp.com>, Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: hpet patches
Date: Wed, 15 Jun 2005 02:51:55 +0200 [thread overview]
Message-ID: <m1slzka1ck.fsf@muc.de> (raw)
In-Reply-To: <9e47339105061416365f4cd1eb@mail.gmail.com> (Jon Smirl's message of "Tue, 14 Jun 2005 19:36:42 -0400")
Jon Smirl <jonsmirl@gmail.com> writes:
> On 6/14/05, Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com> wrote:
>> HPET device itself can be there. But, it can appear in different
>> addresses. Most commonly used address is 0xfed00000. But, it can be
>> different as well.
>
> Does Intel build different versions of something like an 82801EB with
> the HPET at different addresses and still have the same part number?
Sometimes the address can be configured in the chipset and HPET also
be disabled. So the only reliable way would be to check the chipset
registers for each chipset. Unfortunately some are undocumented
(e.g. i've been trying to figure that out for Nvidia for quite some time
to no avail :/)
-Andi
next prev parent reply other threads:[~2005-06-15 0:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 23:16 Fwd: hpet patches Pallipadi, Venkatesh
2005-06-14 23:36 ` Jon Smirl
2005-06-15 0:51 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-15 17:15 Pallipadi, Venkatesh
2005-06-15 17:54 ` Jon Smirl
2005-06-15 18:11 ` Lee Revell
2005-06-16 14:00 ` Vitezslav Samel
2005-06-14 22:37 Pallipadi, Venkatesh
2005-06-14 23:11 ` Jon Smirl
[not found] <88056F38E9E48644A0F562A38C64FB6004F77C29@scsmsx403.amr.corp.intel.com>
[not found] ` <9e473391050614092661d665ee@mail.gmail.com>
[not found] ` <20050614164605.GQ3728@localhost.localdomain>
2005-06-14 17:50 ` Jon Smirl
2005-06-14 18:38 ` Bob Picco
2005-06-14 21:51 ` Jon Smirl
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=m1slzka1ck.fsf@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=bob.picco@hp.com \
--cc=jonsmirl@gmail.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