Date: Tue, 30 May 2006 22:42:22 +0800 From: "william wallace" <avalonwallace@gmail.com> To: "Scott Long" <scottl@samsco.org> Cc: freebsd-hackers@freebsd.org, John-Mark Gurney <gurney_j@resnet.uoregon.edu> Subject: Re: misc questions about the device&driver arch Message-ID: <87ab37ab0605300742h14493096gbf8cb05e72bacd74@mail.gmail.com> In-Reply-To: <447C548C.4080302@samsco.org> References: <20060524153153.GF49081@funkthat.com> <87ab37ab0605280309s15a31cb4yc8a54be1af5472dd@mail.gmail.com> <87ab37ab0605300642ja608c97s24836a317cdac24@mail.gmail.com> <20060530.075818.-820706528.imp@bsdimp.com> <447C548C.4080302@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/30/06, Scott Long <scottl@samsco.org> wrote: > 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 > > I have to clarify my intentions that i am not TRYing to do a userland PCI express driver . I just want to make a interesting branch whitch can do pci express native Hot plug and hot remove ,with Mr Losh and other gentlemen's help ,i am making progress ,and now a loadable module is finishing . I have borrowed many Ideas from Linux ,but several fatal difficulties paused me ,with the PCI_REGMAX included. wish to hear from u :) thank u! -- we who r about to die,salute u!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87ab37ab0605300742h14493096gbf8cb05e72bacd74>