linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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: Sun, 16 Oct 2005 10:17:59 +0200	[thread overview]
Message-ID: <20051016081759.GA2609@Redstar.dorchain.net> (raw)
In-Reply-To: <1129327105.21765.39.camel@gaston>

[-- Attachment #1: Type: text/plain, Size: 615 bytes --]

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.
> 
> Usually, to debug those crashes, I'm adding a hack to kernel/printk.c to
> call btext_drawstring() (with some test to make sure to do that not too
> early, typically only after setup_arch has been called).

Thanks,

Joerg

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-10-16  8:24 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 [this message]
2005-10-16  8:42     ` Benjamin Herrenschmidt
2005-10-17 18:34       ` Joerg Dorchain
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=20051016081759.GA2609@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).