From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Moritz Muehlenhoff <jmm@inutil.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] radeonfb: (#2) Implement proper workarounds for PLL accesses
Date: Mon, 11 Apr 2005 08:45:29 +1000 [thread overview]
Message-ID: <1113173129.9568.501.camel@gaston> (raw)
In-Reply-To: <E1DKZJn-0001dN-KQ@localhost.localdomain>
> But it's not specific to X11; I've applied the patch you posted and the
> same symptoms occur for pure tty switching as well, the delay has decreased
> a bit (it's hard to measure, but around a second), but it's still rather
> annoying to work with.
>
> Is it distinguishable which M6 models are buggy? I'm using my X31 for about
> a year now and have probably made some tens of thousands of switches without
> lockups, so presumably not all models cause lockups.
ATI hasn't been very precise about that unfortunately...
Ben.
prev parent reply other threads:[~2005-04-10 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1110519743.5810.13.camel@gaston>
[not found] ` <1110672745.5787.60.camel@gaston>
[not found] ` <je8y3wyk3g.fsf@sykes.suse.de>
[not found] ` <1112743901.9568.67.camel@gaston>
[not found] ` <jeoecr1qk8.fsf@sykes.suse.de>
[not found] ` <1112827655.9518.194.camel@gaston>
[not found] ` <jehdii8hjk.fsf@sykes.suse.de>
[not found] ` <21d7e9970504071422349426eb@mail.gmail.com>
[not found] ` <1112914795.9568.320.camel@gaston>
[not found] ` <jemzsa6sxg.fsf@sykes.suse.de>
2005-04-08 1:19 ` [PATCH] radeonfb: (#2) Implement proper workarounds for PLL accesses Benjamin Herrenschmidt
2005-04-08 21:11 ` Andreas Schwab
2005-04-09 0:03 ` Benjamin Herrenschmidt
2005-04-09 16:24 ` Andreas Schwab
2005-04-09 23:33 ` Benjamin Herrenschmidt
2005-04-10 10:05 ` Moritz Muehlenhoff
2005-04-10 22:45 ` Benjamin Herrenschmidt [this message]
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=1113173129.9568.501.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jmm@inutil.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).