Date: Thu, 19 Nov 1998 12:57:04 -0200 (EDT) From: Joao Carlos Mendes Luis <jonny@jonny.eng.br> To: nate@mt.sri.com (Nate Williams) Cc: jonny@jonny.eng.br, roger@cs.strath.ac.uk, mobile@FreeBSD.ORG Subject: Re: strange behavious of two PCMCIA modem cards Message-ID: <199811191457.MAA20669@roma.coe.ufrj.br> In-Reply-To: <199811190610.XAA02387@mt.sri.com> from Nate Williams at "Nov 18, 98 11:10:46 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
#define quoting(Nate Williams) // > // My question then is, why can I not hard code the IRQ. // // My guess is that on 3.0 something changed in the way the interrupts are // being used, *OR* the probes have somehow awakened some part of your // hardware that is using the IRQ in question. // // > Take a look at the output of pccardc dumpcis, and verify which are the // > valid interrupts for config 0x20. Maybe irq 11 is not a valid one. // > You cannot chose irqs on the fly if the card does not support them. // // Actually, the interrupts and the I/O ports the card's claim to use are // completely irrelevant since the PCIC controller can map them to be // anywhere. I could not change my ethernet card irq from its default 5. Do you have another explanation for that ? I'm running 3.0, could it be the problem you said above ? Its configuration code allows only irq 5. The card is a D-Link DE660. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811191457.MAA20669>