public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Vincent C Jones <vcjones@networkingunlimited.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, mpm@selenic.com
Subject: Re: Radeon FB troubles with recent kernels
Date: Tue, 15 Feb 2005 23:50:46 +1100	[thread overview]
Message-ID: <1108471847.10281.3.camel@gaston> (raw)
In-Reply-To: <20050215031441.EFABE1DDFE@X31.nui.nul>


> On my Thinkpad X31 with a Radeon Mobility M6 LY I see a major
> regression going from 2.6.11-rc3 to rc4. With rc-4, the frame
> buffer console (using "video=radeonfb:1024x768-24@60") comes up as
> 640x480 expanded to 1024x768. The inability of ACPI suspend to turn
> off the backlight also returns. Using rc-3, frame buffer console
> works fine and suspend/resume appears to work reliably without
> needing radeontool to turn off the backlight (as long as I do it
> from X.org X).

Ok, this is getting complicated. So far, I'm getting a bit more success
reports that regression reports, so I'm keen to keep this new radeonfb
for 2.6.11...

There are several issues involved

As far as the mode setting is concerned, I'm not sure what's going on
whith your specific model, could you please enable radeonfb debug output
in the kernel config and send me the complete dmesg log ?

As far as the panel blanking is concerned (either during suspend or
normal console blanking), this is a tricky matter. It seems that a bit
of code that works for some panels won't work with others. So far, I
managed to isolate the issue to some panels relying on an inverted
signal out of the chip. I'm in contact with ATI to try to solve that
problem, it might be possible to get proper infos about the type of
panel connected via the BIOS ROM image. Unfortunately, I don't think
I'll get a definitive answer before 2.6.11 is released.

Note that some users have successfully enabled the powerbook/ibook
specific power management code I have in there for thinkpads. I intend t
o merge some of that stuff after 2.6.11 is done.

Ben.



  parent reply	other threads:[~2005-02-15 12:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3xVku-kH-15@gated-at.bofh.it>
2005-02-15  3:14 ` Radeon FB troubles with recent kernels Vincent C Jones
2005-02-15 12:46   ` Benjamin Herrenschmidt
2005-02-15 12:50   ` Benjamin Herrenschmidt [this message]
2005-02-15 12:58     ` sigwait() and 2.6 Yves Crespin
2005-02-15 23:59       ` Ulrich Drepper
2005-02-16 10:08 Radeon FB troubles with recent kernels tvrtko.ursulin
     [not found] <3y1SR-5K6-1@gated-at.bofh.it>
     [not found] ` <3yatk-4mE-29@gated-at.bofh.it>
2005-02-15 15:07   ` Vincent C Jones
2005-02-15 22:02     ` Benjamin Herrenschmidt
2005-02-16  1:53       ` Vincent C Jones
2005-02-16  2:41         ` Benjamin Herrenschmidt
2005-02-16 14:39           ` Vincent C Jones
  -- strict thread matches above, loose matches on Subject: below --
2005-02-14 20:39 Matt Mackall
2005-02-14 22:38 ` Benjamin Herrenschmidt
2005-02-14 23:08   ` Benjamin Herrenschmidt
2005-02-15  0:02     ` Antonino A. Daplas
2005-02-15  0:20     ` Matt Mackall
2005-02-15  1:07       ` Benjamin Herrenschmidt
2005-02-15  6:06         ` Matt Mackall

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=1108471847.10281.3.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=vcjones@networkingunlimited.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox