Date: Sun, 06 Aug 2000 21:30:57 -0600 From: Warner Losh <imp@village.org> To: Peter Radcliffe <pir@pir.net> Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: 4.0RELEASE and 3COM589EC Message-ID: <200008070330.VAA28709@harmony.village.org> In-Reply-To: Your message of "Sun, 06 Aug 2000 22:28:26 EDT." <20000806222826.B22130@pir.net> References: <20000806222826.B22130@pir.net> <200008070123.SAA04980@bubba.whistle.com> <200008070151.TAA28079@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20000806222826.B22130@pir.net> Peter Radcliffe writes: : Warner Losh <imp@village.org> probably said: : > Generally speaking, you can't. There are too many whacked out : > configurations in the wild to be able to do it always. However, it : > wouldn't be too hard to do this. It is waiting for an ioctl to be : > written for the card device that asks "Can I use this?" so pccardd can : > be hacked to cope. : : I have to say I did prefer the PAO approach of "what irqs can I : definately not use that I think I can" and let it sort out the rest. : Caused me fewer problems. We've generalized that into pccardd asking "Can I use this resource" of the kernel and the kernel saying "yes" or "no". One still needs to be able to control which irqs are used, and /etc/pccard.conf is the place for that if your machine needs special TLC for irqs or io addresses. Warner 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?200008070330.VAA28709>