From owner-freebsd-hackers Thu Feb 25 2:13:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hda.hda.com (hda-bicnet.bicnet.net [209.244.238.132]) by hub.freebsd.org (Postfix) with ESMTP id 5766414D6B for ; Thu, 25 Feb 1999 02:13:08 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id FAA24538; Thu, 25 Feb 1999 05:04:57 -0500 (EST) From: Peter Dufault Message-Id: <199902251004.FAA24538@hda.hda.com> Subject: Re: pccardd, pccardc, the LabPC+, and the NIDAQ 1200 In-Reply-To: <199902251003.DAA03943@harmony.village.org> from Warner Losh at "Feb 25, 99 03:03:21 am" To: imp@harmony.village.org (Warner Losh) Date: Thu, 25 Feb 1999 05:04:57 -0500 (EST) Cc: dufault@hda.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199902250938.EAA24470@hda.hda.com> Peter Dufault writes: > : Does anyone understand the interaction between pccardc, pccardd, and > : the access to I/O ports for pccards to know what the fix is? > > Generally I've had to hack the drivers to add pcmcia support to them. > Take a look at, for example, the ed or sio drivers to see how this is > done. Usually it is just a matter of a few lines. I did that part and during boot I see: > Initializing PC-card drivers: ep labpc sio Both ep and sio continue to work OK. I/O ranges and interrupts in pccard.conf permit 0x260 and 5 and I know I have no conflicts. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message