From owner-freebsd-mobile Wed Oct 11 17:32:54 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from gloworm.Stanford.EDU (gloworm.Stanford.EDU [171.64.99.46]) by hub.freebsd.org (Postfix) with ESMTP id 76E8E37B502 for ; Wed, 11 Oct 2000 17:32:52 -0700 (PDT) Received: from localhost (yergeau@localhost) by gloworm.Stanford.EDU (8.9.3/8.9.3) with ESMTP id RAA18755; Wed, 11 Oct 2000 17:32:43 -0700 (PDT) Message-Id: <200010120032.RAA18755@gloworm.Stanford.EDU> To: Wesley Morgan Cc: freebsd-mobile@freebsd.org, yergeau@gloworm.Stanford.EDU Subject: Re: FW: Linksys 10/100 PCMCIA card In-reply-to: Your message of "Wed, 11 Oct 2000 18:14:50 -0400." Date: Wed, 11 Oct 2000 17:32:43 -0700 From: Dan Yergeau Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org AFAICT, pccardd uses the free IRQ pool information specified in /etc/defaults/pccard.conf, /etc/pccard.conf, or via the "-I" argument to pccardd. It does not query the kernel for conflicts. I don't even think that there is a way for a user-level program to query the kernel to see which IRQ's have been assigned to any device, but I'm not a kernel hacker. The code for IRQ selection in /usr/src/usr.sbin/pccard/pccardd/cardd.c:assign_driver() is /* Allocate a free IRQ if none has been specified */ if (conf->irq == 0) { int i; for (i = 1; i < 16; i++) if (pool_irq[i]) { conf->irq = i; pool_irq[i] = 0; break; } if (conf->irq == 0) { logmsg("Failed to allocate IRQ for %s\n", cp->manuf); return (NULL); } } In any case, ensuring that there aren't IRQ conflicts seems to be currently left up to the user. This is discussed in the old PAO FAQ (http://www.jp.FreeBSD.org/PAO/) and in messages in the freebsd-mobile archives. It just doesn't appear to be mentioned loud enough in the documentation. Dan >Just some input -- I found that my PCMPC100v2 card was continually >assigned an irq that did not work, thus i was forced for manually >configure it based on the settings it was given under windows. I guess >that the OS does not test for irq conflicts with the other subsystems (in >my case it was conflicting with the built-in modem). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message