From owner-freebsd-mobile Thu Mar 23 8:29:17 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id 3C96537B558 for ; Thu, 23 Mar 2000 08:29:09 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id JAA20956; Thu, 23 Mar 2000 09:29:05 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id JAA02977; Thu, 23 Mar 2000 09:29:04 -0700 (MST) (envelope-from nate) Date: Thu, 23 Mar 2000 09:29:04 -0700 (MST) Message-Id: <200003231629.JAA02977@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: nate@yogotech.com (Nate Williams), mobile@FreeBSD.ORG Subject: Re: 4.0 a severe disappointment In-Reply-To: <200003231624.JAA41343@harmony.village.org> References: <200003231618.JAA02894@nomad.yogotech.com> <200003230551.WAA37833@harmony.village.org> <200003230830.IAA00509@hak.lan.Awfulhak.org> <200003231624.JAA41343@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > : > Indeed. FWIW, a friends laptop has a strange allergy to irq 10.... > : > *any* pccard that's given irq 10 will just not work (modem's one > : > character behind etc), as if the controller itself couldn't handle > : > it. In fact, if you give the controller irq 10, nothing works ! > : > : What probably is the issue is the underlying hardware uses IRQ 10. On > : my ThinkPad, the CardBus controller uses up IRQ 10, even though FreeBSD > : doesn't support Cardbus. However, I *still* have to assign another IRQ > : to it for PCMCIA legacy support as well, so I lose two interrupts. :( > > There's a problem with interrupt sharing in legacy mode for mode > cardbus bridges. Since I don't have the tools to troubleshoot why > this would be the case (no bus analyser, no clue where to connect it > if I did, etc), I can only speculate it is due to the level vs edge > interrupt nature of the card. > > The list of interrupts in the pccard's cis is hard coded into roms on > the pccard itself. It should be completely ignored. And to add to this, the entire resource allocation scheme in the cards can be safely ignored for the most part. Some of the drivers (most notably sio) want the card to use the same resources as they expect, but those resources are assigned by pccardd/kernel, and can be almost anything that doesn't conflict with already existing devices.. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message