<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-2" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
It is answered in the thread "The "iGoogle bug" ".<br>
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.<br>
<br>
<br>
Albert Cahalan wrote:
<blockquote
cite="mid:787b0d920709270527t180e2483q57b311492d179c5e@mail.gmail.com"
type="cite">
<pre wrap="">On 9/26/07, Daniel Monteiro Basso <a class="moz-txt-link-rfc2396E" href="mailto:daniel@basso.inf.br"><daniel@basso.inf.br></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Em Qua, 2007-09-26 às 19:29 -0400, Albert Cahalan escreveu:
</pre>
<blockquote type="cite">
<pre wrap="">The simple Xlib calls would be:
loop{
1. app writes to inactive private buffer
2. app asks X to copy that buffer to video memory
}
That's a whole worthless copy.
</pre>
</blockquote>
<pre wrap="">Actually that would be:
loop{
1. app write to a memory buffer
2. app asks X to do a hardware blit to the video memory using the XVideo
extension
}
</pre>
</blockquote>
<pre wrap=""><!---->
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
<a class="moz-txt-link-abbreviated" href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a>
<a class="moz-txt-link-freetext" href="http://lists.laptop.org/listinfo/devel">http://lists.laptop.org/listinfo/devel</a>
</pre>
</blockquote>
</body>
</html>