On Llu, 2005-09-26 at 01:54 +0100, Dave Airlie wrote:
Do we need to restrict the size of the maps we allow the DRI clients to
acess in the FB area?
Yes - SiS has a 64K command queue in the frame buffer for example
---
SF.Net email is
On 9/26/05, Alan Cox [EMAIL PROTECTED] wrote:
On Llu, 2005-09-26 at 01:54 +0100, Dave Airlie wrote:
Do we need to restrict the size of the maps we allow the DRI clients to
acess in the FB area?
Yes - SiS has a 64K command queue in the frame buffer for example
Savage has a command
I was talking to Ben on IRC about this and I realised I wasn't really sure
about this..
At the moment we allow the DRI client full r/w access to the framebuffer
if I'm not mistaken (for software fallbacks and the like)..
If I put the PCIE GART table into fb memory (which I've no choice in), the
On Mon, 2005-09-26 at 01:54 +0100, Dave Airlie wrote:
I was talking to Ben on IRC about this and I realised I wasn't really sure
about this..
At the moment we allow the DRI client full r/w access to the framebuffer
if I'm not mistaken (for software fallbacks and the like)..
If I put the
memory for the
framebuffer via DRI, I think there is an ioctl for that, but
I'm not sure.
No there isn't, because DRM doesn't have any memory manager ATM.
And is it possible to allocate offscreen memory with DRI?
So I could render into it, read the pixels out of it and
put them
Felix Kühling wrote:
Am Sa, den 18.12.2004 schrieb Tomas Carnecky um 14:54:
Most (all?) supported hardware doesn't support multiple clipping
rectangles in hardware, so the driver iterates over them and draws all
primitives once in each clipping rectangle.
Quite CPU expensive, isn't it?
It seems
Am So, den 19.12.2004 schrieb Tomas Carnecky um 15:32:
Felix Kühling wrote:
Am Sa, den 18.12.2004 schrieb Tomas Carnecky um 14:54:
Most (all?) supported hardware doesn't support multiple clipping
rectangles in hardware, so the driver iterates over them and draws all
primitives once in
Felix Kühling wrote:
Am So, den 19.12.2004 schrieb Tomas Carnecky um 15:32:
Who exactly does map the memory? The Xserver or the DRM library? If it's
the Xserver, how can it know where all the different buffers are?
I'm not sure I understand the question. I'll rephrase the above and hope
it
Tomas Carnecky wrote:
Hi,
Can I control a graphics card _completely_ with DRI? I mean
allocate the framebuffer, switch between modes etc. Or do I
need some kind of helper code that does these things (like
fbdev or the Xserver)?
I'm particulary interested in allocating memory for the
framebuffer
Hi,
Can I control a graphics card _completely_ with DRI? I mean
allocate the framebuffer, switch between modes etc. Or do I
need some kind of helper code that does these things (like
fbdev or the Xserver)?
I'm particulary interested in allocating memory for the
framebuffer via DRI, I think
Hello!
Will using the matrox framebuffer cause me problems trying to use DRI?
I have:
X410
Matrox G450
Have tried everything and still can't get any OpenGL-apps to run. (The apps are
linked to the correct libGL, libGLU; DRI is enabled according to the X-log and
Glxinfo). Gears hangs the
11 matches
Mail list logo