From: Jon Smirl <jonsmirl@gmail.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.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: Tue, 14 Jun 2005 19:11:13 -0400 [thread overview]
Message-ID: <9e473391050614161117592eb5@mail.gmail.com> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB6004F782CB@scsmsx403.amr.corp.intel.com>
On 6/14/05, Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com> wrote:
> OK. I was thinking PCI fixup is to late in the initialization for
> HPET fixup. But, we should be OK with a new ACPI_FIXUP macro. My only
> other concern is, we should safely fallback to PIT, when our fixed_up
> HPET address isn't right.
If we're keying off from the PCI ID for the chip, how can it not have
the device? On the other hand, it would probably be good to always do
a little test on the HPET and fall back to the PIT if the HPET is
dead.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-06-14 23:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 22:37 Fwd: hpet patches Pallipadi, Venkatesh
2005-06-14 23:11 ` Jon Smirl [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 23:16 Pallipadi, Venkatesh
2005-06-14 23:36 ` Jon Smirl
2005-06-15 0:51 ` Andi Kleen
[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=9e473391050614161117592eb5@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=akpm@osdl.org \
--cc=bob.picco@hp.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