public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Manfred Spraul" <manfred@colorfullife.com>
To: <root@chaos.analogic.com>
Cc: <hosler@lugs.org.sg>, <linux-kernel@vger.kernel.org>
Subject: Re: AC'97 (VT82C686A)
Date: Mon, 30 Apr 2001 18:56:37 +0200	[thread overview]
Message-ID: <003901c0d196$89d8f2d0$5517fea9@local> (raw)

> Observe that the PCI DWORD (long) register at DWORD offset 15 consists
> of 4 byte-wide registers (from the PCI specification), Max_lat,
> Min_Gnt, Interrupt pin, and interrupt line. Nothing has to fit into
> 4 bits, you have 8 bits. I haven't looked at the Linux code, but if
> it provides only 4 bits for the IRQ, it's broken.

I don't have the PCI specification, but at least some network cards
ignore all writes to that register. It's only an interface between the
bios and os. (pnic-82c168: "Interrupt Line. This 8-bit register will be
written by the POST software. The value of this register indicates which
input of the system interrupt controller PNIC's interrupt pin is
connected to."). The AC97 documentation says that only the low 4 bits
are writable. Perhaps it reconfigures itself if
someone writes to that register? Linux never writes to the low byte of
DWORD offset 15.

Greg, what's the value of 'dev->irq'? Usually drivers should never read
offset 3C, instead they should use 'dev->irq'.

arch/i386/kernel/mpparse should figure out where the interrupts arrive.
If that doesn't work: the MP table is documented at
http://developer.intel.com/design/pentium/datashts/24201606.pdf
and one of the debugging options in arch/i386/kernel/mpparse.c will
print all interrupt routing entries during boot up.

The routing entries are (bus, function and pin) -> io apic pin, and the
values for bus, function and pin are known.

--
    Manfred







                 reply	other threads:[~2001-04-30 16:57 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='003901c0d196$89d8f2d0$5517fea9@local' \
    --to=manfred@colorfullife.com \
    --cc=hosler@lugs.org.sg \
    --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