From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 19 00:35:27 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF74316A4CE for ; Sat, 19 Feb 2005 00:35:27 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91D4943D46 for ; Sat, 19 Feb 2005 00:35:27 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by rproxy.gmail.com with SMTP id f1so12913rne for ; Fri, 18 Feb 2005 16:35:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=alGa41fY155SfDNhX1OCFZig4pDLKHP40wzb1qmepzQh7xBFhrSPBQOSNyS4vP42u5CC3A4TdX9NtR6o0XiESBn/2ER4+U9QCirYkIBruyPoJwcn6a5P4RRZoLpNpCPeymmT9XDfBU/N7JLXTqQFibY7J/cvWx8/jN78KfTmQl8= Received: by 10.38.68.14 with SMTP id q14mr99999rna; Fri, 18 Feb 2005 16:35:26 -0800 (PST) Received: by 10.38.22.22 with HTTP; Fri, 18 Feb 2005 16:35:26 -0800 (PST) Message-ID: <346a802205021816354ebbd91e@mail.gmail.com> Date: Fri, 18 Feb 2005 19:35:26 -0500 From: Coleman Kane To: Warner Losh In-Reply-To: <20050218.131311.104079154.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050218.102310.74705720.imp@bsdimp.com> <200502181249.53139.jkim@niksun.com> <346a8022050218113126c1af5f@mail.gmail.com> <20050218.131311.104079154.imp@bsdimp.com> cc: freebsd-amd64@freebsd.org Subject: Re: PC Card subpart to R3000 thread X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cokane@cokane.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Feb 2005 00:35:28 -0000 On Fri, 18 Feb 2005 13:13:11 -0700 (MST), Warner Losh wrote: > > There are a number of issues relating to it, which makes it hard to > solve generically (well, one could always write 255 as the subbus > number, but that has some rather severe performance implications... > > Warner > How do we keep track of the busses now? What considerations must be taken into account regarding setting the numbering this subordinate bus number? In the patch code it seems that it is setting this register to the same value as the bus number (10). You are stating that it can be set to any number (PCIR_SUBBUS_1 that is)? -- coleman