From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: andreas.herrmann3@amd.com, mingo@elte.hu, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: enable hpet=force for AMD SB400
Date: Fri, 9 May 2008 16:55:01 -0700 [thread overview]
Message-ID: <20080509165501.a0fdb29d.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0805100140490.3197@apollo.tec.linutronix.de>
On Sat, 10 May 2008 01:42:30 +0200 (CEST)
Thomas Gleixner <tglx@linutronix.de> wrote:
> On Fri, 9 May 2008, Andrew Morton wrote:
> > On Fri, 9 May 2008 11:49:11 +0200
> > Andreas Herrmann <andreas.herrmann3@amd.com> wrote:
> >
> > > x86: enable hpet=force for ATI SB400
> >
> > Sigh.
> >
> > > Add quirk to allow forced usage of HPET on ATI SB400.
> > > I stumbled over machines where HPET is enabled but not reported
> > > by BIOS.
> >
> > Is there no way in which we can probe for or identify this condition,
> > rather than hoping that the user will find out about this boot option?
>
> I'd love to have a sane solution for that, but looking at the rate of
> HPET wreckage since we increased the usage of HPET I'm happy to have
> this as an opt in thingy.
>
Well we don't have to auto-enable the hpet. Simply adding a loud "you
should try the hpet=force option" printk would help a lot of people.
next prev parent reply other threads:[~2008-05-09 23:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 9:49 [PATCH] x86: enable hpet=force for AMD SB400 Andreas Herrmann
2008-05-09 23:37 ` Andrew Morton
2008-05-09 23:42 ` Thomas Gleixner
2008-05-09 23:55 ` Andrew Morton [this message]
2008-05-10 0:02 ` Thomas Gleixner
2008-05-10 20:40 ` Thomas Gleixner
2008-05-11 3:02 ` Alistair John Strachan
2008-05-11 9:03 ` Thomas Gleixner
2008-06-24 16:00 ` Andreas Herrmann
2008-07-04 18:55 ` Andreas Herrmann
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=20080509165501.a0fdb29d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andreas.herrmann3@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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