LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Lee Revell" <rlrevell@joe-job.com>
To: "Jan Marek" <linux@hazard.jcu.cz>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Is it possible to change IRQ for certain device?
Date: Sun, 13 Jan 2008 22:57:13 -0500 [thread overview]
Message-ID: <75b66ecd0801131957s1e70bda9x342f16a7d16a2789@mail.gmail.com> (raw)
In-Reply-To: <20080111165711.GA21173@hazard.jcu.cz>
On Jan 11, 2008 11:57 AM, Jan Marek <linux@hazard.jcu.cz> wrote:
> I suppose, that VGA card does not need unique IRQ, but programmers,
> which wrote driver, want it. I can imagine, that VGA card have many
> interrupts, especially in the OpenGL games, but I cannot assign unique
> IRQ for VGA card at all :-(
>
> But thank you for advice: I will try to send e-mail to Gigabyte and ask
> they, if it possible to do change in the BIOS.
>
> BTW: it is interesting: I had a Biostar TA690G motherboard and it behave
> similar as Gigabyte: I cannnot assign unique IRQ to the external
> graphics card... Chipsets of this motherboards are the same...
>
> I've tried to solve this problem by bought of new motherboard: Gigabyte
> MA790FX-DS5. I will see, if this board will behave as previous board...
Why is a shared IRQ a problem for you? IRQ handlers are supposed to
be fast enough that disabling an IRQ line for the duration of the
handler execution should not be a problem even if the IRQ is shared.
VGA interrupts in particular should only fire once per frame and only
need to flip some bits to wake up any processes waiting on vsync.
If you have issues with a shared VGA interrupt then the bug is that
some IRQ handler runs for too long and should be deferring work to a
bottom half.
Lee
next prev parent reply other threads:[~2008-01-14 3:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 11:05 Is it possible to change IRQ for certain device? Jan Marek
2008-01-10 11:23 ` Andi Kleen
2008-01-10 14:01 ` linux-os (Dick Johnson)
2008-01-10 23:43 ` Len Brown
2008-01-11 16:57 ` Jan Marek
2008-01-14 3:57 ` Lee Revell [this message]
2008-01-14 5:30 ` Bryan Donlan
2008-01-14 6:04 ` Lee Revell
2008-01-15 21:33 ` Folkert van Heusden
[not found] <fa.LwvfKOhzep/AjTQmtXaIiXMm6zI@ifi.uio.no>
2008-01-11 5:18 ` Robert Hancock
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=75b66ecd0801131957s1e70bda9x342f16a7d16a2789@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=linux@hazard.jcu.cz \
/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).