xserver/hw
Bjorn Helgaas 58653b676d Do not map full 0-1MB legacy range
If we're mapping something in the "legacy range" (0-1Mb), we shouldn't
expand the requested range to the entire 0-1Mb range.  Typically this
is for mapping the VGA frame buffer, and some platforms support mmap of
the frame buffer but not the entire 0-1Mb range.

For example, HP sx1000 and sx2000 ia64 platforms can have memory from
0-0x9ffff, VGA frame buffer from 0xa0000-0xbffff, and memory from
0xc0000-0xfffff.  On these platforms, we can't map the entire 0-1Mb
range with the same attribute because the memory only supports WB,
while the frame buffer supports only UC.  But an mmap of just the
frame buffer should work fine.
(cherry picked from bd0c829654 commit)
2006-11-08 10:18:51 -05:00
..
darwin remove .cvsignores from EXTRA_DIST 2006-07-30 11:11:59 +03:00
dmx Check for visual==NULL in dmxBECreateColormap() before calling XCreateColormap() 2006-10-11 16:02:00 -04:00
kdrive Fix previous commit breaking other kdrives pulling in fbdev.a 2006-08-31 17:30:24 +01:00
vfb Make 'Xvfb -render' also disable Composite, lest we segfault on startup. 2006-08-23 14:38:34 -04:00
xfree86 Do not map full 0-1MB legacy range 2006-11-08 10:18:51 -05:00
xgl get rid of XFree86LOADER, XFree86Server, XFree86Module, and IN_MODULE 2006-07-18 18:17:38 -04:00
xnest Make sure _XSERVER64 is defined when it should be and gets tested. 2006-09-06 15:20:55 +02:00
xprint * Install Xprint's Xsession script to $(sysconfdir)/X11/Xsession.d 2006-10-11 16:01:00 -04:00
xwin Apply patch in bug #7919, blit improvements in 2006-08-24 13:56:22 +01:00
Makefile.am Xprint/ -> hw/xprint 2006-06-18 21:07:28 -04:00