public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Hentges <mailinglisten-H4PcyxPeSRnR7s880joybQ@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: S3 broken on a Samsung P30
Date: Fri, 12 Nov 2004 13:51:59 +0100	[thread overview]
Message-ID: <1100263919.3523.3.camel@mhcln03> (raw)
In-Reply-To: <20041110231802.GA1099-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 461 bytes --]

Am Donnerstag, den 11.11.2004, 00:18 +0100 schrieb Pavel Machek:

> See recent threads of adding beeping to begining of wakeup.S. Does it
> beep for you?

No it doesn't.
I've googled for the beep patch. The one I found is attached as I'm not
sure if it is the right one.

Thanks
-- 
Matthias Hentges 
Cologne / Germany

[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4   -> No files, no URL's

My OS: Debian SID. Geek by Nature, Linux by Choice

[-- Attachment #2: Type: text/x-patch, Size: 751 bytes --]

--- clean-mm/arch/i386/kernel/acpi/wakeup.S	2004-08-24 09:02:23.000000000 +0200
+++ linux-mm/arch/i386/kernel/acpi/wakeup.S	2004-09-07 21:15:17.000000000 +0200
@@ -11,8 +11,23 @@
 #
 # If physical address of wakeup_code is 0x12345, BIOS should call us with
 # cs = 0x1234, eip = 0x05
-# 
+#
 
+#define BEEP \
+	inb	$97, %al; 	\
+	outb	%al, $0x80; 	\
+	movb	$3, %al; 	\
+	outb	%al, $97; 	\
+	outb	%al, $0x80; 	\
+	movb	$-74, %al; 	\
+	outb	%al, $67; 	\
+	outb	%al, $0x80; 	\
+	movb	$-119, %al; 	\
+	outb	%al, $66; 	\
+	outb	%al, $0x80; 	\
+	movb	$15, %al; 	\
+	outb	%al, $66; 
+	
 ALIGN
 	.align	4096
 ENTRY(wakeup_start)
@@ -20,6 +35,7 @@
 	wakeup_code_start = .
 	.code16
 
+	BEEP
  	movw	$0xb800, %ax
 	movw	%ax,%fs
 	movw	$0x0e00 + 'L', %fs:(0x10)

  parent reply	other threads:[~2004-11-12 12:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-04 21:50 S3 broken on a Samsung P30 Matthias Hentges
2004-11-10 23:18 ` Pavel Machek
     [not found]   ` <20041110231802.GA1099-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-11-12 12:51     ` Matthias Hentges [this message]
2004-11-12 16:04       ` Pavel Machek
     [not found]         ` <20041112160435.GC1858-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-11-12 18:10           ` Matthias Hentges
2004-11-12 19:55             ` Pavel Machek
     [not found]               ` <20041112195530.GA1123-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-11-12 20:55                 ` Matthias Hentges
2004-11-12 21:16                   ` Pavel Machek
     [not found]                     ` <20041112211659.GD1252-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-11-17 23:54                       ` 2.6.7-rc2 breaks resume (was Re: S3 broken on a Samsung P30) Matthias Hentges
  -- strict thread matches above, loose matches on Subject: below --
2004-11-12 22:11 S3 broken on a Samsung P30 Pallipadi, Venkatesh
     [not found] ` <88056F38E9E48644A0F562A38C64FB6003569022-exJ48ZlmiLpQxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-11-12 22:32   ` Pavel Machek
     [not found]     ` <20041112223209.GI1252-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-11-13 10:53       ` Matthias Hentges

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=1100263919.3523.3.camel@mhcln03 \
    --to=mailinglisten-h4pcyxpesrnr7s880joybq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=pavel-+ZI9xUNit7I@public.gmane.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