From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: Linus Torvalds <torvalds@osdl.org>,
Russell King <rmk+lkml@arm.linux.org.uk>,
Andrew Morton <akpm@osdl.org>,
Andreas Mohr <andi@rhlx01.fht-esslingen.de>,
florin@iucha.net, linux-kernel@vger.kernel.org,
linux@dominikbrodowski.net
Subject: Re: pcmcia oops on 2.6.17-rc[12]
Date: Mon, 22 May 2006 23:38:28 +0100 [thread overview]
Message-ID: <1148337508.17376.147.camel@localhost.localdomain> (raw)
In-Reply-To: <20060522212724.GC9454@bitwizard.nl>
On Llu, 2006-05-22 at 23:27 +0200, Rogier Wolff wrote:
> Fine. I know hardware that /cannot/ share interrupts. So, my driver
> requesting an interrupt, and getting: "Can't allocate interrupt" is an
> indication of a hardware configuration error. Or software (you've been
> telling one of the drivers the wrong interrupt line). If you force
> "shared mode", my driver will cope (it works just great on the PCI
> version of the card, no problem). But will the hardware?
Depends on the backplane
> You guys maybe trying to fix very real problems in PCMCIA land, of
> which I have very little knowledge. But changing what "not passing
> SA_SHIRQ" means globlaly IMHO changes too much...
PCMCIA doesn't need any big changes. The rules are simple. PCMCIA IRQs
today are shared, period. Because of the way the hardware works this
isn't an electrical issue. Drivers that ask for an exclusive PCMCIA IRQ
need to wake up and smell the coffee and get fixed.
Alan
next prev parent reply other threads:[~2006-05-22 22:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 19:22 Florin Iucha
2006-04-23 22:02 ` Andrew Morton
2006-04-23 22:15 ` Randy.Dunlap
2006-04-24 0:46 ` Florin Iucha
2006-05-08 14:56 ` Andreas Mohr
2006-05-08 15:43 ` Andrew Morton
2006-05-08 16:34 ` Russell King
2006-05-15 22:07 ` Alan Cox
2006-05-15 22:00 ` Russell King
2006-05-18 11:10 ` Russell King
2006-05-15 22:02 ` Linus Torvalds
2006-05-15 23:00 ` Alan Cox
2006-05-15 23:37 ` Linus Torvalds
2006-05-15 23:52 ` Linus Torvalds
2006-05-16 0:17 ` Alan Cox
2006-05-16 0:18 ` Linus Torvalds
2006-05-16 1:18 ` Alan Cox
2006-05-16 15:16 ` Alan Cox
2006-05-22 11:50 ` Rogier Wolff
2006-05-22 12:10 ` Alan Cox
2006-05-22 21:27 ` Rogier Wolff
2006-05-22 22:38 ` Alan Cox [this message]
2006-06-02 19:09 ` Russell King
2006-05-22 15:06 ` Linus Torvalds
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=1148337508.17376.147.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=R.E.Wolff@BitWizard.nl \
--cc=akpm@osdl.org \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=florin@iucha.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.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
Powered by JetHome