Hi.

On Friday 29 June 2007 00:25:32 Pavel Machek wrote:
quoted text
> Hi!
>=20
> > Hi all
> >=20
> > Here's what I have after today's work.
> >=20
> > I haven't yet been able to test on x86, but can confirm that it works o=
kay=20
on x86_64. I'm currently working towards testing it on my old Omnibook. My =
P4=20
desktop won't resume from suspend to ram at all, and hasn't produced any=20
beeps.
quoted text
> >=20
> > I needed to move the BEEP invocation to after the data segment is=20
reloaded, so that the test could access the variable. That was pretty trick=
y=20
to find - no oops or anything bad prior, it just didn't beep when expected.
quoted text
> >=20
> > A couple of notes:
> >=20
> > - I'd like to put the BEEP macro somewhere that can be shared by x86 32=
=20
and 64. If that's a good idea, any suggestions on where? Nothing occurs to =
me=20
straight off.
quoted text
> > - I've just switched from Evo to Kmail. Please let me know if there's a=
ny=20
mangling of the patch.
quoted text
> >=20
> > Regards,
> >=20
> > Nigel
> >=20
> >  arch/i386/kernel/acpi/wakeup.S   |   29 ++++++++++++++++++++++++++++-
> >  arch/x86_64/kernel/acpi/wakeup.S |   25 +++++++++++++++++++++++++
> >  include/linux/acpi.h             |    1 +
> >  kernel/power/main.c              |   23 +++++++++++++++++++++++
> >  4 files changed, 77 insertions(+), 1 deletion(-)
> > diff -ruNp 970-str-beep.patch-old/arch/i386/kernel/acpi/wakeup.S=20
970-str-beep.patch-new/arch/i386/kernel/acpi/wakeup.S
quoted text
> > --- 970-str-beep.patch-old/arch/i386/kernel/acpi/wakeup.S	2007-06-19=20
12:15:25.000000000 +1000
quoted text
> > +++ 970-str-beep.patch-new/arch/i386/kernel/acpi/wakeup.S	2007-06-19=20
21:14:49.000000000 +1000
quoted text
> > @@ -11,7 +11,22 @@
> >  #
> >  # If physical address of wakeup_code is 0x12345, BIOS should call us w=
ith
quoted text
> >  # cs =3D 0x1234, eip =3D 0x05
> > -#=20
> > +#
> > +
> > +#define BEEP \
> > +	inb	, %al; 	\
> > +	outb	%al, __PLACEHOLDER__8_x80; 	\
> > +	movb	, %al; 	\
> > +	outb	%al, ; 	\
> > +	outb	%al, __PLACEHOLDER__8_x80; 	\
> > +	movb	$-74, %al; 	\
> > +	outb	%al, ; 	\
> > +	outb	%al, __PLACEHOLDER__8_x80; 	\
> > +	movb	$-119, %al; 	\
> > +	outb	%al, ; 	\
> > +	outb	%al, __PLACEHOLDER__8_x80; 	\
> > +	movb	, %al; 	\
> > +	outb	%al, ;
> > =20
> >  ALIGN
> >  	.align	4096
> > @@ -31,6 +46,11 @@ wakeup_code:
> >  	movw	%cs, %ax
> >  	movw	%ax, %ds					# Make ds:0 point to wakeup_start
> >  	movw	%ax, %ss
> > +
> > +	testl   , beep_flags - wakeup_code
> > +	jz      1f
> > +	BEEP
> > +1:
>=20
> Can we rename/reuse existing flag variable?

Sorry, but I can't resist the opportunity to say "Send a patch!" :)

Seriously, though, I'd prefer not to. If we rename that acpi video flags=20
variable (I assume this is what you're thinking of), we only create cause f=
or=20
confusion. A variable should for debugging or for controlling quirks, not f=
or=20
both at the same time.

Regards,

Nigel
=2D-=20
Nigel, Michelle and Alisdair Cunningham
5 Mitchell Street
Cobden 3266
Victoria, Australia