From owner-freebsd-current Thu Jan 27 13: 4:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id B1B33156BF for ; Thu, 27 Jan 2000 13:04:38 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 15CE61CD4; Fri, 28 Jan 2000 05:04:36 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Matthew N. Dodd" Cc: Warner Losh , Edwin Mons , current@FreeBSD.ORG Subject: Re: ep0 incorrectly probed In-Reply-To: Message from "Matthew N. Dodd" of "Thu, 27 Jan 2000 15:15:49 EST." Date: Fri, 28 Jan 2000 05:04:36 +0800 From: Peter Wemm Message-Id: <20000127210436.15CE61CD4@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > On Fri, 28 Jan 2000, Peter Wemm wrote: > > pnpinfo doesn't have anything to do with what the kernel thinks. It's a > > userland program that manually resets and reconfigures the cards.. This is > > an absolute disaster if you happened to be using the hardware, eg: the soun d > > driver. After running pnpinfo, the hardware essentially "disappears". > > > > pciconf(8) does it properly, it asks the kernel via /dev/pci. pnpinfo uses > > /dev/io to bash on the ports directly. > > Thats kinda weird seeing as how pnpinfo correctly reports the settings as > detected/assigned by the kernel for all other cards. Hmm, I take some of that back. I'm still not 100% sure of the implications of what I'm seeing in src/contrib/pnpinfo, but it still makes me nervous. For example: Logical device #0 IO: 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 IRQ 5 0 DMA 1 0 IO range check 0x00 activate 0x01 versus: pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 Which is right? Does the device really have all 8 IO ranges assigned to the same address? (0x534) Or is pnpinfo wrong? Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message