public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mika Penttilä" <mika.penttila@kolumbus.fi>
To: tom.l.nguyen@intel.com, len.brown@intel.com
Cc: linux-kernel@vger.kernel.org
Subject: PCI vector and ACPI
Date: Sat, 10 Jan 2004 17:12:33 +0200	[thread overview]
Message-ID: <40001661.90705@kolumbus.fi> (raw)

There seems to be some bad interaction between PCI VECTOR 
(use_pci_vector()) and ACPI PRTs. Namely, both mp_parse_prt() and 
pcibios_fixup_irqs() do the IO_APIC_VECTOR() translation on irq, the 
result being  IO_APIC_VECTOR(IO_APIC_VECTOR(irq)). I wonder if this is 
the cause of some bug reports with acpi and pci vector? Maybe 
mp_parse_prt() should not do the irq->vector translation?

--Mika



             reply	other threads:[~2004-01-10 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10 15:12 Mika Penttilä [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-15 20:48 Update MSI Patches Nguyen, Tom L
2004-01-10 15:09 ` PCI vector and ACPI Mika Penttilä

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=40001661.90705@kolumbus.fi \
    --to=mika.penttila@kolumbus.fi \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom.l.nguyen@intel.com \
    /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