mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Carlos Corbacho <cathectic@slackadelic.com>
Cc: linux-kernel@vger.kernel.org,
	Mikko Tiihonen <mikko.tiihonen@iki.fi>,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: [PATCH] x86: Force enable HPET for CK804 (nForce 4) chipsets
Date: Fri, 19 Oct 2007 19:58:21 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.0.9999.0710191957420.22770@localhost.localdomain> (raw)
In-Reply-To: <200710191851.28639.cathectic@slackadelic.com>

On Fri, 19 Oct 2007, Carlos Corbacho wrote:
> From: Carlos Corbacho <cathectic@gmail.com>
> 
> This patch adds a quirk from LinuxBIOS to force enable HPET on
> the nVidia CK804 (nForce 4) chipset.
> 
> This quirk can very likely support more than just nForce 4
> (LinuxBIOS use the same code for nForce 5), and possibly nForce 3,
> but I don't have those chipsets, so cannot add and test them.
> 
> Tested on an Abit KN9 (CK804).
> 
> Signed-off-by: Carlos Corbacho <cathectic@gmail.com>

Applied. Thanks,

	tglx

  reply	other threads:[~2007-10-19 17:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  3:23 nVidia HPET force enable - merge requirements? (resend) Carlos Corbacho
2007-10-19  6:50 ` Thomas Gleixner
2007-10-19 15:29   ` Carlos Corbacho
2007-10-19 16:19     ` Thomas Gleixner
2007-10-19 17:51       ` [PATCH] x86: Force enable HPET for CK804 (nForce 4) chipsets Carlos Corbacho
2007-10-19 17:58         ` Thomas Gleixner [this message]
2007-10-19 18:07           ` [PATCH] x86: Fix resume for nVidia and force_hpet Carlos Corbacho
2007-10-19 18:15             ` Thomas Gleixner
2007-10-19 18:34               ` x86: Add HPET force support for MCP55 (nForce 5) chipsets Carlos Corbacho

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=alpine.LFD.0.9999.0710191957420.22770@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=cathectic@slackadelic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikko.tiihonen@iki.fi \
    --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®