From: Robert <robert.woerle-y2s3ugBAdl9BDgjK7y7TUQ@public.gmane.org>
To: Alberto Ornaghi <alor-n62phY/1UFc3ahhDiVHSzw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 2.4.18 + acpi20020918 + swsusp beta12
Date: Mon, 23 Sep 2002 21:46:45 +0200 [thread overview]
Message-ID: <3D8F6FA5.9090902@symplon.com> (raw)
In-Reply-To: 20020923142355.A4413@zefiro.alor.org
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
hi ..
waited for that !! ..
since i want to try the new patches but i also got very used to the
swsusp...
It compiles perfect and boots also perfect....swsusp is working fine and
still i dont get a working S3
which i never had with any patch since april this year ....
DSDT hacking :
i think there is something wrong with my DSDT:..I read many people who
changed things there and it worked....
hown can i do that ?
i attached my DSDT -- i got this file via pmtools from intel
acpidmp DSDT | acpidisasm >dsdt && tar cfz dsdt.tar.gz dsdt
Alberto Ornaghi schrieb:
>If someone is interested in...
>
>at http://alor.antifork.org/acpi/ there is a patch for SWSUSP beta12 against
>2.4.18-acpi20020918.
>
>the patch for 2.4.18-acpi20020918 is available at:
>
>http://codecs.home.sapo.pt/acpi/index.html
>
>bye
>
>
>
>
[-- Attachment #2: dsdt.tar.gz --]
[-- Type: application/x-gunzip, Size: 30892 bytes --]
next prev parent reply other threads:[~2002-09-23 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 12:23 2.4.18 + acpi20020918 + swsusp beta12 Alberto Ornaghi
[not found] ` <20020923142355.A4413-SK5ojcHaabmAsEEOBIrzxA@public.gmane.org>
2002-09-23 13:19 ` Andrew Kohlsmith
2002-09-23 19:46 ` Robert [this message]
[not found] ` <3D8F6FA5.9090902-y2s3ugBAdl9BDgjK7y7TUQ@public.gmane.org>
2002-09-23 20:18 ` Charl P. Botha
2002-09-23 23:14 ` Nigel Cunningham
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=3D8F6FA5.9090902@symplon.com \
--to=robert.woerle-y2s3ugbadl9bdgjk7y7tuq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=alor-n62phY/1UFc3ahhDiVHSzw@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