NoiseEHC at freemail.hu
Thu Sep 27 08:58:18 EDT 2007
It is answered in the thread "The "iGoogle bug" ".
In short, when the X people finish that DRM thing the XO will probably
be updated to eliminate that copy but currently there are much more
important things to do right now.
Albert Cahalan wrote:
> On 9/26/07, Daniel Monteiro Basso <daniel at basso.inf.br> wrote:
>> Em Qua, 2007-09-26 a`s 19:29 -0400, Albert Cahalan escreveu:
>>> The simple Xlib calls would be:
>>> 1. app writes to inactive private buffer
>>> 2. app asks X to copy that buffer to video memory
>>> That's a whole worthless copy.
>> Actually that would be:
>> 1. app write to a memory buffer
>> 2. app asks X to do a hardware blit to the video memory using the XVideo
> That's a bit better.
> Of course, in this case "video memory" is system memory.
> The copy is costing memory cycles that would be better
> used by the CPU.
> Does it in fact work that way on the XO? I thought that the XO
> was using a software copy because the kernel driver wasn't
> providing the sort of virtual GART (the horribly-named "DRM")
> required to make DMA workable.
> Devel mailing list
> Devel at lists.laptop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel