Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Feb 2009 11:27:23 -0600
From:      Nathan Whitehorn <nwhitehorn@freebsd.org>
To:        John Baldwin <jhb@FreeBSD.org>
Cc:        svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org
Subject:   Re: svn commit: r188018 - in head: sys/dev/pci usr.sbin/pciconf
Message-ID:  <49A57F7B.3040704@freebsd.org>
In-Reply-To: <200902021954.n12JsGT2005768@svn.freebsd.org>
References:  <200902021954.n12JsGT2005768@svn.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote:
> Author: jhb
> Date: Mon Feb  2 19:54:16 2009
> New Revision: 188018
> URL: http://svn.freebsd.org/changeset/base/188018
> 
> Log:
>   - Add a new ioctl to /dev/pci to fetch details on an individual BAR of a
>     device.  The details include the current value of the BAR (including all
>     the flag bits and the current base address), its length, and whether or not
>     it is enabled.  Since this operation is not invasive, non-root users are
>     allowed to use it (unlike manual config register access which requires
>     root).  The intention is that userland apps (such as Xorg) will use this
>     interface rather than dangerously frobbing the BARs from userland to
>     obtain this information.
>   - Add a new sub-mode to the 'list' mode of pciconf.  The -b flag when used
>     with -l will now list all the active BARs for each device.
>

Do you happen to have any patches for libpciaccess to use this?

Libpciaccess (and so the latest Xorg server) hoses my PowerPC machine 
when trying to list BARs, but pciconf -b works correctly. There are 
probably endianness problems in the libpciaccess code, and it would be 
nice to just replace that mess with this interface.
-Nathan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49A57F7B.3040704>