From: Rob North <tzwvgwv2001-O/bDAPVd7B0N+BqQ9rBEUg@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI ignoring IRQ flags in PRT
Date: Sun, 13 Jul 2003 19:08:02 +0100 [thread overview]
Message-ID: <bes74d$ucr$1@main.gmane.org> (raw)
In-Reply-To: <200307131745.42153.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
Andrew de Quincey wrote:
> On Sunday 13 July 2003 15:23, Matthew Wilcox wrote:
>
>
> So, the code in io_apic.c is assuming that all IRQs > 15 are PCI-compatable.
> For me, at least, they are not, *EVEN THOUGH they're in the _PRT*. The ACPI
> tables are describing them as I have experimentally found them to be.
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
> www.parasoft.com/bulletproofapps1
Andrew, I think you're on to something big here.
I've been having similiar problems with my A7N8x Deluxe motherboard, and
I've been looking into the kernel code in the 2.4.X series of kernels,
and you've definately found something that look amiss.
I think what was throwing Matthew is that the interupt trigger types are
specified in _PRS objects
The _PRT object is a mapping from PCI device to a particular "PCI
Interrupt Link device" and in the defintion of the link device, the IRQs
are defined in _PRS objects.
I'm about to re-compile a 2.4.22-pre3-ac1 kernel with your suggested
quick fix.
Will report back.
Keep up the good work
-Rob.
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
next prev parent reply other threads:[~2003-07-13 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 13:52 ACPI ignoring IRQ flags in PRT Andrew de Quincey
[not found] ` <200307131452.39000.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-13 14:23 ` Matthew Wilcox
[not found] ` <20030713142321.GC20424-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2003-07-13 16:45 ` Andrew de Quincey
[not found] ` <200307131745.42153.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-13 18:08 ` Rob North [this message]
2003-07-13 19:36 ` Andrew de Quincey
2003-07-13 19:49 ` Andrew de Quincey
-- strict thread matches above, loose matches on Subject: below --
2003-07-14 0:56 Grover, Andrew
2003-07-14 8:51 ` Andrew de Quincey
[not found] ` <200307140951.18569.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-14 11:07 ` Rob North
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='bes74d$ucr$1@main.gmane.org' \
--to=tzwvgwv2001-o/bdapvd7b0n+bqq9rbeug@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