From: "Emilio Mejía Fernández de Velasco" <emejia-EkmVulN54Sk@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Acpi-devel digest, Vol 1 #1755 - 3 msgs
Date: Wed, 21 Apr 2004 02:14:21 +0200 [thread overview]
Message-ID: <200404210214.22007.emejia@ieee.org> (raw)
In-Reply-To: <20040420235602.2A6361D1CEC-OzNnu8isf6tmn0lPF+B0o2Y9YhHS9GKTCHO06yS12DY@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2037 bytes --]
>
> From: Luca Capello <luca-wlebWZzHoyE@public.gmane.org>
> To: 'acpi-devel' <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
> Subject: Re: RV: [ACPI] differences between acpidump and disassembling
> 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.
yes, sure, but I was explaining why I was using 2.6.4 instead of 2.6.5. This
was before Sergio's advice.
Right now I'm compiling again 2.6.5 even though I'm pretty sure that I'll have
the same blockings.
I have tried to apply last acpi patch, but I get this kind of messages:
Hunk #1 FAILED at 2440.
1 out of 1 hunk FAILED -- saving rejects to file
arch/i386/kernel/io_apic.c.rej
patching file arch/x86_64/kernel/io_apic.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n] y
Hunk #1 FAILED at 1891.
1 out of 1 hunk FAILED -- saving rejects to file
arch/x86_64/kernel/io_apic.c.rej
Hunk #1 FAILED at 2440.
1 out of 1 hunk FAILED -- saving rejects to file
arch/i386/kernel/io_apic.c.rej
patching file arch/x86_64/kernel/io_apic.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n] y
Hunk #1 FAILED at 1891.
1 out of 1 hunk FAILED -- saving rejects to file
arch/x86_64/kernel/io_apic.c.rej
...
So I'll just use the raw version as downloaded from kernel.org, unless you
give me any hint about these.
I also send you the .config file, so if you find something that I shouldn't
include, please let me know
Thank you so much
Emilio
[-- Attachment #2: .config.bz2 --]
[-- Type: application/x-bzip2, Size: 4348 bytes --]
next parent reply other threads:[~2004-04-21 0:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040420235602.2A6361D1CEC@sc8-sf-uberspam1.sourceforge.net>
[not found] ` <20040420235602.2A6361D1CEC-OzNnu8isf6tmn0lPF+B0o2Y9YhHS9GKTCHO06yS12DY@public.gmane.org>
2004-04-21 0:14 ` Emilio Mejía Fernández de Velasco [this message]
2004-04-21 0:45 ` RV: differences between acpidump and disassembling 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=200404210214.22007.emejia@ieee.org \
--to=emejia-ekmvuln54sk@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