From owner-freebsd-current@FreeBSD.ORG Mon Apr 7 00:14:44 2003 Return-Path: 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 2191037B401 for ; Mon, 7 Apr 2003 00:14:44 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40FA643FAF for ; Mon, 7 Apr 2003 00:14:43 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h377EVA7089544; Mon, 7 Apr 2003 01:14:31 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 07 Apr 2003 01:12:58 -0600 (MDT) Message-Id: <20030407.011258.62370040.imp@bsdimp.com> To: mat@cnd.mcgill.ca From: "M. Warner Losh" In-Reply-To: <20030407064749.GO17533@cnd.mcgill.ca> References: <20030406164134.GN17533@cnd.mcgill.ca> <20030407.000118.68039554.imp@bsdimp.com> <20030407064749.GO17533@cnd.mcgill.ca> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: midi problem, an isa device on a pci card X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 07 Apr 2003 07:14:44 -0000 In message: <20030407064749.GO17533@cnd.mcgill.ca> Mathew Kanner writes: : Hello Warner, : Thanks for your comments, it helps keep me interested as this : is only a for fun hacking project. : : On Apr 07, M. Warner Losh wrote: : > You can't create ISA devices that are parented to the pci bus. You : > just can't. : : I don't understand your comment, isn't the newly created : devices parent the (first) ISA bus? I scan for the isa class, get : device instances and create from there. I'm saying that what you are doing isn't right and won't work too well. If the device is on the pci bus, you have to create a pci attachment. : > You have to make them be full pci devices. : > Hweover, this : > is relatively easy to do. You hacks will just not work. : : But it's an ISA device on on a pci card. that's not possible. It is *NOT* an ISA device unless it is on a card that has ISA fingers on it. Otherwise it *IS* a PCI device. Does the pci card have a PCI to ISA bridge on it? If not, then you have to deal with it as a PCI bus. : I don't know this : for sure but the soundcard docs talk about special hardware to appear : as a legacy device, also, all pci devices on my machine have 4 byte : port ranges while this and other ISA devices have 3. I don't understand this. : I can send and receive on the MPU, albeit, sending is screwy : either too fast or too slow, (too slow by itself, too fast when I : force feed interrupts with timeout(), sigh, I wonder if send interrupts : are broken for mpus in general). : kldload and unload both the pci(soundcard) and the isa(mpu) : drivers seem to work well. You likely need to attach the mpu device to the pci soundcard in some way, or if the pci device has its own function, directly to the pci device. Chances are excellent that's what the interrupt problem you are encountering are. Warner