From owner-freebsd-current Tue Sep 23 12:30:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA29339 for current-outgoing; Tue, 23 Sep 1997 12:30:02 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA29304; Tue, 23 Sep 1997 12:29:40 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id NAA23638; Tue, 23 Sep 1997 13:29:37 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA08312; Tue, 23 Sep 1997 13:29:37 -0600 (MDT) Date: Tue, 23 Sep 1997 13:29:37 -0600 (MDT) Message-Id: <199709231929.NAA08312@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: mobile@freebsd.org, current@freebsd.org CC: se@freebsd.org Subject: PCCARD in -current broken X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ Forgive the cross-posting, the information is of interest to a number of folks. ] It has been for some time (May). If it works on your box, you're lucky! (PHK is one of the lucky ones, and it may be related to using more PCI-like machines, unlike older 'straight-ISA' laptops). The change to the 'generic' shared interrupt code broke some assumptions I had about 'register_intr()' and 'unregister_intr()' in /sys/pccard/pcic.c. Basically, I had assumed the register_intr() would fail if I wanted access to an interrupt that was already taken, and now it succeeds so I add it to my list of 'available' IRQ's (I'd give it back, but at this point the freemask is really hosed). This assumption leads to all sorts of problems, of which I haven't completely thought about. In any case, until the code in /sys/kern/kern_intr.c ifdef'd out by 'RESOURCE_CHECK' is finished, or something else is done to make sure that 'ISA/Exclusive' interrupts are not allowed to be registered as 'shared' resources, I think there are potential problems with the current scheme, and may even effect 'normal' (non-laptop) systems who use ISA devices, though it's doubtful they do silly things like I'm doing in the PCCARD code. I don't have any solutions in the short-term, but I wanted to let folks know about the possible problems. Nate ps. The code in 2.2.* is not affected, since the new interrupt code only lives in -current.