public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	suspend-devel@lists.sourceforge.net, seife@suse.de
Subject: Re: [rft] Kill junk from s2ram resume paths
Date: Tue, 31 Jul 2007 15:49:54 +0200	[thread overview]
Message-ID: <200707311549.54863.rjw@sisk.pl> (raw)
In-Reply-To: <20070731131814.GI2087@elf.ucw.cz>

Hi,

On Tuesday, 31 July 2007 15:18, Pavel Machek wrote:
> Hi!
> 
> > > This removes some stale debugging infrastructure from s2ram
> > > paths. Also, there's no need to verify_cpu on x86-64 -- cpu can't
> > > change during s2ram, and removed #if 0-ed code. Some testing would be
> > > useful, perpahs it will even fix someone's machine :-). (VGA accesses
> > > could theoretically hurt if vga is not present / if it is in some
> > > strange state).
> > > 
> > > Signed-off-by: Pavel Machek <pavel@suse.cz>
> > > 
> > > diff --git a/arch/i386/kernel/acpi/wakeup.S b/arch/i386/kernel/acpi/wakeup.S
> > > index 1415da1..9719bd6 100644
> > > --- a/arch/i386/kernel/acpi/wakeup.S
> > > +++ b/arch/i386/kernel/acpi/wakeup.S
> > > @@ -53,9 +38,6 @@ wakeup_code:
> > >  # Uncomment this to make your computer start producing ugly noise as soon
> > >  # as BIOS returns to this real-mode entry point.
> > >  #	BEEP
> > > - 	movw	$0xb800, %ax
> > > -	movw	%ax,%fs
> > > -	movw	$0x0e00 + 'L', %fs:(0x10)
> > 
> > Hmm, was this a part of that yellow "Linux" string?
> 
> Yes. But I'm afraid that may cause problems if vga is not ready.

I agree.

> > >  # Running in *copy* of this code, somewhere in low 1MB.
> > >  
> > > -	movb	$0xa1, %al	;  outb %al, $0x80
> > 
> > Well, what was this for?
> 
> Debugging leds on port 80. I still have that card somewhere
> :-). Interesting parties can reinsert it.

Ah, I see.

Hmm, can you please write about that in the chanelog more explicitly?
Or just comment it out with a "uncomment this to get ..." text?

> > > @@ -88,8 +82,6 @@ # Running in *copy* of this code, somewh
> > >  	movw	%ax,%fs
> > >  	movw	$0x0e00 + 'L', %fs:(0x10)
> > 
> > Why aren't you removing this line?
> 
> Mistake, killed.

Greetings,
Rafael


-- 
"Premature optimization is the root of all evil." - Donald Knuth

  reply	other threads:[~2007-07-31 13:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 12:12 [rft] Kill junk from s2ram resume paths Pavel Machek
2007-07-31 13:20 ` Rafael J. Wysocki
2007-07-31 13:18   ` Pavel Machek
2007-07-31 13:49     ` Rafael J. Wysocki [this message]
2007-07-31 14:01       ` Pavel Machek
2007-07-31 14:43         ` Stefan Seyfried
2007-07-31 15:03           ` Rafael J. Wysocki
2007-07-31 14:58             ` Pavel Machek
2007-08-01 21:10           ` Stefan Seyfried

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=200707311549.54863.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=seife@suse.de \
    --cc=suspend-devel@lists.sourceforge.net \
    /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