From owner-freebsd-current@FreeBSD.ORG Mon Oct 17 19:06:48 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F20A916A41F for ; Mon, 17 Oct 2005 19:06:48 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9058743D45 for ; Mon, 17 Oct 2005 19:06:48 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9HJ5FQ6011916; Mon, 17 Oct 2005 13:05:15 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 17 Oct 2005 13:06:31 -0600 (MDT) Message-Id: <20051017.130631.73017921.imp@bsdimp.com> To: freebsd@psam.se From: "M. Warner Losh" In-Reply-To: <4353F3D5.6060309@psam.se> References: <4352E841.6000601@psam.se> <20051017.113630.35505791.imp@bsdimp.com> <4353F3D5.6060309@psam.se> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 17 Oct 2005 13:05:16 -0600 (MDT) Cc: freebsd-current@freebsd.org Subject: Re: Thoshiba Tecra 8000 with 3com 3CXFE575CT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2005 19:06:49 -0000 : When I start it outside and then connect the card it will detect and : configure it correctly. OK. This is a HUGE clue. One that shouldn't be overlooked :-). What it is telling me is that FUNCTION interrupts aren't getting through, but STATUS interrupts ARE getting through. I'll have to go re-read my two TOPIC data sheets to make sure, but I think that the TOPIC chips, especially the older ones, have a number of knobs for function interrupts that are not in the standard bridge chipset. Please refresh my recollection: Did this used to work with 5.4? IIRC, I did some work to fix o2 micro hangs that disabled the function interrupts during card insertion by routing them via IRQ 1 (which the o2micro actually doesn't route, so they just disappear). Maybe that work around had bad effects for the TOPIC95B that you have? Warner