From: Carlos Corbacho <cathectic@slackadelic.com>
To: linux-kernel@vger.kernel.org
Cc: Mikko Tiihonen <mikko.tiihonen@iki.fi>,
Thomas Gleixner <tglx@linutronix.de>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Subject: nVidia HPET force enable - merge requirements? (resend)
Date: Fri, 19 Oct 2007 04:23:31 +0100 [thread overview]
Message-ID: <200710190423.31714.cathectic@slackadelic.com> (raw)
(Resend with CC's fixed)
Back in April, Mikko posted a patch to force enable the HPET on some nVidia
chipsets:
v2:
http://lkml.org/lkml/2007/4/16/46
v3:
http://lkml.org/lkml/2007/4/17/354
What would need to be done to this patch to get it into x86 now (besides i386/
x86_64 -> x86 conversion), given that:
A) There is now a force_hpet boot parameter in the x86 tree (mm branch)
(rather than relying on the solution in the earlier patches of a config
option).
B) On the other hand, the force-quirk's are going into quirks.c, whilst
Mikko's patch requires PCI scanning in early_quirks.c (could the PCI scanning
be done in early_quirks.c and the actual HPET enabling handled in quirks.c
later - or if not, could this early quirk play be made to obey the force_hpet
boot option)?
-Carlos
--
E-Mail: cathectic@gmail.com
Web: strangeworlds.co.uk
GPG Key ID: 0x23EE722D
next reply other threads:[~2007-10-19 3:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 3:23 Carlos Corbacho [this message]
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
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=200710190423.31714.cathectic@slackadelic.com \
--to=cathectic@slackadelic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikko.tiihonen@iki.fi \
--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
Powered by JetHome