I'll take a look into this. I'm not sure libpciaccess uses /dev/mem
anymore though?
Thanks!
Alex
--
<>
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscr
> Does mapping the whole BAR work? If so it'd be trivial to change the
> driver to just do that instead, and it should be harmless.
As far as I can tell, no:
[root@tpad ~]# ./testneo
neomagic nm2160 found
phys_base: 0xfd00 phys_len: 0x0100
attempt pci_device_map_range of 0x0100
pci_de
Hi Michel,
Thank you very much for the insight on CONFIG_IO_STRICT_DEVMEM. I was able to
use SystemTap to find where the error was occurring in the kernel. It turns out
the vesafb takes the framebuffer and sets it IO_RESOURCE_BUSY using sysfb. When
the framebuffer memory is set as busy and the
