public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew de Quincey <adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
To: Claas Langbehn <claas-YJlxJerscEeELgA04lAiVw@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 2.6.0-test4 acpi problems
Date: Sun, 31 Aug 2003 02:19:41 +0100	[thread overview]
Message-ID: <200308310219.41304.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <20030830215116.GA1444-YJlxJerscEeELgA04lAiVw@public.gmane.org>

On Saturday 30 Aug 2003 10:51 pm, Claas Langbehn wrote:
> To: kernel list <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
>
> Hello!
>
>
> I have got an Epox 8K9A9i mainboard with an Athlon XP 1800+ CPU. The
> chipset is an VIA KT400A. The bios is dated 12.05.2003.
> When booting with ACPI enabled, the interrupts dont get enumerated
> properly. with acpi=ht it works, but i dont have enough features.
> Below you see my bootlog with acpi and further down the bootlog with
> acpi=off. Is there a way to use full acpi support and "normal"
> interrupts? pci=noacpi was not really successful.
>
> How can I help acip development and do more debugging?

Aha, this is a known problem with the KT400 chipset. All BIOSes I've 
encountered for the KT400 have a nasty bug in the AML code which breaks ACPI 
IRQ routing.

The only way to make it work is to directly program the hardware itself. Via 
are sending me docs on the KT400, so I will add appropriate code to 
arch/i386/pci/irq.c for this board. As far as I can make out this is how 
Windows makes ACPI work on this board... it has specific hardware support for 
certain chipsets.

Hopefully I'll have something sometime next week.....



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

       reply	other threads:[~2003-08-31  1:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030830215116.GA1444@rootdir.de>
     [not found] ` <20030830215116.GA1444-YJlxJerscEeELgA04lAiVw@public.gmane.org>
2003-08-31  1:19   ` Andrew de Quincey [this message]
     [not found]     ` <200308310219.41304.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-08-31  0:35       ` 2.6.0-test4 acpi problems Carlos Morgado
     [not found]         ` <20030831003536.GG14307-hpVnRXGo/2ksCylrc8G9yg@public.gmane.org>
2003-08-31 10:38           ` Andrew de Quincey
2003-08-31 13:17           ` Alan Cox
     [not found]             ` <1062335841.31332.46.camel-Z+iYsftfazAXoXS6vNje7nviChZXdy279dF7HbQ/qKg@public.gmane.org>
2003-08-31 17:28               ` Andrew de Quincey
     [not found]                 ` <200308311828.19231.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-08-31 18:06                   ` Alan Cox
2003-08-31 13:23       ` Holger W.
     [not found]         ` <000f01c36fc3$1a099f90$0200a8c0-IGm5bqYn3xw@public.gmane.org>
2003-08-31 17:22           ` Andrew de Quincey

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=200308310219.41304.adq_dvb@lidskialf.net \
    --to=adq_dvb-fmpxvn3awwjajazl26g0sa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=claas-YJlxJerscEeELgA04lAiVw@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