mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: torvalds@transmeta.com, kernel list <linux-kernel@vger.kernel.org>
Subject: suspend-to-disk documentation updates
Date: Sat, 29 Jun 2002 16:05:29 +0200	[thread overview]
Message-ID: <20020629140529.GA576@elf.ucw.cz> (raw)

Hi!

Please apply,
									Pavel

--- linux-swsusp.test/Documentation/swsusp.txt	Sun May 26 19:31:41 2002
+++ linux-swsusp/Documentation/swsusp.txt	Sat Jun 29 15:56:37 2002
@@ -122,11 +122,9 @@
   interrupts AFAIK..
 - We should only make a copy of data related to kernel segment, since any
   process data won't be changed.
-- By copying pages back to their original position, copy_page caused General
-  Protection Fault. Why?
 - Hardware state restoring.  Now there's support for notifying via the notify
   chain, event handlers are welcome. Some devices may have microcodes loaded
-  into them. We should have event handlers for them aswell.
+  into them. We should have event handlers for them as well.
 - We should support other architectures (There are really only some arch
   related functions..)
 - We should also restore original state of swaps if the ``noresume'' kernel
@@ -148,6 +146,15 @@
   go there anyway..
 - If X is active while suspending then by resuming calling svgatextmode
   corrupts the virtual console of X.. (Maybe this has been fixed AFAIK).
+
+Drivers we support
+- IDE disks are okay
+- vesafb
+
+Drivers that need support
+- pc_keyb -- perhaps we can wait for vojtech's input patches
+- do IDE cdroms need some kind of support?
+- IDE CD-RW -- how to deal with that?
 
 Any other idea you might have tell me!
 

-- 
(about SSSCA) "I don't say this lightly.  However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa

                 reply	other threads:[~2002-06-30 14:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020629140529.GA576@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®