From: Andi Kleen <andi@firstfloor.org>
To: Mikko Tiihonen <mikko.tiihonen@iki.fi>
Cc: clemens@ladisch.de, bob.picco@hp.com,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] hpet: Enable hidden HPET on NVidia motherboards
Date: 16 Apr 2007 21:24:46 +0200 [thread overview]
Message-ID: <p734png6s1t.fsf@bingen.suse.de> (raw)
In-Reply-To: <1176708094.22969.7.camel@dual.local>
Mikko Tiihonen <mikko.tiihonen@iki.fi> writes:
> It looks probable that most NVidia chipsets have the HPET address at
> 0x44. It might be possible to enable the HPET even if BIOS did not
That seems like a dangerous assumption. If anything this needs to be keyed
on specific PCI IDs.
And the way you coded a recursive PCI scan is just .... <looking for words, censoring
some that come to mind first> ... not nice.
> initialize it properly by writing the wanted address there. Some other
> pci config space bits might need to be fiddled around too, most likely
> candidates are 0x74 bit 2 and 0xA3 bit ?. One or both of them have been
> identified to change in some motherboards when HPET is enabled/disabled
> in BIOS.
Or just add a random generator and poke random bits? Should be roughly
equivalent.
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)
-Andi
next prev parent reply other threads:[~2007-04-16 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 7:21 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 [this message]
2007-04-16 21:28 ` Mikko Tiihonen
2007-04-16 21:40 ` Andi Kleen
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=p734png6s1t.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--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 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®