public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tim Stadelmann" <t.stadelmann1-JAjqph6Yjy8XSZKaUYBEcQ@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI on Dell Latitude C600
Date: Sat, 24 Jan 2004 17:09:52 -0000	[thread overview]
Message-ID: <001c01c3e29c$e1f03fe0$03f101a3@physics.ox.ac.uk> (raw)
In-Reply-To: 20040123155820.GA194@elf.ucw.cz


----- Original Message ----- 
From: "Pavel Machek" <pavel-+ZI9xUNit7I@public.gmane.org>

> Video issues with S3 resume
>
> ...
>
> You may have system where none of above works. At that point you
> either invent another ugly hack that works, or write proper driver for
> your video card (good luck getting docs :-(). Maybe suspending from X
> (proper X, knowing your hardware, not XF68_FBcon) might have better
> chance of working.

In other words, software suspend (which has its own problems, and is rather
slow...) is the only chance of getting any kind of suspend mode to work
under Linux on ACPI-only laptops in the forseeable future?



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  reply	other threads:[~2004-01-24 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 17:04 ACPI on Dell Latitude C600 Tim Stadelmann
     [not found] ` <003e01c3e040$ab873700$03f101a3-JAjqph6Yjy8XSZKaUYBEcQ@public.gmane.org>
2004-01-21 17:46   ` Nate Lawson
2004-01-23 15:58   ` Pavel Machek
2004-01-24 17:09     ` Tim Stadelmann [this message]
     [not found]       ` <001c01c3e29c$e1f03fe0$03f101a3-JAjqph6Yjy8XSZKaUYBEcQ@public.gmane.org>
2004-01-24 17:35         ` Pavel Machek

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='001c01c3e29c$e1f03fe0$03f101a3@physics.ox.ac.uk' \
    --to=t.stadelmann1-jajqph6yjy8xszkauybecq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=pavel-+ZI9xUNit7I@public.gmane.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