mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Michael Frank <mhf@berlios.de>
Cc: softwaresuspend-devel@lists.berlios.de,
	Patrick Mochel <mochel@digitalimplant.org>,
	Nigel Cunningham <ncunningham@linuxmail.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [SoftwareSuspend-devel] 2.6 Suspend PM issues
Date: Sun, 19 Dec 2004 18:36:13 +0100	[thread overview]
Message-ID: <20041219173613.GB1039@elf.ucw.cz> (raw)
In-Reply-To: <200412191114.25930.mhf@berlios.de>

Hi!

> > ...which will not work anyway, swsusp1 or swsusp2. Have you actually
> > tried it?
> 
> I put suspend support into 2.4 serial driver and use it. It does work.
> 
> 2.6 serial driver suspend was not working a year ago, have not tried since.
> 
> > During boot, BIOS is probably going to play with RTS anyway. So no
> > matter what you do during suspend, you are probably going to screw it
> > up anyway on the boot just before resume.
> 
> Luckily not on several of my machines and the linux 2.4 driver at least 
> does not turn the lines on until resume tells it to do so...

If 2.6 serial does not turn it on boot, there's no reason it should
turn it on during resume() [and it would be a bug].

Find out what 2.6 serial does, and fix the bug...
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

      reply	other threads:[~2004-12-19 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200412171315.50463.mhf@berlios.de>
2004-12-17  5:57 ` Nigel Cunningham
2004-12-17  9:26   ` Pavel Machek
2004-12-18  2:14     ` Michael Frank
2004-12-18  7:42       ` Pavel Machek
2004-12-18  7:50         ` Pavel Machek
2004-12-19  3:14           ` Michael Frank
2004-12-19 17:36             ` Pavel Machek [this message]

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=20041219173613.GB1039@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhf@berlios.de \
    --cc=mochel@digitalimplant.org \
    --cc=ncunningham@linuxmail.org \
    --cc=softwaresuspend-devel@lists.berlios.de \
    /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®