xserver/hw
Bjorn Helgaas bd0c829654 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.
2006-11-03 18:59:52 +01:00
..
darwin make core keyboard/pointer map functions act on all core-sending devices 2006-09-29 00:34:23 +03:00
dmx make core keyboard/pointer map functions act on all core-sending devices 2006-09-29 00:34:23 +03:00
kdrive kdrive:remove Change{Keyboard,Pointer}Device 2006-11-02 00:46:33 +02:00
vfb input: add non-keyboard bell ringing function 2006-11-01 23:10:26 +02:00
xfree86 Do not map full 0-1MB legacy range 2006-11-03 18:59:52 +01:00
xgl make core keyboard/pointer map functions act on all core-sending devices 2006-09-29 00:34:23 +03:00
xnest input: add non-keyboard bell ringing function 2006-11-01 23:10:26 +02:00
xprint Convert Xprt DDX to new motion history api 2006-11-02 18:30:58 -08:00
xwin make core keyboard/pointer map functions act on all core-sending devices 2006-09-29 00:34:23 +03:00
Makefile.am Xprint/ -> hw/xprint 2006-06-18 21:07:28 -04:00