From: Joerg Dorchain <joerg@dorchain.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: 2.6.13 ati (ibook) frambuffer problem
Date: Mon, 17 Oct 2005 20:34:43 +0200 [thread overview]
Message-ID: <20051017183443.GB28756@Redstar.dorchain.net> (raw)
In-Reply-To: <1129452167.7620.34.camel@gaston>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On Sun, Oct 16, 2005 at 06:42:46PM +1000, Benjamin Herrenschmidt wrote:
> On Sun, 2005-10-16 at 10:17 +0200, Joerg Dorchain wrote:
> > On Sat, Oct 15, 2005 at 07:58:25AM +1000, Benjamin Herrenschmidt wrote:
> > >
> > > This looks like a bug that was introduced by linus in 2.6.13 and that I
> > > _think_ should be fixed in the stable series, so if you get 2.6.13.x (x
> > > = latest stable release) it should work.
> >
> > 2.6.13.4 does not fix it and(, as far as I skimmed it,) contains no
> > changes to the ati framebuffer code.
>
> Hrm... annoying, I was sure it was fixed, I'll have to check. The bug
> isn't actually in the ATI code, but in the PCI code. Well, maybe you are
> hitting something else...
It seems.
>
> The bug I'm thinking about was fixed by git commit
> 6821eb3b64158ec230982f4db5f027b326edd620, here's the patch. Let me know
> if it helps.
This patch is contained in 2.6.13.4. It did not help.
I selected
CONFIG_FB
CONFIG_FB_RADEON
CONFIG_FB_RADEON_I2C
CONFIG_BACKLIGHT_LCD_SUPPORT
FRAMEBUFFER_CONSOLE
The 2.6.12 version worked. Would it make sense to post the complete
.config?
Bye,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-17 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 12:38 2.6.13 ati (ibook) frambuffer problem Joerg Dorchain
2005-10-14 21:58 ` Benjamin Herrenschmidt
2005-10-16 8:17 ` Joerg Dorchain
2005-10-16 8:42 ` Benjamin Herrenschmidt
2005-10-17 18:34 ` Joerg Dorchain [this message]
2005-10-17 21:44 ` Benjamin Herrenschmidt
2005-10-18 8:49 ` Joerg Dorchain
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=20051017183443.GB28756@Redstar.dorchain.net \
--to=joerg@dorchain.net \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).