From: Ralph Siemsen <ralphs@netwinder.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Martin Michlmayr <tbm@cyrius.com>,
Woody Suwalski <woodys@xandros.com>,
linux-fbdev-devel@lists.sourceforge.net,
debian-arm@lists.debian.org
Subject: Re: 2.6.16-rc3 + Xorg 6.9.0 - works for me...
Date: Thu, 27 Apr 2006 08:23:07 -0400 [thread overview]
Message-ID: <4450B7AB.70904@netwinder.org> (raw)
In-Reply-To: <20060427115353.GA30095@flint.arm.linux.org.uk>
Russell King wrote:
> And under 2.6, does clearing this burst bit solve your problem?
Yes, I have confirmed this behaviour. Clearing the burst flag makes the
2010 work for me. I tried all other sorts of changes, like going back
to the "OLD_PLL" code and similar, but none had any effect, except for
the burst flag.
RMK, its worth noting that "2.4" in the previous conversation was
referring to 2.4.19-rmk7, so that may explain why it was working there.
So is it a 2010 bug? Seems unlikely...
-R
PS. I am still seeing X crash after a few hours running x11perf, now
with both 2.4 and 2.6 framebuffers. Its easily reproduced, but without
any debugging symbols in the X binary, I'm not sure how useful a gdb
backtrace would be...
next prev parent reply other threads:[~2006-04-27 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43F4AF97.8080909@xandros.com>
[not found] ` <443E3A4B.8000101@netwinder.org>
[not found] ` <443E4435.1060904@xandros.com>
[not found] ` <443F8EB1.30803@netwinder.org>
2006-04-26 18:38 ` 2.6.16-rc3 + Xorg 6.9.0 - works for me Woody Suwalski
2006-04-26 20:09 ` Russell King
2006-04-26 20:15 ` Woody Suwalski
2006-04-27 11:48 ` Martin Michlmayr
2006-04-27 11:53 ` Russell King
2006-04-27 11:59 ` Martin Michlmayr
2006-04-27 12:23 ` Ralph Siemsen [this message]
2006-04-27 12:32 ` Woody Suwalski
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=4450B7AB.70904@netwinder.org \
--to=ralphs@netwinder.org \
--cc=debian-arm@lists.debian.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=rmk@arm.linux.org.uk \
--cc=tbm@cyrius.com \
--cc=woodys@xandros.com \
/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.