public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Emilio Mejia Fernandez de Velasco <emejia-EkmVulN54Sk@public.gmane.org>
To: sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org
Cc: acpi-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: RV: differences between acpidump and disassembling
Date: Wed, 21 Apr 2004 01:18:16 +0200	[thread overview]
Message-ID: <200404210118.17337.emejia@ieee.org> (raw)
In-Reply-To: <1082487806.28680.8.camel-4/PLUo9XfK8@public.gmane.org>

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

El Martes, 20 de Abril de 2004 21:03, Sérgio Monteiro Basto escribió:
> Hello You have very similar to mine :)
>
> when you compile the kernel you must disable SMP, IO-APIC and LOCAL
> APIC, in menu  "Processor type and features" to work with ACPI.
> (use make xconfig)
>
> Please send me the output /sbin/lspci and /sbin/lspci -n
>
> You must disable Advance Program Interrupt Control.
>
Now I don't know what else I can do. Here I send you the results of lspci and 
lspci -n, and also the configuration file to compile the kernel 2.6.4, which 
is very similar to the one that I used for 2.6.5. I think I had already taken 
in account to disable SMP and APIC.
Tomorrow I will try again to compile the kernel 2.6.5. By the way, in this 
last kernel, when I try to apply last acpi patch -from march 26th I think-, I 
get some hunks failed.
What should I answer when it asks me the following questions:
Reversed (or previously applied) patch detected! Assume -R? [n]
and, I usually answer n, so it asks me:
Apply anyway? [n]
and then I answer y
This is what happens when using a clean or vanilla kernel directly downloaded 
from kernel.org, and the acpi patch from acpi.sf.net
Anyway, I have already tried 2.6.5 with and without the acpi patch, and the 
only way to get it working is without acpi options
I will send you the .config file when I compile it, so you can check out if 
I'm using the right options ¿ok?

Best regards,

Emilio

[-- Attachment #2: lspci.bz2 --]
[-- Type: application/x-bzip2, Size: 534 bytes --]

[-- Attachment #3: lspci-n.bz2 --]
[-- Type: application/x-bzip2, Size: 222 bytes --]

[-- Attachment #4: .config.bz2 --]
[-- Type: application/x-bzip2, Size: 4322 bytes --]

  parent reply	other threads:[~2004-04-20 23:18 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
     [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 [this message]
     [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=200404210118.17337.emejia@ieee.org \
    --to=emejia-ekmvuln54sk@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=sergiomb-hHo3WeeoaswVhHzd4jOs4w@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