public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
To: art stallone <art_stallone-QOiod4cnrWAN+BqQ9rBEUg@public.gmane.org>
Cc: ACPI List <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: PCI IRQ routing table
Date: Thu, 31 Mar 2005 11:08:56 -0700	[thread overview]
Message-ID: <1112292536.22598.10.camel@eeyore> (raw)
In-Reply-To: <20050331095849.25312.qmail-dvNlIvcwX/N1RbMNNJCVHYkgB36zAFJh@public.gmane.org>

On Thu, 2005-03-31 at 09:58 +0000, art stallone wrote:
> Do ACPI caches PCI IRQ routing table (PIR).
> Is there any ioctl so user space can get that table?

I don't know much about the PIR.  ACPI uses a PCI Routing
Table (_PRT).  ACPI supplies a _PRT for every PCI root bridge.
The ACPI PCI root bridge driver (drivers/acpi/pci_root.c)
parses the _PRT when it claims a new bridge (see the
acpi_pci_root_add() -> acpi_pci_irq_add_prt() path).

There is no convenient user-space mechanism to get the
_PRT.  The _PRT is stored in the DSDT, which you *can*
get, via /proc/acpi/dsdt.  But then you have to disassemble
the DSDT and parse the _PRT yourself.  I.e., you would do
something like "cp /proc/acpi/dsdt dsdt; iasl -d dsdt;
cat dsdt.dsl".

You can get iasl here:
    http://www.intel.com/technology/IAPC/acpi/downloads.htm



-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30

      parent reply	other threads:[~2005-03-31 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31  9:58 PCI IRQ routing table art stallone
     [not found] ` <20050331095849.25312.qmail-dvNlIvcwX/N1RbMNNJCVHYkgB36zAFJh@public.gmane.org>
2005-03-31 18:08   ` Bjorn Helgaas [this message]

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=1112292536.22598.10.camel@eeyore \
    --to=bjorn.helgaas-vxdhtt5mjny@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=art_stallone-QOiod4cnrWAN+BqQ9rBEUg@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