> The problem:
> The agpgart usage model is not well suited for UMA architectures because
> each gart user is expected to allocate memory and only bind it into
> the gart while it is active. Therefore on systems where all graphics
> memory is obtained from the gart a huge amount of system memory is
> wasted (16 Megs is probably a common amount of wasted memory on a
> system running 2 X servers). To further the problem this memory is
> non-swappable.
> The issue has become exacerbated on embedded devices that must have
> a framebuffer console for smooth graphics transitions during boot.
> The framebuffer console must share a framebuffer among the virtual
> terminals and eventually share resources with X.
> 
> Solution:
> I have created a new type of agp memory in use in the i810's agpgart.
> This type is "Shared" memory and works quite differently from regular
> agpgart memory.

This seems reasonable enough, but I'll have to think about it more and learn
a bit more about the AGP implementation to fully grok it.  On question I do
have is what impact will this have (if any) on chipsets that aren't UMA?

-- 
Tell that to the Marines!

_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to