From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sven-Thorsten Dietrich <sven@mvista.com>,
Yann.LEPROVOST@wavecom.fr, Daniel Walker <dwalker@mvista.com>,
linux-kernel@vger.kernel.org, linux-kernel-owner@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Ingo's realtime_preempt patch causes kernel oops
Date: Wed, 24 May 2006 18:55:06 +0200 [thread overview]
Message-ID: <1148489706.5239.68.camel@localhost.localdomain> (raw)
In-Reply-To: <1148488687.24623.67.camel@localhost.localdomain>
On Wed, 2006-05-24 at 12:38 -0400, Steven Rostedt wrote:
> OK I haven't worked on arm much at all. Only had to port one board
> before, and didn't need to get too involved.
>
> Can't two devices share the same interrupt line? Not talking about a
> cascading interrupt controller, but two actual devices that can trigger
> a single interrupt line. So, if this is the case, how do you disable a
> particular source without going to the driver itself?
Yeah, the demux code has to go into the device driver to figure that
out, which is not hard to do on SoC devices, as the peripherals are
usually unique for a given SoC family.
PCI and other globally shared devices are completely differnt beasts and
you would need a legion of hackers to fix that up.
tglx
next prev parent reply other threads:[~2006-05-24 16:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 13:40 Ingo's realtime_preempt patch causes kernel oops Yann.LEPROVOST
2006-05-23 14:09 ` Steven Rostedt
2006-05-23 14:19 ` Steven Rostedt
2006-05-23 14:26 ` Thomas Gleixner
2006-05-23 15:33 ` Daniel Walker
2006-05-23 16:02 ` Steven Rostedt
2006-05-23 16:27 ` Yann.LEPROVOST
2006-05-23 17:00 ` Steven Rostedt
2006-05-23 17:10 ` Yann.LEPROVOST
2006-05-23 18:21 ` Steven Rostedt
2006-05-24 8:06 ` Yann.LEPROVOST
2006-05-24 12:55 ` Steven Rostedt
2006-05-24 13:13 ` Thomas Gleixner
2006-05-24 15:32 ` Sven-Thorsten Dietrich
2006-05-24 15:52 ` Steven Rostedt
2006-05-24 16:03 ` Thomas Gleixner
2006-05-24 16:38 ` Steven Rostedt
2006-05-24 16:55 ` Thomas Gleixner [this message]
2006-05-24 17:09 ` Sven-Thorsten Dietrich
2006-05-24 16:06 ` Daniel Walker
2006-05-24 13:58 ` Yann.LEPROVOST
2006-05-24 16:43 ` Esben Nielsen
2006-05-24 17:06 ` Thomas Gleixner
2006-05-24 18:00 ` Sven-Thorsten Dietrich
2006-05-30 10:00 ` RT_PREEMPT problem with cascaded irqchip Yann.LEPROVOST
2006-05-30 10:27 ` Thomas Gleixner
2006-05-30 10:26 ` Yann.LEPROVOST
2006-05-30 11:22 ` Thomas Gleixner
2006-05-30 14:44 ` Yann.LEPROVOST
2006-05-30 23:25 ` Thomas Gleixner
2006-05-31 8:26 ` Yann.LEPROVOST
2006-05-24 17:30 ` Ingo's realtime_preempt patch causes kernel oops Sven-Thorsten Dietrich
[not found] <OF928FB2B7.5CE25C69-ONC1257177.00596B7A-C1257177.005AAA6F@wavecom.fr>
2006-05-23 16:38 ` Daniel Walker
2006-05-23 16:44 ` Thomas Gleixner
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=1148489706.5239.68.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=Yann.LEPROVOST@wavecom.fr \
--cc=dwalker@mvista.com \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=sven@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