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 clears
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
> > primitive
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 to
Am Sa, den 18.12.2004 schrieb Tomas Carnecky um 14:54:
> 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
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 via
