All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Haninger <ahaning@gmail.com>
Cc: lokum spand <lokumsspand@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: A possible idea for Linux: Save running programs to disk
Date: Mon, 3 Oct 2005 20:59:23 +0200	[thread overview]
Message-ID: <20051003185923.GG3652@stusta.de> (raw)
In-Reply-To: <105c793f0510031152v76225bc7r83e5e2170f3434d5@mail.gmail.com>

On Mon, Oct 03, 2005 at 02:52:52PM -0400, Andrew Haninger wrote:
> On 10/3/05, Adrian Bunk <bunk@stusta.de> wrote:
> > Where are hardware issues with suspend to disk?
> >
> Actually, very few currently [AFAIK, on my hardware]. However, at
> least in the past, my r200 card wasn't useable after resume from
> suspend without patches to XFree86. I know people had trouble with the
> fglrx drivers not supporting suspend-to-disk. [I believe current r300
> drivers work fine, but I do not have personal confirmation.] I have a
> machine that used to have issues because I was using a keyboard and no
> mouse. When I resumed, the keyboard didn't work. If I had a mouse
> plugged in, suspend/resume worked fine. Here's a link to my mail to
> LKML about this issue:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=112139506118959&w=2
> 
> As new hardware is introduced and drivers have to be written or
> reverse-engineered and kinks worked out, bugs like these will crop up
> again and again. [That is, unless manufacturers become more open about
> their hardware. From my perspective, they are becoming more closed.
> ATI, for example.]
>...

These are all software problems, not hardware problems.
 
> Neat.
> 
> -Andy

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-10-03 18:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-01 21:30 A possible idea for Linux: Save running programs to disk lokum spand
2005-10-01 21:39 ` Arjan van de Ven
2005-10-01 22:21   ` Michael Concannon
2005-10-01 22:51     ` lokum spand
2005-10-01 23:09       ` Michael Concannon
2005-10-02  8:30       ` Tomasz Torcz
2005-10-02 13:31       ` Benoit Boissinot
2005-10-02 18:49       ` Jon Masters
2005-10-02 19:21       ` Lexington Luthor
2005-10-02  0:34   ` grundig
2005-10-02  4:53 ` Bernard Blackham
2005-10-02 12:57   ` Ed Tomlinson
2005-10-02 14:16     ` Bernard Blackham
2005-10-10  1:13       ` serue
2005-11-06 15:42         ` Bernard Blackham
2005-11-09  2:15           ` Peter Chubb
2005-10-02  5:36 ` Andrew Haninger
2005-10-03 17:41   ` Adrian Bunk
2005-10-03 18:52     ` Andrew Haninger
2005-10-03 18:59       ` Adrian Bunk [this message]
2005-10-03 19:48         ` Andrew Haninger
2005-10-02 18:46 ` Jon Masters
     [not found] <4SXfo-7hM-9@gated-at.bofh.it>
2005-10-02  3:19 ` Bodo Eggert
     [not found] ` <4T47e-5E-1@gated-at.bofh.it>
     [not found]   ` <4TbLq-2VG-5@gated-at.bofh.it>
     [not found]     ` <4TcR9-4sS-9@gated-at.bofh.it>
2005-10-02 17:08       ` Bodo Eggert
2005-10-02 17:51         ` Bernard Blackham
2005-10-02 19:13           ` Jeff Dike
2005-10-03 20:02           ` 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=20051003185923.GG3652@stusta.de \
    --to=bunk@stusta.de \
    --cc=ahaning@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lokumsspand@hotmail.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 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.