All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <syrjala-ORSVBvAovxo@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Abit KT7 IRQ routing
Date: Mon, 7 Oct 2002 01:48:59 +0300	[thread overview]
Message-ID: <20021007014859.A24132@sci.fi> (raw)

As I reported earlier my AGP card seems to get the wrong IRQ. It works but
one IRQ remains completely unused. I just turned on debugging in the PCI
code...

The AGP slot 01:00.0 doesn't have an entry in the PRT so the code will try
to derive it from the AGP bridge 00:01.0

I'm not sure this is relevant but I included it here anyway:
pci_irq-0318 [0001] [02] acpi_pci_irq_enable : No interrupt pin configured
for device 00:01.0

Here's the interesting output:
pci_irq-0242 [0001] [03] acpi_pci_irq_lookup   : Searching for PRT entry
for 00:01:00[A]
<snip>
pci_irq-0248 [0001] [03] acpi_pci_irq_lookup   : PRT entry not found
<snip>
pci_irq-0242 [0001] [04] acpi_pci_irq_lookup   : Searching for PRT entry
for 00:00:01[B]
            ^^^
Why does it think 01:00.0[A] == 00:01.0[B]? This is what causes it to get
the IRQ from LNKB instead of LNKA.

Looking at the code in pci_irq.c:

while (!irq && (bridge = bridge->bus->self)) {
  pin = (pin + PCI_SLOT(bridge->devfn)) % 4;
  irq = acpi_pci_irq_lookup(0, bridge->bus->number, PCI_SLOT(bridge->devfn), pin);
}

So it seems that PCI_SLOT(brigde->devfn) is doing something wrong.

Any ideas?


PS.
I "fixed" the ISA sound card + SCSI CDROM problem by using a PCI sound
card. Something ISA related gets configured in a funny manner with ACPI.

-- 
Ville Syrjälä
syrjala-ORSVBvAovxo@public.gmane.org
http://www.sci.fi/~syrjala/


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

                 reply	other threads:[~2002-10-06 22:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021007014859.A24132@sci.fi \
    --to=syrjala-orsvbvaovxo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.