From: Terence Ripperda <tripperda@nvidia.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Terence Ripperda <tripperda@nvidia.com>,
Roger Heflin <rheflin@atipa.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: What determines which interrupts are shared under Linux?
Date: Tue, 15 Aug 2006 12:43:38 -0500 [thread overview]
Message-ID: <20060815174338.GR7189@hygelac> (raw)
In-Reply-To: <44E20799.4060606@ru.mvista.com>
On Tue, Aug 15, 2006 at 09:42:49PM +0400, sshtylyov@ru.mvista.com wrote:
> Hello.
>
> Terence Ripperda wrote:
> >we've seen a lot of problems on ck804 chipsets when multiple devices
> >share level-triggered interrupts. I think some of the earlier sample
> >bioses assumed that interrupts would be configured via ACPI, and when
> >ACPI is not used, the interrupts end up as level-triggered instead of
> >edge-triggered.
>
> Edge-triggered *shared* interrupts?! Now that sounds interesting (I'm
> not saying impossible).
ah shoot, you're right. doing too much and got the two backwards.
ignore my email, I'm going off to sit in the corner with a dunce cap
on..
>
> WBR, Sergei
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
next prev parent reply other threads:[~2006-08-15 17:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 14:17 What determines which interrupts are shared under Linux? Roger Heflin
2006-08-15 14:30 ` Sergei Shtylyov
2006-08-15 14:38 ` Roger Heflin
2006-08-15 14:47 ` Len Brown
2006-08-15 15:06 ` Alan Cox
2006-08-15 15:24 ` Roger Heflin
2006-08-15 15:55 ` Alan Cox
2006-08-15 17:47 ` Roger Heflin
2006-08-15 18:13 ` Alan Cox
2006-08-16 22:54 ` Mark Lord
2006-08-17 0:39 ` Alan Cox
2006-08-17 13:18 ` Roger Heflin
2006-08-15 15:19 ` linux-os (Dick Johnson)
2006-08-15 17:31 ` Terence Ripperda
2006-08-15 17:42 ` Sergei Shtylyov
2006-08-15 17:43 ` Terence Ripperda [this message]
[not found] <fa.xiop2gho7OdOydmzXzpUsR5ksXM@ifi.uio.no>
2006-08-15 14:29 ` 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=20060815174338.GR7189@hygelac \
--to=tripperda@nvidia.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rheflin@atipa.com \
--cc=sshtylyov@ru.mvista.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;
as well as URLs for NNTP newsgroup(s).