Date: Tue, 18 Jun 2013 09:25:47 -0600 From: Warner Losh <imp@bsdimp.com> To: Andriy Gapon <avg@FreeBSD.org> Cc: arch@FreeBSD.org, Niclas Zeising <zeising@FreeBSD.org>, Marius Strobl <marius@alchemy.franken.de> Subject: Re: Bus space routines Message-ID: <F54B68BD-ABD6-4A29-8E64-56D3E326186C@bsdimp.com> In-Reply-To: <51C07A2F.3060504@FreeBSD.org> References: <51C0345E.4000309@freebsd.org> <20130618111351.GA43938@alchemy.franken.de> <51C07A2F.3060504@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 18, 2013, at 9:18 AM, Andriy Gapon wrote: > on 18/06/2013 14:13 Marius Strobl said the following: >> What we really need is a proper interface allowing userland to access >> PCI I/O and memory registers, f. e. via /dev/pci, and for = libpciaccess >> to build upon that, i. e. essentially the same as things work on/with >> Linux and /sys/bus/pci/device. As a side-effect this then also = permits >> to properly sanity check PCI accesses from userland within the = kernel. >=20 > We have this pciconf utility (in base), which can read PCI config = registers (and > more). Apparently it uses some ioctl interface of /dev/pci. > Is this the interface that you had in mind or does it lack some = required capabilities? It reads config space registers. This thread is about memory and/or I/O = spaces that are mapped via BARs on the device. We have no generic = interface to do that (although adding a memory mapped one for memory = BARs wouldn't be hard). Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F54B68BD-ABD6-4A29-8E64-56D3E326186C>