From: Nish Aravamudan <nish.aravamudan@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Moritz Muehlenhoff <jmm@inutil.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.12-rc2
Date: Thu, 7 Apr 2005 17:44:23 -0700 [thread overview]
Message-ID: <29495f1d05040717445728af5@mail.gmail.com> (raw)
In-Reply-To: <1112913902.9568.304.camel@gaston>
On Apr 7, 2005 3:45 PM, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> On Thu, 2005-04-07 at 11:54 -0700, Nish Aravamudan wrote:
> > On Apr 7, 2005 10:50 AM, Moritz Muehlenhoff <jmm@inutil.org> wrote:
> > > Benjamin Herrenschmidt wrote:
> > > > > 1. When resuming from S3 suspend and having switched off the backlight
> > > > > with radeontool the backlight isn't switched back on any more.
> > > >
> > > > I'm not sure what's up here, it's a nasty issue with backlight. Can
> > > > radeontool bring it back ?
> > >
> > > Before suspending I power down the backlight with "radeontool light off"
> > > and with 2.6.11 the display is properly restored. With 2.6.12rc2 the
> > > backlight remains switched off and if I switch it on with radeontool it
> > > becomes lighter, but there's still no text from the fbcon, just the blank
> > > screen.
> >
> > FWIW, I have the same problem on a T41p with 2.6.11 and 2.6.12-rc2,
> > except that neither returns from suspend-to-ram with video restored on
> > the LCD. I believe I was able to get video restored on an external CRT
> > in either 2.6.12-rc2 or 2.6.12-rc2-mm1, but the LCD still didn't
> > restore (can verify later today, if you'd like). I had dumped out the
> > radeontool regs values before & after the sleep, in case they help.
> > They are attached.
> >
> > I posted these problems in the "Call for help S3" thread, but no one responded.
>
> I would say the different value in LVDS_GEN_CNTL explains it. I'll see
> if I can force radeonfb to save/restore this.
Great! That seemed odd to me, as well. I'll be more than happy to try
any patches (I'll take a look at the code tonight myself).
Thanks,
Nish
next prev parent reply other threads:[~2005-04-08 0:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0504040945100.32180@ppc970.osdl.org>
2005-04-04 21:32 ` Linux 2.6.12-rc2 Linus Torvalds
2005-04-04 22:58 ` Andres Salomon
2005-04-04 23:04 ` Andres Salomon
2005-04-04 23:07 ` Andres Salomon
2005-04-04 23:24 ` Al Viro
2005-04-04 23:49 ` Russell King
2005-04-04 23:54 ` Al Viro
2005-04-04 23:37 ` Stephen Rothwell
2005-04-04 23:54 ` Al Viro
2005-04-05 4:54 ` Gene Heskett
2005-04-06 17:14 ` Moritz Muehlenhoff
2005-04-06 22:42 ` Benjamin Herrenschmidt
2005-04-07 17:50 ` Moritz Muehlenhoff
2005-04-07 18:54 ` Nish Aravamudan
2005-04-07 22:45 ` Benjamin Herrenschmidt
2005-04-08 0:44 ` Nish Aravamudan [this message]
2005-04-08 6:28 ` AsterixTheGaul
2005-04-08 6:39 ` AsterixTheGaul
2005-04-08 7:00 ` AsterixTheGaul
2005-04-08 15:39 ` Nish Aravamudan
2005-04-08 18:14 ` AsterixTheGaul
2005-04-07 22:43 ` Benjamin Herrenschmidt
2005-05-26 4:56 ` Andrew Morton
2005-05-26 5:14 ` Benjamin Herrenschmidt
2005-05-26 10:45 ` Moritz Muehlenhoff
2005-04-05 7:29 Oleg Nesterov
2005-04-05 8:03 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2005-04-05 14:56 Hubert Tonneau
2005-04-06 23:20 Bob Gill
2005-04-06 23:25 ` Dave Jones
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=29495f1d05040717445728af5@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=jmm@inutil.org \
--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 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.