public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
To: Venki Pallipadi <venkatesh.pallipadi@intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	Thomas Gleixner <tglx@linutronix.de>, Andi Kleen <ak@suse.de>,
	Ingo Molnar <mingo@elte.hu>, Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 4/8] Force detect and enable HPET on ICH
Date: Mon, 21 May 2007 02:58:22 +0200	[thread overview]
Message-ID: <20070521025822.506c3287@laptop.hypervisor.org> (raw)
In-Reply-To: <20070507203128.GD3926@linux-os.sc.intel.com>

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

On Mon, 7 May 2007 13:31:28 -0700 Venki Pallipadi (VP) wrote:

VP> Force detect and/or enable HPET on ICH chipsets. This patch just handles the
VP> detection part and following patches use this information.
VP> 
VP> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>

Venki,

Is there any reason your patch only enables HPET on ICH6 and beyond? HPET can
be enabled on earlier ICH by setting bit 17 in GEN_CNTL on PCI dev 31, func 0,
offset d0. This seems to work for ICH3/4/5. Are there any errata affecting
these ICHs?

Cheers,

	- Udo

-- 
Dipl.-Inf. Udo Steinberg                     
Technische Universität Dresden               http://os.inf.tu-dresden.de/~us15
Institute for System Architecture            Tel: +49 351 463 38401
D-01062 Dresden                              Fax: +49 351 463 38284

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-21  0:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 20:31 [PATCH 4/8] Force detect and enable HPET on ICH Venki Pallipadi
2007-05-21  0:58 ` Udo A. Steinberg [this message]
2007-05-21 15:46   ` Jesse Barnes
2007-05-21 15:52     ` Pallipadi, Venkatesh
2007-05-21 15:53     ` Udo A. Steinberg

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=20070521025822.506c3287@laptop.hypervisor.org \
    --to=us15@os.inf.tu-dresden.de \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --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