All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair John Strachan <alistair@devzero.co.uk>
To: Andi Kleen <ak@suse.de>
Cc: Nicolas Mailhot <nicolas.mailhot@laposte.net>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc4-mm1
Date: Tue, 4 Sep 2007 17:05:45 +0100	[thread overview]
Message-ID: <200709041705.45670.alistair@devzero.co.uk> (raw)
In-Reply-To: <200709041626.27945.ak@suse.de>

On Tuesday 04 September 2007 16:26:27 Andi Kleen wrote:
> > Seconded. It's been largely ignored which is annoying because the HPET
> > works perfectly on this board. I assume the reason is still that nobody
> > from NVIDIA verified hardward support for the hack.
>
> It's IMHO a bad idea to add any overrides without access to data sheets
> and errata sheets. The hardware might be broken and do bad
> (subtle) bad things with HPET.  That's not a theoretical case.
> There used to be at least one case where a chipset would occasionally
> destroy the BIOS flash when HPET was force enabled.

I haven't used any CK804 with an HPET which is BIOS enabled by default, so 
it's probably most likely that the reference BIOS didn't enable it.

As this technology is quite antiquated, the usual "well Vista uses HPET, so 
maybe vendors will enable it" probably won't apply. I know for my board, no 
BIOS has been released since early 2006.

> That means for Intel it's fine to do (because errata sheets are public);
> but for Nvidia and VIA it's dangerous and should not be done.

I don't disagree with you and I think you're right in the general case, but 
even if we could pin somebody down from NVIDIA (which is seeming unlikely, 
considering the right people have already been CCed), it would still be a 
BIOS override.

In this case,  there's a perfectly good HPET masked behind what I can only 
speculate is a BIOS misfeature (my kernel's behaved itself with Mikko's patch 
applied and Thomas's HRT patchset on x86-64).

What about an expert option which could force the HPET on (rather than "find" 
and enable it)? Are you opposed to this too?

-- 
Cheers,
Alistair.

137/1 Warrender Park Road, Edinburgh, UK.

  reply	other threads:[~2007-09-04 16:07 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-02  2:56 2.6.23-rc4-mm1 Mats Johannesson
2007-09-03  8:06 ` 2.6.23-rc4-mm1 Nicolas Mailhot
2007-09-04 15:20   ` 2.6.23-rc4-mm1 Alistair John Strachan
2007-09-04 15:26     ` 2.6.23-rc4-mm1 Andi Kleen
2007-09-04 16:05       ` Alistair John Strachan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-01  4:58 2.6.23-rc4-mm1 Andrew Morton
2007-09-01  6:53 ` 2.6.23-rc4-mm1 KAMEZAWA Hiroyuki
2007-09-01  6:58   ` 2.6.23-rc4-mm1 Andrew Morton
2007-09-01  8:54     ` 2.6.23-rc4-mm1 Herbert Xu
2007-09-01 21:09       ` 2.6.23-rc4-mm1 Satyam Sharma
2007-09-02  1:46         ` 2.6.23-rc4-mm1 Herbert Xu
2007-09-02  2:52           ` 2.6.23-rc4-mm1 Satyam Sharma
2007-09-02  3:59             ` 2.6.23-rc4-mm1 Herbert Xu
2007-09-01 11:55     ` 2.6.23-rc4-mm1 Kamalesh Babulal
2007-09-01 16:07 ` 2.6.23-rc4-mm1 Torsten Kaiser
2007-09-01 16:16   ` 2.6.23-rc4-mm1 Andrew Morton
2007-09-03  4:30 ` 2.6.23-rc4-mm1 Randy Dunlap
2007-09-03 19:25   ` 2.6.23-rc4-mm1 Wim Van Sebroeck
2007-09-03 22:32     ` 2.6.23-rc4-mm1 Satyam Sharma
2007-09-04 21:21       ` 2.6.23-rc4-mm1 Wim Van Sebroeck
2007-09-04 17:54 ` 2.6.23-rc4-mm1 Zach Carter
2007-09-04 21:36   ` 2.6.23-rc4-mm1 Stephen Hemminger
2007-09-05 14:37 ` 2.6.23-rc4-mm1 Valdis.Kletnieks
2007-09-05 15:12   ` 2.6.23-rc4-mm1 Andrew Morton
2007-09-05 15:20     ` 2.6.23-rc4-mm1 Balbir Singh
2007-09-05 15:58     ` 2.6.23-rc4-mm1 Valdis.Kletnieks
2007-09-09 12:22 ` 2.6.23-rc4-mm1 Mel Gorman
2007-09-10 17:49 ` 2.6.23-rc4-mm1 Andy Whitcroft
2007-09-10 18:19   ` 2.6.23-rc4-mm1 Andrew Morton
2007-09-10 18:59     ` 2.6.23-rc4-mm1 Torsten Kaiser
2007-09-10 19:20       ` 2.6.23-rc4-mm1 Andrew Morton
2007-09-10 19:38         ` 2.6.23-rc4-mm1 Torsten Kaiser
2007-09-10 19:42         ` 2.6.23-rc4-mm1 FUJITA Tomonori
2007-09-10 20:43           ` 2.6.23-rc4-mm1 Torsten Kaiser
2007-09-11  8:32             ` 2.6.23-rc4-mm1 Jens Axboe
2007-09-10 19:10     ` 2.6.23-rc4-mm1 FUJITA Tomonori
2007-09-13 17:34       ` 2.6.23-rc4-mm1 Andy Whitcroft
2007-09-15  4:16       ` 2.6.23-rc4-mm1 Paul Jackson
2007-09-15 10:52         ` 2.6.23-rc4-mm1 FUJITA Tomonori
2007-09-17 13:28           ` 2.6.23-rc4-mm1 Jens Axboe
2007-09-17 14:32             ` 2.6.23-rc4-mm1 FUJITA Tomonori
2007-09-18 10:18               ` 2.6.23-rc4-mm1 Jens Axboe
2007-09-18 12:25                 ` 2.6.23-rc4-mm1 FUJITA Tomonori
2007-09-18 12:51                   ` 2.6.23-rc4-mm1 Jens Axboe
2007-09-10 19:31     ` 2.6.23-rc4-mm1 FUJITA Tomonori
2007-09-14  8:10       ` 2.6.23-rc4-mm1 Andy Whitcroft
2007-09-14 13:01         ` 2.6.23-rc4-mm1 Torsten Kaiser
2007-09-14 20:15           ` 2.6.23-rc4-mm1 Andrew Morton

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=200709041705.45670.alistair@devzero.co.uk \
    --to=alistair@devzero.co.uk \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.mailhot@laposte.net \
    /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.