I'm sure you already have
looked at http://pcmcia-cs.sourceforge.net/ftp...A-HOWTO-4.html
, since it's on the first page of google("linux irq pcmcia").
Anything beyond that, I don't know--sorry.
Now, I'd like to quote from `Smart Questions', especially the part where I think you could learn something--it's meant as things you should grep for and read the whole context.
"When you ask your question, display the fact that you have done these things (searched the web, read the faq, ...) first."
Assuming--like I said--that you aren't asking this question because you're interested in PCMCIA-to-kernel interfacing, or the kernels ways of dealing with IRQ, but
because you want a specific piece of hardware and/or software to work and/or cooperate:
"Be precise and informative about your problem"
"Describe the symptoms of your problem or bug carefully and clearly."
"Describe the environment in which it occurs (machine, OS, application, whatever). Provide your vendor's distribution and release level (e.g.: `Fedora Core 4', `Slackware 9.1', etc.)."
also, "Describe the problem's symptoms, not your guesses"; "It's not useful to tell hackers what you think is causing your problem. (If your diagnostic theories were such hot stuff, would you be consulting others for help?)"
I think this exactly
what you're doing--you're displaying (double horror) only
or would someone tell me how to go about resource conflicts in general?
"Open-ended questions tend to be perceived as open-ended time sinks."
"In general, asking yes-or-no questions is a good thing to avoid unless you want a yes-or-no answer."
And finally "If you can't get an answer, please don't take it personally that we don't feel we can help you."
Sorry if you were offended by my curtness, mistaking it for arrogance.