possible resource conflicts
 

how would i check for an irq conflict on a pcmcia device and how would i go about fixing it?

or would someone tell me how to go about resource conflicts in general.

My best guess is as to why you're asking this is because you have some problem at hand you want fixed, not because you're interested in the intricacies of the way Linux does interrupt requests (in particular with relevance to pcmcia devices).

If I'm right, go read http://www.catb.org/~esr/faqs/smart-questions.html. If I'm wrong, I apologise for being unhelpful.

--Jonas

Nothing to say!
 

Hello!

Hmmm... To be honest, I never met something less usefull than your reply. 90% of people here ask questions because they have problems and don't know how to solve those problems. That's our nature - noone can know everything.

So, if you know the answer - place it here. In any form - open text, link, reference to the proper page in the book... Be heplfull and usefull, share your knowledge. But send somebody to the page teaching how to ask questions - is simply silly, sorry... If you have nothing to say, just keep silence.

Regards,
A.

P.S. Yes, I'm one of those 90% - I ask questions about my daily problems in Linux.
P.S.2 Perhaps, MS is a criminal company. But in WinXP I could use my modem to send faxes, my cell phone was recognized via IrDA and I could see pretty fonts... Everything has its advantages and disadvantages.

Hi.

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 your guess.

No.

"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.

--Jonas

And helping would be more easy with more detailed descriptions
of the problem; hence Jonas' attmept to encourage the person
to be more verbose/descriptive; and "How to ask questions the
smart way" is a VERY valuable ressource on the way there.
I suggest you read it, too.


And ifyou haven't got anything constructive to contribute to a thread:
take your own advice. If it really bugs you that much, either take it
up with the poster in a private e-Mail exchange or (if for example
he has e-Mailing disabled) report the post to a mod.

Neither of these has got anything to do with anything in this
thread, really ... what was that in aid of?



Cheers,
Tink

strange thread
first let me say i understood the question (which is unusual for me)
must have been everybody is crashing from an extended bender and angry at the world for asking about things they don't understand.

you can look at lspci -v and get some info about IRQ.
and look in /proc
cat /proc/interrupts

The only think i think you could do is mess with the BIOS settings and more junk around in the case.
try reading
http://www-128.ibm.com/developerwork...ary/l-hw2.html
http://www.scyld.com/pci_irq.html
http://www.xml.com/ldd/chapter/book/ch09.html

it is fairly rare in Linux for IRQ sharing to cause any latency or problems but given a crappy driver all things are possible.