From owner-freebsd-mobile Sat Nov 22 11:44:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA21607 for mobile-outgoing; Sat, 22 Nov 1997 11:44:10 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA21602 for ; Sat, 22 Nov 1997 11:44:06 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA08397; Sat, 22 Nov 1997 12:43:59 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA18819; Sat, 22 Nov 1997 12:43:58 -0700 Date: Sat, 22 Nov 1997 12:43:58 -0700 Message-Id: <199711221943.MAA18819@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Alan Batie Cc: mobile@FreeBSD.ORG Subject: Re: Hot upgrades In-Reply-To: <19971122101447.61698@agora.rdrop.com> References: <19971122101447.61698@agora.rdrop.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ Moved to -mobile ] > I just hot-upgraded my laptop from 2.1-PAO to 2.2.5, and now it's off > the net --- it seems that the pccard driver no longer accepts "default" > and "any" for interrupts and memory locations, but wants specific > numbers. 'any' for interrupt was a complete un-necessary hack since '?' was already there. 'default' for 'tuple' id's introduced bugs in the CIS parser code in pccardd, plus added a ton of complexity in already difficult to understand code. If I'm going to maintain the code I want to be able to understand it and also not have new functionality add new bugs. The tradeoff isn't worth it. :( > Which seems like a big step backwards if you ask me, but I haven't yet > gotten a chance to track down what's going on, so don't consider this > a bug report or a complaint yet (unless you know for sure that this was > what was supposed to happen :-) ). This was supposed to happen. The 'any' interrupt code won't go in, but the 'default' stuff should happen sometime, since it is a good thing. However, that's not going to be for a little while, so for now go find a nice configuration entry for your card to get it working using pccardc dumpcis. I'm sorry for breaking this support, but the code that implemented it was too nasty for me to integrate it. :( Nate