LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Lee Revell" <rlrevell@joe-job.com>
To: "Bryan Donlan" <bdonlan@gmail.com>
Cc: "Jan Marek" <linux@hazard.jcu.cz>,
"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: Mon, 14 Jan 2008 01:04:19 -0500 [thread overview]
Message-ID: <75b66ecd0801132204r5d4a5401hacc1de871342cf8c@mail.gmail.com> (raw)
In-Reply-To: <3e8340490801132130l737e166i3f957518170b98fc@mail.gmail.com>
On Jan 14, 2008 12:30 AM, Bryan Donlan <bdonlan@gmail.com> wrote:
>
> On Jan 13, 2008 10:57 PM, Lee Revell <rlrevell@joe-job.com> wrote:
> > On Jan 11, 2008 11:57 AM, Jan Marek <linux@hazard.jcu.cz> wrote:
> > 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.
>
> Jan is apparently using the nvidia binary driver, so I doubt it will
> be possible to fix the bug that prevents it from sharing IRQs.
>
Ah, of course, stupid me. Thought I was on linux-audio-user where
this is a FAQ (for completely different reasons) and not LKML.
But this is strange - I'm sure I've seen people using that driver with
a shared IRQ before.
Jan, maybe you can blacklist ohci-hcd as a workaround? In any case
let's take this discussion off LKML so as not to spam the list with
binary only driver issues.
Lee
next prev parent reply other threads:[~2008-01-14 6:04 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
2008-01-14 5:30 ` Bryan Donlan
2008-01-14 6:04 ` Lee Revell [this message]
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=75b66ecd0801132204r5d4a5401hacc1de871342cf8c@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=bdonlan@gmail.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).