From: Andi Kleen <ak@suse.de>
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: 01 Mar 2006 11:40:00 +0100 [thread overview]
Message-ID: <p73psl6zbwf.fsf@verdi.suse.de> (raw)
In-Reply-To: <20060228161512.0cdbe560.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> writes:
> Chuck Ebbert <76306.1226@compuserve.com> wrote:
> >
> > This fixes the "timer runs too fast" bug on ATI chipsets (bugzilla #3927).
>
> Wonderful, thanks. What's the relationship (if any) between this and the
> recently-merged x86_64 fix?
He just ported the x86-64 change over without any original authorship
attribution :/
And some less functionality (only works for ACPI now) and some totally
unrelated Documentation cleanup and a few random printk changes.
The ACPI only thing is probably mostly ok because the timing won't work
at least on the dual cores without ACPI anyways because PMtimer is needed.
On single cores it would be useful even without ACPI
(for that earlyquirk.c just would need to be moved up to run independently
of ACPI)
Still it's probably a good idea for 2.6.16.
-Andi
next prev parent reply other threads:[~2006-03-01 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 0:03 [patch] i386: port ATI timer fix from x86_64 to i386 Chuck Ebbert
2006-03-01 0:15 ` Andrew Morton
2006-03-01 10:40 ` Andi Kleen [this message]
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=p73psl6zbwf.fsf@verdi.suse.de \
--to=ak@suse.de \
--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 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.