From: Russell King <rmk@arm.linux.org.uk>
To: John Clemens <john@deater.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pci_write_config_byte question..
Date: Mon, 19 Nov 2001 17:23:00 +0000 [thread overview]
Message-ID: <20011119172300.B16263@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0111191243570.237-100000@pianoman.cluster.toy>
In-Reply-To: <Pine.LNX.4.33.0111191243570.237-100000@pianoman.cluster.toy>; from john@deater.net on Mon, Nov 19, 2001 at 12:48:24PM -0500
On Mon, Nov 19, 2001 at 12:48:24PM -0500, John Clemens wrote:
> I've been hacking some PCI code to get USB working on my laptop. I need
> to change PCI config space to use IRQ 11 for the device instead of IRQ 9.
Changing interrupts is non-trivial, especially on x86.
> So i call pci_write_config_byte(...), but that only appears to change the
> "system" view of PCI space.. if you boot the kernel and do an lspci, it
> shows up as IRQ11, but if you do a lspci -b (for "Bus" view), it still
> shows up as IRQ 9.
The kernel caches a copy of the IRQ number register. The IRQ number
register (PCI_INTERRUPT_LINE) is just like RAM - you can read it, you
can write it. However, it has no hardware side effects however. It's
sole purpose in life is to communicate the IRQ number from the POST
(which knows how the interrupts are arranged) to the driver.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-11-19 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 17:48 pci_write_config_byte question John Clemens
2001-11-19 17:23 ` Russell King [this message]
2001-11-19 18:39 ` John Clemens
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=20011119172300.B16263@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=john@deater.net \
--cc=linux-kernel@vger.kernel.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.