Michel DÃnzer wrote:
fixed a copy & paste error in the non-core drm version, and it actually
auto-refreshes the screen when switching between a tiled and untiled resolution...
Nice.
What happened to Stephane's surface allocator, BTW? If you just whack
the surface registers directly from the X ser
>
> On Wed, 2005-01-19 at 23:49 +0100, Amir Bukhari wrote:
> >
> > > On Wednesday 19 January 2005 17:29, Amir Bukhari wrote:
> > > > Hallo,
> > > > Our users of Looking Glass 3D Desktop have a problem getting DRI to
> work
> > > > with LG3D. DRI is disabled when Composite Extension enabled. Is
> T
On Wed, 2005-01-19 at 23:49 +0100, Amir Bukhari wrote:
>
> > On Wednesday 19 January 2005 17:29, Amir Bukhari wrote:
> > > Hallo,
> > > Our users of Looking Glass 3D Desktop have a problem getting DRI to work
> > > with LG3D. DRI is disabled when Composite Extension enabled. Is There
> > any
> > >
> -Original Message-
> From: Adam Jackson [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 19, 2005 11:30 PM
> To: dri-devel@lists.sourceforge.net
> Cc: Amir Bukhari
> Subject: Re: DRI and Composite
>
> On Wednesday 19 January 2005 17:29, Amir Bukhari wrote:
> > Hallo,
> > Our users
> Almost certainly. Last time I glossed over it, there definitely seemed to be
> some registers missing which would need to be emitted. Though it might be
> easier to just put everything in one single big block and emit that instead,
> since it looks like everything fragment shader related has con
On Wednesday 19 January 2005 17:29, Amir Bukhari wrote:
> Hallo,
> Our users of Looking Glass 3D Desktop have a problem getting DRI to work
> with LG3D. DRI is disabled when Composite Extension enabled. Is There any
> way to enable DRI when composite enabled?
> Nvidia driver has an Option in xorg.c
Hallo,
Our users of Looking Glass 3D Desktop have a problem getting DRI to work
with LG3D. DRI is disabled when Composite Extension enabled. Is There any
way to enable DRI when composite enabled?
Nvidia driver has an Option in xorg.conf which let also GLX initialized when
Composite is enabled!
A
Am Mittwoch, den 19.01.2005, 11:28 -0500 schrieb Adam Jackson:
> On Wednesday 19 January 2005 03:56, Keith Whitwell wrote:
> > Dave Airlie wrote:
> > > Hi all,
> > > On error a lot of DRI drivers do an exit and just leave, this
> > > means you have to setup a break on exit to debug these cases whi
Dave Airlie wrote:
This is not a driver bug. Doom3 with r_renderer arb simply does look
that awful. At least I've tried it with some other OS, and it looked
exactly the same. AFAIK noone has the required documentation to
implement the ati fragment shader extensions, which are required to
enable oth
On Wednesday 19 January 2005 10:27, Vladimir Dergachev wrote:
> On Wed, 19 Jan 2005, Dave Airlie wrote:
> > Hi all,
> > On error a lot of DRI drivers do an exit and just leave, this
> > means you have to setup a break on exit to debug these cases which can be
> > a bit of a pain if you forget.. I
Michel DÃnzer wrote:
and furthermore there needs to be some code to deal with disabled
irqs. Is this such a big issue? I'm happy to leave it broken.
I don't know, you brought it up, I just brainstormed how it could be
done. :)
Ok. I leave it broken then at least for now.
Also, if doing that in t
On Wednesday 19 January 2005 03:56, Keith Whitwell wrote:
> Dave Airlie wrote:
> > Hi all,
> > On error a lot of DRI drivers do an exit and just leave, this
> > means you have to setup a break on exit to debug these cases which can be
> > a bit of a pain if you forget.. I wonder how to people feel
On Wed, 19 Jan 2005, Vladimir Dergachev wrote:
On Wed, 19 Jan 2005, Dave Airlie wrote:
Hi all,
On error a lot of DRI drivers do an exit and just leave, this
means you have to setup a break on exit to debug these cases which can be
a bit of a pain if you forget.. I wonder how to people fee
On Wed, 19 Jan 2005, Dave Airlie wrote:
Hi all,
On error a lot of DRI drivers do an exit and just leave, this
means you have to setup a break on exit to debug these cases which can be
a bit of a pain if you forget.. I wonder how to people feel about
changing these exits to aborts so the ap
On Wed, 2005-01-19 at 13:32 +0100, Roland Scheidegger wrote:
> Michel DÃnzer wrote:
> > On Tue, 2005-01-18 at 20:43 +0100, Roland Scheidegger wrote:
> >
> The DRM could update the register in the vblank interrupt
> handler?
> >
> >
> > [...]
> >
> >
> >> How would you do that in-kern
On Tue, Jan 18, 2005 at 01:23:24PM -0800, Ian Romanick wrote:
> Pasi Kärkkäinen wrote:
>
> >http://www.opengl.org/documentation/extensions/EXT_framebuffer_object.txt
> >
> >Has finally been posted.. hopefully it will be implemented in Mesa soon :)
>
> The superbuffers working group worked on that
Am Dienstag, den 18.01.2005, 20:04 -0800 schrieb Mark Cass:
> savage driver team,
>
> when i run glxgears a window appears but nothing is displayed. the
> shell from which glxgears was run displays the usual frames per second
> and no other information. i checked glxinfo and dri is enabled. also
Michel DÃnzer wrote:
On Tue, 2005-01-18 at 20:43 +0100, Roland Scheidegger wrote:
The DRM could update the register in the vblank interrupt
handler?
[...]
How would you do that in-kernel? There is vblank interrupt related
stuff (radeon_driver_vblank_wait for instance), but that only is
called whe
Dave Airlie wrote:
Hi all,
On error a lot of DRI drivers do an exit and just leave, this
means you have to setup a break on exit to debug these cases which can be
a bit of a pain if you forget.. I wonder how to people feel about
changing these exits to aborts so the app gets a signal and th
19 matches
Mail list logo
