Date: Wed, 24 Sep 1997 09:26:59 -0600 (MDT) From: Nate Williams <nate@mt.sri.com> To: Stefan Esser <se@freebsd.org> Cc: Nate Williams <nate@mt.sri.com>, mobile@freebsd.org, current@freebsd.org Subject: Re: PCCARD in -current broken Message-ID: <199709241526.JAA12203@rocky.mt.sri.com> In-Reply-To: <19970924144744.47293@mi.uni-koeln.de> References: <199709231929.NAA08312@rocky.mt.sri.com> <19970923230018.00034@mi.uni-koeln.de> <199709232246.QAA09189@rocky.mt.sri.com> <19970924144744.47293@mi.uni-koeln.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> I assume you are sure that the PCCARD code is only
> called after the ISA devices are attached ?
In autoconf.c/configure:
#if NEISA > 0
eisa_configure();
#endif
#if NPCI > 0
pci_configure();
#endif
#if NISA > 0
isa_configure();
#endif
#if NCRD > 0
/* After everyone else has a chance at grabbing resources */
pccard_configure();
#endif
> Well, in fact you should see the "device combination doesn't support ..."
> message printed, when you call register_intr() to check for the interrupt
> to be available.
Hmm, do mobile users see these messages who run -current?
> If you don't then there is a good chance, that you perform
> this test, before the ISA devices are attached, and there is no collision
> reported until the PCCARD attach tries to register a handler for an assumed
> free IRQ, which has been claimed by an ISA driver in between ...
That shouldn't happen (given the code in autoconf.) Sorry for the false
alarm, back to the drawing board.
Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709241526.JAA12203>