From owner-freebsd-hackers Thu Feb 25 1:47: 2 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 004F714D1F for ; Thu, 25 Feb 1999 01:46:47 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id EAA24470 for hackers@freebsd.org; Thu, 25 Feb 1999 04:38:41 -0500 (EST) From: Peter Dufault Message-Id: <199902250938.EAA24470@hda.hda.com> Subject: pccardd, pccardc, the LabPC+, and the NIDAQ 1200 To: hackers@freebsd.org Date: Thu, 25 Feb 1999 04:38:40 -0500 (EST) 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 When I went to write a driver for the PCCARD NI DAQCard 1200 I was pleased to discover that it is register compatible with the LABPC+ with the exception of not supporting DMA. Since the FBSD driver doesn't support DMA it almost works perfectly out of the box. The gotcha is probing. The only way I can get it to probe is with the following machinations. First I run pccardd with this entry in /etc/pccard.conf: > card "National Instruments" "DAQCard-1200" > config 0x1 "labpc0" 5 > insert echo National Instruments DAQCard-1200 inserted > remove echo National Instruments DAQCard-1200 removed and it will then fail with a "Return IRQ=5" on the console and the no "driver allocation failed" message from pccardd. Now if I enable it by hand using pccardc via: pccardc enabler 1 labpc0 -a 0x260 -i 5 it pops up and works fine. If I don't first use "pccardd" "pccardc" doesn't work at all - it won't do a "dumpcis", pccardd must initialize something. Kernel config is: > device labpc0 at isa? port 0x260 tty irq 5 vector labpcintr I assume the kernel looks here for the I/O port, and breakpoints in the probe show that when probed via pccardd it is looking at 0x260, however, it fails the probe when it can't overrun the ADC FIFO. Does anyone understand the interaction between pccardc, pccardd, and the access to I/O ports for pccards to know what the fix is? 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