From owner-freebsd-mobile Tue Jul 23 14:21:59 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8260937B400 for ; Tue, 23 Jul 2002 14:21:55 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53EE943E4A for ; Tue, 23 Jul 2002 14:21:54 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.3/8.12.3) with ESMTP id g6NLLpYx012594; Tue, 23 Jul 2002 15:21:51 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 23 Jul 2002 15:06:49 -0600 (MDT) Message-Id: <20020723.150649.12657684.imp@bsdimp.com> To: tony@valemount.com Cc: mobile@FreeBSD.ORG, andrew@unfortu.net Subject: Re: PCI -> PCMCIA Adapter woes - patch From: "M. Warner Losh" In-Reply-To: <0f5001c23287$1a948530$114c35d1@tonyxp> References: <20020723194554.I32012-100000@plum.flirble.org> <0ee301c2327e$01a73a80$114c35d1@tonyxp> <0f5001c23287$1a948530$114c35d1@tonyxp> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message: <0f5001c23287$1a948530$114c35d1@tonyxp> "Tony Toole" writes: : Here is my patch to solve the problem you are having. It works very well, : and you can use regular PCI IRQ routing with no /boot/loader.conf tweaks : needed. NEWCARD also had the same problem, so this patch with subtle : changes should fix it as well. : : I have included the patch as an attachment as email tends to mangle them. First off, the IRQMUX register is 12xx and newer. The documentation for the MUX register indicates that it should be programmed once by the eeprom that's on the board. Chances are that this is a workaround for a bug in the card in question. However, a reasonable thing to do would likely be to do this if the low nibble of the word was 0 (configuring it for a GPIO input, that the code never uses), then set it up to do PCI signalling. I'm a little loathe to do this by default, because the docs say that you have to have terminal resistors on these multifuction pins to use them as outputs. However, given that this is the only way I know to drive the PCI bus, it may make good sense to do it anyway. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message