From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] i386: port ATI timer fix from x86_64 to i386
Date: Tue, 28 Feb 2006 19:03:13 -0500 [thread overview]
Message-ID: <200602281905_MC3-1-B97E-7FDC@compuserve.com> (raw)
In-Reply-To: <20060228152124.616e6c1c.akpm@osdl.org>
On Tue, 28 Feb 2006 15:21:24, Andrew Morton wrote:
> Chuck Ebbert <76306.1226@compuserve.com> wrote:
> >
> > Disable timer routing over 8254 when an ATI chipset is detected
> > (autodetect is only implemented for ACPI, but these are new systems
> > and should be using ACPI anyway.) Adds boot options for manually
> > disabling and enabling this feature. Also adds a note to the timer
> > error message caused by this change explaining that this error
> > is expected on ATI chipsets.
>
> umm, why did you write this patch? Presumably it's fixing something, but
> what?
Oops... I'm here in the middle of the forest and all I can see are trees.
This fixes the "timer runs too fast" bug on ATI chipsets (bugzilla #3927).
--
Chuck
"Equations are the Devil's sentences." --Stephen Colbert
next reply other threads:[~2006-03-01 0:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 0:03 Chuck Ebbert [this message]
2006-03-01 0:15 ` Andrew Morton
2006-03-01 10:40 ` Andi Kleen
2006-03-01 10:52 ` Andrew Morton
2006-03-01 11:07 ` Andi Kleen
2006-03-02 5:02 ` [patch] i386: port ATI timer fix from x86_64 to i386 II Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-03-01 17:10 [patch] i386: port ATI timer fix from x86_64 to i386 Chuck Ebbert
2006-03-01 15:50 Chuck Ebbert
2006-03-01 2:22 Chuck Ebbert
2006-03-01 1:18 Parag Warudkar
2006-02-28 21:17 Chuck Ebbert
2006-02-28 23:21 ` Andrew Morton
2006-03-01 13:59 ` Alistair John Strachan
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=200602281905_MC3-1-B97E-7FDC@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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