From: Andi Kleen <andi@firstfloor.org>
To: Mikko Tiihonen <mikko.tiihonen@iki.fi>
Cc: Andi Kleen <andi@firstfloor.org>,
clemens@ladisch.de, bob.picco@hp.com,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Andy Currid <ACurrid@nvidia.com>
Subject: Re: [PATCH v2] hpet: Enable hidden HPET on NVidia motherboards
Date: Mon, 16 Apr 2007 23:40:42 +0200 [thread overview]
Message-ID: <20070416214042.GB25508@one.firstfloor.org> (raw)
In-Reply-To: <Pine.OSF.4.64.0704162337320.487506@kosh.hut.fi>
On Tue, Apr 17, 2007 at 12:28:31AM +0300, Mikko Tiihonen wrote:
> I actually was more worried that someone might complain that the pci
> scanning is copy & paste code from end of the same file. I did try to use
> the generic pci functions first but because they insist on enabling
> interrupts they cannot be used this early. And this code needs to be run
> before the timer initialization.
Yes that's the issue. You're adding another PCI scanner copy'n'pasted
from the caller of the function you're adding it to. See the problem?
> If you want I can submit a separate patch to move the ... not nice pci
> scanning code to pci directory under some early_pci_scan(u32 *pci_ids,
> hook) function. The same code was already cut&pasted in
That is what early-quirks is anyways. But the way to scan for multple
things is not to add anther recursive scan, but to just extend or
change the main loop.
> >Also there should be done anything here without confirmation from
> >Nvidia that HPET is actually supposed to work. Sometimes hardware
> >is disabled by BIOS because it is seriously broken (there was at least
> >one other chipset that could corrupt your flash if you force enabled
> >HPET in some steppings)
>
> I hope someone has some secret contacts at NVidia because they have not
> been very open with their chipsets. I looked at LinuxBios and their NForce4
> chipset code had just had commented out code that wrote to 0x44 register.
> So obviously something more is needed.
Andy, can you help please? There is interest in force enabling HPET on
boards where the BIOS didn't chose too. We would need a list of PCI-IDs
where this is safe to do and what bits to poke. Thanks.
-Andi
next prev parent reply other threads:[~2007-04-16 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 7:21 [PATCH v2] hpet: Enable hidden HPET on NVidia motherboards Mikko Tiihonen
2007-04-16 11:36 ` Krzysztof Halasa
2007-04-16 13:33 ` Mikko Tiihonen
2007-04-17 11:26 ` Krzysztof Halasa
2007-04-16 19:24 ` Andi Kleen
2007-04-16 21:28 ` Mikko Tiihonen
2007-04-16 21:40 ` Andi Kleen [this message]
2007-04-17 10:13 ` Mikko Tiihonen
2007-04-17 22:18 ` Andi Kleen
2007-04-17 21:57 ` [PATCH v3] hpet: Detect " Mikko Tiihonen
2007-04-20 22:41 ` Andrew Morton
2007-04-21 9:50 ` Andi Kleen
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=20070416214042.GB25508@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ACurrid@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=bob.picco@hp.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikko.tiihonen@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.