From owner-freebsd-hackers@FreeBSD.ORG Tue May 30 14:29:34 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D7A416A46A for ; Tue, 30 May 2006 14:29:34 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56E1443D46 for ; Tue, 30 May 2006 14:29:30 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k4UEJsZT077923; Tue, 30 May 2006 08:19:59 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <447C548C.4080302@samsco.org> Date: Tue, 30 May 2006 08:19:56 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <20060524153153.GF49081@funkthat.com> <87ab37ab0605280309s15a31cb4yc8a54be1af5472dd@mail.gmail.com> <87ab37ab0605300642ja608c97s24836a317cdac24@mail.gmail.com> <20060530.075818.-820706528.imp@bsdimp.com> In-Reply-To: <20060530.075818.-820706528.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-hackers@freebsd.org, avalonwallace@gmail.com, dely.l.sy@intel.com Subject: Re: misc questions about the device&driver arch 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: Tue, 30 May 2006 14:29:35 -0000 M. Warner Losh wrote: > : THIRD > : Because the PCIE configure space is 4k long ,shall we change the > : #define PCI_REGMAX 255 > : to facilitate the PCI express config R/W? > > Maybe. Lemme investigate because PCIe changes this from a well known > constant for all pci busses, to a variable one... > > Warner When I added PCIe extended config support, I never took into consderation the userland access point of view. Changing this definition to 4096 might Just Work, and it might Not Work. Dunno. In the 18 months since I implemented it, no other person has asked about userland access. Other than the silly case of people trying to write device drivers in PERL, I'm not sure how much value it gives compared to the stability and security risk it imposes. Scott