From: Luca Capello <luca-wlebWZzHoyE@public.gmane.org>
To: 'acpi-devel'
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: RV: differences between acpidump and disassembling
Date: Tue, 20 Apr 2004 23:15:19 +0200 [thread overview]
Message-ID: <408592E7.7050105@pca.it> (raw)
In-Reply-To: <000201c4271b$37662da0$0301a8c0-qXvZZVhXUsA@public.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
on 04/20/04 23:05, Emilio Mejía Fernández de Velasco wrote:
> The only reason why I used 2.6.4 for acpi was that there was no patch to
> override the dsdt with initrd available for 2.6.5
if there's no patch available for the latest 2.6.5 it doesn't mean that the
patch for 2.6.4 doesn't work on 2.6.5. In fact this isn't correct: the contrary
is true, I successfully patched a vanilla 2.6.5 with the ACPI DSDT in initrd
patch for 2.6.4 (Jose Bernardo Silva one from http://gaugusch.at/kernel.shtml).
> Anyway, the only solution is to give up and wait until some kernel comes
> and works with my laptop -and acpi-.
Doesn't Sergio Monteiro Basto advise you that you don't need any custom DSDT?
You should be able to use any vanilla kernel + ACPI patches with the original DSDT.
Thx, bye,
Gismo / Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFAhZLmVAp7Xm10JmkRAn+XAKCEiTsykWedAO1MgsuEM8GZ2xb4WwCggZzD
9z4quaMBDdGLXOjSlEBFqt8=
=w237
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-04-20 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000701c425f8$6157aef0$0301a8c0@portatil>
[not found] ` <000701c425f8$6157aef0$0301a8c0-qXvZZVhXUsA@public.gmane.org>
2004-04-19 11:09 ` RV: differences between acpidump and disassembling Emilio Mejia Fernandez de Velasco
[not found] ` <200404191309.45870.emejia-EkmVulN54Sk=@public.gmane.org>
2004-04-19 21:16 ` Sérgio Monteiro Basto
[not found] ` <1082409395.11663.63.camel-4/PLUo9XfK8@public.gmane.org>
2004-04-19 22:24 ` Emilio Mejia Fernandez de Velasco
[not found] ` <200404200024.18432.emejia-EkmVulN54Sk@public.gmane.org>
2004-04-20 19:09 ` Sérgio Monteiro Basto
[not found] ` <1082488182.28680.14.camel-4/PLUo9XfK8@public.gmane.org>
2004-04-20 21:05 ` Emilio Mejía Fernández de Velasco
[not found] ` <000201c4271b$37662da0$0301a8c0-qXvZZVhXUsA@public.gmane.org>
2004-04-20 21:15 ` Luca Capello [this message]
[not found] ` <200404192343.11269.emejia@ieee.org>
[not found] ` <1082487806.28680.8.camel@darkstar>
[not found] ` <1082487806.28680.8.camel-4/PLUo9XfK8@public.gmane.org>
2004-04-20 23:18 ` Emilio Mejia Fernandez de Velasco
[not found] ` <200404210118.17337.emejia-EkmVulN54Sk@public.gmane.org>
2004-04-20 23:54 ` Sérgio Monteiro Basto
2004-04-21 0:15 ` Sérgio Monteiro Basto
[not found] <20040420235602.2A6361D1CEC@sc8-sf-uberspam1.sourceforge.net>
[not found] ` <20040420235602.2A6361D1CEC-OzNnu8isf6tmn0lPF+B0o2Y9YhHS9GKTCHO06yS12DY@public.gmane.org>
2004-04-21 0:45 ` Emilio Mejía Fernández de Velasco
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=408592E7.7050105@pca.it \
--to=luca-wlebwzzhoye@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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