public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: nigel@suspend2.net
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Optional Beeping During Resume From Suspend To Ram.
Date: Thu, 5 Jul 2007 00:48:59 +0200	[thread overview]
Message-ID: <20070704224859.GC2491@elf.ucw.cz> (raw)
In-Reply-To: <200707050834.17747.nigel@nigel.suspend2.net>

Hi!

> Documentation is also an issue. Your patch should update the kernel_parameters 
> file so users can know how to get the beeping to happen. It would be nice if 
> it mentioned the proc entry too.

Fixed the docs.

> > @@ -80,9 +82,11 @@ static int __init acpi_sleep_setup(char 
> >  
> >  __setup("acpi_sleep=", acpi_sleep_setup);
> >  
> > +/* Ouch, we want to delete this. We already have better version in 
> userspace, in 
> > +   s2ram from suspend.sf.net project */
> 
> Do we? This version has advantages in not requiring any userspace app and in 
> being able to work even if you can't yet get as far as having

Take a look at the file. It has whitelist with just one entry, too
bad.

> > @@ -124,7 +124,7 @@ real_save_cr3:	.long 0
> >  real_save_cr4:	.long 0
> >  real_magic:	.long 0
> >  video_mode:	.long 0
> > -video_flags:	.long 0
> > +realmode_flags:	.long 0
> >  beep_flags:	.long 0
> >  real_efer_save_restore:	.long 0
> >  real_save_efer_edx: 	.long 0
> 
> Beep_flags should be removed too if you're sticking with /proc.

Fixed.
										Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-07-04 22:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 11:18 [PATCH] Optional Beeping During Resume From Suspend To Ram Nigel Cunningham
2007-06-19 21:33 ` Rafael J. Wysocki
2007-06-20 22:09   ` Rafael J. Wysocki
2007-06-20 22:24     ` Nigel Cunningham
2007-06-21 21:20       ` Rafael J. Wysocki
2007-06-28 14:25 ` Pavel Machek
2007-06-28 22:27   ` Nigel Cunningham
2007-06-29 18:03     ` Stefan Seyfried
2007-06-29 22:35     ` Pavel Machek
2007-06-30 10:15       ` Rafael J. Wysocki
2007-06-30 10:11         ` Pavel Machek
2007-06-30 20:30           ` Rafael J. Wysocki
2007-07-04 21:29             ` Pavel Machek
2007-07-04 21:50               ` Rafael J. Wysocki
2007-07-04 22:46                 ` Pavel Machek
2007-07-05 19:03                   ` Rafael J. Wysocki
2007-07-05 22:32                     ` Pavel Machek
2007-07-04 22:34               ` Nigel Cunningham
2007-07-04 22:48                 ` Pavel Machek [this message]
2007-07-04 22:56                   ` Nigel Cunningham
2007-07-04 23:01                     ` Pavel Machek
2007-07-04 23:10                       ` Nigel Cunningham
2007-07-04 23:25                         ` Pavel Machek
2007-07-05 18:43                           ` Rafael J. Wysocki
2007-07-05 22:37                             ` 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=20070704224859.GC2491@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigel@suspend2.net \
    --cc=rjw@sisk.pl \
    /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