From owner-freebsd-arch Fri Jan 5 15:50:41 2001 From owner-freebsd-arch@FreeBSD.ORG Fri Jan 5 15:50:38 2001 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id E98A937B400 for ; Fri, 5 Jan 2001 15:50:37 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f05NoTs42746; Fri, 5 Jan 2001 16:50:29 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101052350.f05NoTs42746@aslan.scsiguy.com> To: Paul Richards Cc: freebsd-arch@FreeBSD.ORG Subject: Re: Inheritance in new-bus. In-Reply-To: Your message of "Fri, 05 Jan 2001 23:45:40 GMT." <3A565CA4.3466BF11@originative.co.uk> Date: Fri, 05 Jan 2001 16:50:29 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >"Justin T. Gibbs" wrote: >> > >> >> Cardbus is no different than your ethernet card example. Cardbus is >> not a child bus of PCI, but is rather a specialized implementation of > >Yes, cardbus is specialized PCI, that's why inheritance would be >correct. Ethernet is not anything like PCI though so inheritance would >be wrong. Hmm. I thought you were implying that your ethernet driver might need to overload some method of its parent bus in order to deal with a special quirk of that piece of hardware. In otherwords, you wouldn't be a specialized version of PCI, but perhaps have a few specialized methods of a particular interface provided by your parent bus. In general, I would not expect this to happen. >> >I don't know which particular take on inheritance you've implemented, I >> >wouldn't mind getting a look at the patches :-) >> >> Several of PCI's methods are now exported in pci_private.h. Cardbus's >> method table now references several of these methods and occassionally >> one or more of its method overrides also calls into the PCI code to get >> some amount of work done. > >Yeah, this is where inheritance would be useful. > And it is only the first example of many to come I think. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message