From: Adrian Cox <adrian@humboldt.co.uk>
To: root@chaos.analogic.com
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Greg Hosler <hosler@lugs.org.sg>,
linux-kernel@vger.kernel.org
Subject: Re: AC'97 (VT82C686A) & IRQ reassignment (I/O APIC)
Date: Mon, 30 Apr 2001 19:19:26 +0100 [thread overview]
Message-ID: <3AEDACAE.5090105@humboldt.co.uk> (raw)
In-Reply-To: <Pine.LNX.3.95.1010430131456.14407A-100000@chaos.analogic.com>
Richard B. Johnson wrote:
> Woof... More GAWDAUFULL junk. You mean that if I write 0xff to the R/W
> interrupt line register and read it back, it's only 0x0f?
Yes, and that disables generation of audio interrupts.
> This didn't
> save any money. There are only 4 interrupt 'pins', i.e., interrupt lines
> that go to the PCI bus (A thru D). What these lines connect to for
> actual IRQs is known only to the motherboard manufacturer hence the
> BIOS has to check the pin value and write the appropriate IRQ value
> into the interrupt line register. This register is used only as a
> scratch-pad so that a driver "knows" what IRQ goes to the board. The
> board, itself, never accesses this register. The board only gets one
> interrupt connected (A thru D), and to the board, all interrupts are
> the same.
I'm currently writing the BIOS for a PowerPC embedded system using the
686B southbridge. On the 686 the 8259 interrupt controller and the
audio system are inside the same physical device. The value you write to
offset 0x3c actually makes the internal connection between the audio
interrupt and the PIC. There is a trick to route that interrupt to an
external APIC involving config register 0x58 in function 0, but I've not
used it.
Most southbridge functions work this way. The USB on the 686B is like
this, and the the IDE controller always generates the legacy IRQ 14/15.
- Adrian Cox
prev parent reply other threads:[~2001-04-30 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 15:38 AC'97 (VT82C686A) & IRQ reassignment (I/O APIC) Greg Hosler
2001-04-30 15:41 ` Richard B. Johnson
2001-04-30 16:38 ` Jeff Garzik
2001-04-30 17:32 ` Richard B. Johnson
2001-04-30 18:19 ` Adrian Cox [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=3AEDACAE.5090105@humboldt.co.uk \
--to=adrian@humboldt.co.uk \
--cc=hosler@lugs.org.sg \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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