From owner-freebsd-arch@FreeBSD.ORG Mon Sep 22 08:52:31 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADD9916A4C2 for ; Mon, 22 Sep 2003 08:52:31 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96A6E43FE0 for ; Mon, 22 Sep 2003 08:52:30 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9p1/8.12.3) with ESMTP id h8MFqTGA041818; Mon, 22 Sep 2003 09:52:29 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 22 Sep 2003 09:52:25 -0600 (MDT) Message-Id: <20030922.095225.85015472.imp@bsdimp.com> To: dfr@nlsystems.com From: "M. Warner Losh" In-Reply-To: <1064221837.15078.14.camel@herring.nlsystems.com> References: <1064221837.15078.14.camel@herring.nlsystems.com> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: arch@freebsd.org Subject: Re: kobj multiple inheritance X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 15:52:31 -0000 In message: <1064221837.15078.14.camel@herring.nlsystems.com> Doug Rabson writes: : This effectively allows all pci : drivers to get into the cardbus probe. If a particular driver needs to : treat its cardbus attachment specially, it can still do this by adding a : special cardbus driver (e.g. with a cardbus specific probe or attach : method) to the cardbus devclass (exactly as it does now). So if there's devices that can only be "base" pci, and have issues with all other types of pci-like buses, is there a way to say "only on pci bus, but none of the derived buses"? Or is it better to list those derived buses that are known to cause problems? I'd imagine that these devices would be rare, but I've worked on one.... Also, we're violating the PC Card spec by not matching the CIS values, but reading the vendor/device instead. Technically, this is a violation and those registers aren't reqiured to be defined. So far, nobody has showed up with devices that don't have them, but I thought I'd point this out. It has been theorized that this is because so many designs share silicon with PCI. Warner