mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Grover, Andrew" <andrew.grover@intel.com>
To: "'Kai Germaschewski'" <kai@tp1.ruhr-uni-bochum.de>
Cc: "'Ducrot Bruno'" <poup@poupinou.org>,
	linux-kernel@vger.kernel.org, Pavel Machek <pavel@suse.cz>,
	acpi-devel@lists.sourceforge.net
Subject: RE: [PATCH] S4bios for 2.5.52.
Date: Tue, 17 Dec 2002 14:24:23 -0800	[thread overview]
Message-ID: <EDC461A30AC4D511ADE10002A5072CAD04C7A5B6@orsmsx119.jf.intel.com> (raw)

> From: Kai Germaschewski [mailto:kai@tp1.ruhr-uni-bochum.de] 
> > I still am not clear on why we would want s4bios in 2.5.x, 
> since we have S4.
> > Like you said, S4bios is easier to implement, but since 
> Pavel has done much
> > of the heavy lifting required for S4 proper, I don't see the need.
> 
> Let me counter this, I have to admit that I didn't try the 
> patch yet, but
> my laptop does S4 BIOS, and I'd definitely prefer that to 
> swsusp, since
> it's much faster and also I somewhat have more faith into S4 BIOS than
> swsusp (as in: after resuming, it'll most likely either work 
> or crash, but
> not cause any weird kinds of corruption). Since it does not 
> need not much
> more to support it than S3, I don't see why you wouldn't want to give
> users the option?

Ok that's reasonable.

My belief is that S4bios is a stopgap measure until S4 gets better. That
said, I think you are right - it should go in for now, and then at some
point in the future someone will say, "S4bios?? who needs *that* anymore??"
and it will get pulled out. ;-)

So I'll look to merge it, unless someone upstream beats me to it.

Regards -- Andy

             reply	other threads:[~2002-12-17 22:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-17 22:24 Grover, Andrew [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-17 21:39 Grover, Andrew
2002-12-17 22:14 ` Kai Germaschewski
2002-12-18  8:59   ` Ducrot Bruno
2002-12-17 20:39 Ducrot Bruno

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=EDC461A30AC4D511ADE10002A5072CAD04C7A5B6@orsmsx119.jf.intel.com \
    --to=andrew.grover@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=poup@poupinou.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

all inboxes | Powered by JetHome®