From owner-freebsd-mobile Thu Dec 18 15:35:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA03103 for mobile-outgoing; Thu, 18 Dec 1997 15:35:39 -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 PAA03087 for ; Thu, 18 Dec 1997 15:35:28 -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 QAA19941; Thu, 18 Dec 1997 16:35:12 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA18248; Thu, 18 Dec 1997 16:35:00 -0700 Date: Thu, 18 Dec 1997 16:35:00 -0700 Message-Id: <199712182335.QAA18248@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ted Faber Cc: ambrisko@whistle.com, nate@mt.sri.com, freebsd-mobile@FreeBSD.ORG In-Reply-To: <199712182328.PAA23547@tnt.isi.edu> References: <199712182328.PAA23547@tnt.isi.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Nate, here's a patch to -current that addresses the issue Doug raised > of CL-PD6832's that are initialized to odd ports and also allows users > to specify a port for their pcic other than the bios default port. Ugh. I really dislike adding 'yet another' config option. > Right now, this added flexibility isn't worth much, because > /sys/pccard/pcic.c has its ports essentially hardwired at 0x3e0, but > it seems cleaner to me anyway. It should provide a way for users with > chips initialized to standard CArdBus operation to switch to 16-bit > legacy mode. So, wouldn't it be 'easier' to just hard-code the port to 0x3e0, since that's where the code expects to find it? > Doug and I (mostly Doug, since I don't see the same problems in my > setup) are still poking around with his interrupts so there may be > some more fixes to come, but this seems solid (and works fine on my > box with PCIC_PCI_PORT defined or not (defining it to other than 0x3e0 > boots, but the pcic driver doesn't find the chip). Then why allow the user to set it? Why not just hard-code it to 0x3e0 *always*? What would that break? Nate [ patch deleted ]