From: "Ville Syrjälä" <syrjala@sci.fi>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Alexander Kern <alex.kern@gmx.de>
Subject: Re: [patch 1/9] atyfb: Remove FIXME
Date: Sat, 9 Sep 2006 15:39:16 +0300 [thread overview]
Message-ID: <20060909123916.GA12468@sci.fi> (raw)
In-Reply-To: <Pine.LNX.4.62.0609091017450.24057@pademelon.sonytel.be>
On Sat, Sep 09, 2006 at 10:20:25AM +0200, Geert Uytterhoeven wrote:
> On Sat, 9 Sep 2006, Ville [iso-8859-1] Syrj??wrote:
> > > have checked this patches on my RAGE MOBILITY
> > > on top of 2.6.17.11(added with some fuzzies)
> > >
> > > Signed-off-by: Alexander Kern <alex.kern@gmx.de>
> > > for all 9 patches
> > >
> > > Best Wishes
> > > Mit freundlichen Gr?n
> > >
> > > P.S. I would like to iron out the long standing issue on my laptop
> > > I saw about for along time. I can shutdown but reboot. At least TFT goes
> > ^
> > There should be a "not" here, right?
> >
> > > black, leds go off and than nothing. Have you any infos about special
> > > register state for MOBILITY before reboot?
> >
> > No. My OmniBook 500 does the same thing BTW. I can shutdown but reboot
> > just hangs the laptop. I'm guessing the BIOS doesn't like the state in
> > which atyfb leaves the card. The reason I'm thinking it's the BIOS is
> > that my OB6000, which has nearly the same hardware, reboots just fine.
> > I also tried all of the reboot= kernel options but none helped.
> >
> > Maybe we just need to restore some of the original state before reboot.
> > But I don't know if that's even possible. Do drivers get any kind of
> > notification about reboot?
>
> I used to have the same problem (shutdown works, reboot hangs with black
> screen) on my Vaio Z600 (Z505 in US/JP), but recent 2.6 (I use a Debian kernel)
> seems to have this fixed.
Was that with atyfb? My OB500 reboots fine without atyfb.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-09-09 12:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 22:06 [patch 1/9] atyfb: Remove FIXME syrjala
2006-09-03 22:06 ` [patch 2/9] atyfb: Fix compiler warnings syrjala
2006-09-03 22:06 ` [patch 3/9] atyfb: Fix sparse warnings syrjala
2006-09-03 22:06 ` [patch 4/9] atyfb: Fix blanking level transitions syrjala
2006-09-03 22:06 ` [patch 5/9] atyfb: Remove pointless aty_init() argument syrjala
2006-09-03 22:06 ` [patch 6/9] atyfb: Fix __init and __devinit annotations syrjala
2006-09-03 22:06 ` [patch 7/9] atyfb: Remove aty_cmap_regs syrjala
2006-09-03 22:06 ` [patch 8/9] atyfb: Improve atyfb_atari_probe() syrjala
2006-09-04 9:20 ` Geert Uytterhoeven
2006-09-03 22:06 ` [patch 9/9] atyfb: Improve power management syrjala
2006-09-08 22:02 ` [patch 1/9] atyfb: Remove FIXME Alexander Kern
2006-09-09 7:46 ` Ville Syrjälä
2006-09-09 8:20 ` Geert Uytterhoeven
2006-09-09 12:39 ` Ville Syrjälä [this message]
2006-09-10 7:48 ` Geert Uytterhoeven
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=20060909123916.GA12468@sci.fi \
--to=syrjala@sci.fi \
--cc=alex.kern@gmx.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).