> > 1) The memory mapped by 'vremap' is marked cacheable. This
> > is (almost certainly) incorrect as it is memory that is
> > actually device memory. Note that the mmap call used by
> > X servers marks the memory as uncached.
>
> The PC architecture is supposed to handle this for you. It could well
> be an issue on MIPS and friends. The X one is hack and shouldnt be needed
what shouldn't be needed? turning off caching for a mapped frame buffer ?
or did I miss your point ?
how would you guarantee data/display integrity (esp. for WB cache) if you're
changing the frame buffer sometimes by direct access to the frame buffer by the CPU
and sometimes by using the graphics engine ? otherwise you'd have to flush the cache
for very cpu <-> graphics engine tansition
Harald
--
All SCSI disks will from now on ___ _____
be required to send an email notice 0--,| /OOOOOOO\
24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
\ OOOOOOOOOOOOOOOOO|//
Harald Koenig, \/\/\/\/\/\/\/\/\/
Inst.f.Theoret.Astrophysik // / \\ \
koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^