From owner-freebsd-hackers Sat Jan 20 20:11:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8489537B402 for ; Sat, 20 Jan 2001 20:11:40 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id XAA11930; Sat, 20 Jan 2001 23:11:40 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f0L4BdU08206; Sat, 20 Jan 2001 23:11:39 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Jan 2001 23:11:39 -0500 (EST) To: Nicolas Souchu Cc: freebsd-hackers@freebsd.org Reply-To: trim-your-headers@loopback.net Subject: Re: more info about: odd result of pci_read_config In-Reply-To: <20010121004349.A27198@ontario.alcove-int> References: <20010120161834.B20753@ontario.alcove-int> <20010121004349.A27198@ontario.alcove-int> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14954.24548.925891.707424@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicolas Souchu writes: <...> > What is the hose field? It is for server-class alphas. Alphas do their peer PCI buses a little differently. Rather than have a ppb between "peer" pci buses, each different peer bus (or hose) is rooted separately at the nexus. So you can have two PCI buses labeled "0" with no ppb between them, for example. Platform support code needs to know which hose a bus is on so that it can diddle with the correct set of registers to access memory, i/o and pci config spaces. > cfg.hose = -1; If you need to set this, please set it to zero so that it and any code derived from it will have at least a fighting chance of working on alpha, where this field is not ignored.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message