From: Chuck Ebbert <76306.1226@compuserve.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>, Peter Osterlund <petero2@telia.com>
Subject: Re: 2.6.14-rc1 on ATI hangs when executing _STA and _INI methods
Date: Fri, 16 Sep 2005 19:36:24 -0400 [thread overview]
Message-ID: <200509161938_MC3-1-AA5F-2E2A@compuserve.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509141521370.26803@g5.osdl.org>
On Wed, 14 Sep 2005 at 15:27:19 -0700 (PDT), Linus Torvalds wrote:
> > [PATCH] x86-64: i386/x86-64: Fix time going twice as fast problem on ATI Xpress chipsets
> >
> > Passing enable_timer_pin_1 as a kernel boot parameter doesn't help,
> > but this patch does:
>
> Ok. That patch has been one big pain, and was clearly totally half-baked.
> I think I'll disable the automated checks, since they are clearly wrong.
Well I never meant it to be merged, but Andi picked it up from Bugzilla
bug #3927, added some bugs of his own, then sent it on.
This bug was mine, though: just checking for vendor == ATI was a bad idea.
Current earlyquirk code actually looks at PCI bridges instead of host bridge,
so to get an accurate test I guess it needs to look at PCI dev 00:00.0 and
check both vendor and device ID. As new models come out they will have to
be added one by one.
With a real understanding of what's going on maybe this problem can be solved
reliably with generic code, but it's beyond me...
__
Chuck
Subliminal URL: www.sluggy.com/daily.php?date=050905
next reply other threads:[~2005-09-16 23:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 23:36 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-13 3:34 "Read my lips: no more merges" - aka Linux 2.6.14-rc1 Linus Torvalds
2005-09-14 22:11 ` 2.6.14-rc1 on ATI hangs when executing _STA and _INI methods Peter Osterlund
2005-09-14 22:27 ` Linus Torvalds
2005-09-14 22:41 ` Peter Osterlund
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=200509161938_MC3-1-AA5F-2E2A@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--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
all inboxes | Powered by JetHome®