From: Kendrick Hamilton <hamilton@sedsystems.ca>
To: Linux Kernel Mailing list <linux-kernel@vger.kernel.org>
Subject: Getting APIC interrupts
Date: Tue, 27 May 2003 09:04:46 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.44.0305270857580.14661-100000@sw-55.sedsystems.ca> (raw)
Hi,
please CC hamilton@sedsystems.ca with responses/dicsussion
regarding this posting.
We developped a modulator card and device driver for linux. The
card is a PCI card. When installed in an IBM E-server, dual processor xeon
computer, the linux kernel does not receive any interupts. If I cat
/proc/interrupts, the card is assigned interrupt 10 on the XT-PIC. The
only other device assigned to the XT-PIC is cascade. When we check the
card's intterupt line with an oscilloscope, we see that an interrupt is
being generated.
A temporary work around is to use the noapic flag with the kernel.
I am wondering if there is a special call when requesting the interrupt
that I can use to get the interrupt to go through the APIC so I don't need
the noapic flag?
--
Kendrick Hamilton E.I.T.
SED Systems, a division of Calian Ltd.
18 Innovation Blvd.
PO Box 1464
Saskatoon, Saskatchewan
Canada
S7N 3R1
Hamilton@sedsystems.ca
Tel: (306) 933-1453
Fax: (306) 933-1486
reply other threads:[~2003-05-27 14:51 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=Pine.LNX.4.44.0305270857580.14661-100000@sw-55.sedsystems.ca \
--to=hamilton@sedsystems.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).