is all about on the pixmaps
score?
-Yves
On Thu, Jun 10, 2010 at 09:16:44PM +0200, Maarten Maathuis wrote:
On Thu, Jun 10, 2010 at 8:56 PM, Corbin Simpson
mostawesomed...@gmail.com wrote:
2010/6/10 Yves De Muyter y...@alfavisio.be:
Is there any documentation available about the differences
sys_ptr because that will probably be slow for Xv...
-Yves
On Fri, 2010-07-23 at 10:33 +0200, Michel Dänzer wrote:
On Don, 2010-07-22 at 20:18 +0200, Yves De Muyter wrote:
I have now ported the driver to exa_mixed (also because the
exa_classic bugfix is not being backported to 1.7
=0xb6c1c000 and memoryBase=0xb4a74000.
Any Idea how I can access the framebuffer address of the pixmap from
within the driver?
-Yves
On Fri, 2010-07-23 at 12:57 +0200, Michel Dänzer wrote:
On Fre, 2010-07-23 at 12:07 +0200, Yves De Muyter wrote:
Second argument of fbScreenInit() is definitely
is all about on the pixmaps
score?
-Yves
On Thu, Jun 10, 2010 at 09:16:44PM +0200, Maarten Maathuis wrote:
On Thu, Jun 10, 2010 at 8:56 PM, Corbin Simpson
mostawesomed...@gmail.com wrote:
2010/6/10 Yves De Muyter y...@alfavisio.be:
Is there any documentation available about the differences
-06-09 at 22:18 +0200, Yves De Muyter wrote:
I'm trying to port an older driver to XFree 1.7 and I'm facing an
issue with EXA (classic). It seems that Xv's PutImage is calling our
PutImage handler with a Drawable that is PINNED ?
That means we cannot ever draw to it since
the window region the wrong way? I
can imagine alot of drivers don't touch the pixmap and simply overlay
their video...
-Yves
On Thu, Jun 10, 2010 at 12:38:27PM +0200, Michel Dänzer wrote:
On Don, 2010-06-10 at 12:34 +0200, Yves De Muyter wrote:
OK so i'm porting the 'poulsbo' driver to Xorg 1.7. What
