[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Using wsdisplay from the Xserver
-----BEGIN PGP SIGNED MESSAGE-----
On Jan 24, 2009, at 5:30 PM, der Mouse wrote:
That's an interface which is already there and used by X.
That's the problem. X has no business dealing with the level of PCI
config registers; that's for the PCI attachment code for the graphics
hardware to deal with. See also below.
Why reinvent the wheel?
Because the one that's there is the wrong wheel. The X server should
be telling the driver "give me the $FOO registers", not mucking about
with PCI config itself.
That's exactly what this ioctl() is doing.
What if the attachment the chip is behind isn't PCI? Userland
shouldn't care about that any more than it cares about whether a
file is on a bha-attached Seagate drive or a Firewire-attached
Western Digital drive.
Feel free to rewrite the Xserver and all its drivers.
Accessing a graphics chip's config space is ok in my book and indeed
The _graphics chip_'s config space, yes.
Again - that's all it gets.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
-----END PGP SIGNATURE-----
Main Index |
Thread Index |