From owner-freebsd-hackers Thu Nov 12 08:56:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27508 for freebsd-hackers-outgoing; Thu, 12 Nov 1998 08:56:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27503 for ; Thu, 12 Nov 1998 08:56:31 -0800 (PST) (envelope-from lile@stdio.com) Received: from localhost (lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id LAA29057; Thu, 12 Nov 1998 11:59:38 -0500 (EST) (envelope-from lile@heathers.stdio.com) Date: Thu, 12 Nov 1998 11:59:37 -0500 (EST) From: "Larry S. Lile" To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: Re: PCI device question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Nov 1998, Ron G. Minnich wrote: > On Thu, 12 Nov 1998, Larry S. Lile wrote: > > What is the "64 byte PCI configuration space header" and where do I get > > that from (what pci_* call) > > > > I already know the io-base address, dma-level, csn, pci slot, ... from > > another call. > > That's where stuff like base address etc. are. If you have pulled out > base address info via config read and friends then you already know. If > you are not pulling base etc. out via config reads then you have to fix > your driver :-) > > Functions look like this: > int data = pci_conf_read(tag, PCI_CLASS_REG); > > Are you using these? No, there is a probe function in the driver kit that will find all of the adapters presumably through PIO, so I have not neede to delve into this yet. They then want a pointer into the right spot in memory for the config. info passed into another function. What I need is a way to get a pointer (char *) to the beginning of the config. info for a particular card (one with a PCI ID of 108D0001). Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message