From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 13 18:44:45 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8FD9106564A for ; Mon, 13 Jul 2009 18:44:45 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id BCB008FC19 for ; Mon, 13 Jul 2009 18:44:45 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 6B5B246B6C; Mon, 13 Jul 2009 14:44:45 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 5BD188A094; Mon, 13 Jul 2009 14:44:44 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 13 Jul 2009 14:35:30 -0400 User-Agent: KMail/1.9.7 References: <4A5B3F1B.3040207@demig.de> In-Reply-To: <4A5B3F1B.3040207@demig.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907131435.30452.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 13 Jul 2009 14:44:44 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Norbert Koch Subject: Re: bus device driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2009 18:44:46 -0000 On Monday 13 July 2009 10:05:15 am Norbert Koch wrote: > Hello. > > I just started to write a device > driver for a multi-function pci card. > This card replaces a number of > independant isa hardware devices. > This pci card contains memory, i/o > and interrupt sources. > I want my device driver to > serve as a bus driver between > the pci driver and the specific > device drivers. > > Do I need more than the following (see below)? > Do I have to do any bookkeeping for allocated resources? How do the child devices receive resources? Do they suballocate regions from BARs in the PCI device or is your device a subtractive bridge that will forward requests for ISA ranges and your devices all use ISA ranges? -- John Baldwin