On Sat, May 18, 2002 at 11:32:16PM +0200, Michel Dänzer wrote:
> > > use dma to transfer frames to video ram, or memcpy?
> > Do you know what drivers use DMA for this?
> Only r128 yet,
The closed source nvidia drivers do it as well.
> but it's quite fragile there,
It is by no way fragile. Since m
Michael wrote:
>
> On Sat, May 18, 2002 at 02:57:24AM +0200, Vedran Rodic wrote:
> > I think I found a cause for a problem described at
> > http://marc.theaimsgroup.com/?l=dri-devel&m=101843821602258&w=2
> >
> > If I run a X11 application that updates the screen periodicaly
> > (clock from KDE ki
Hi all
So, I took the first snapshot with textures - and ready to say something
good. Well, DRI now works even in 1280x1024 - great thanks to Leif and
others. At least I don't have to modify XF86Config every time...
1. glxinfo - OK, usual report.
2 glxgears does not show me any real difference
On Sat, 2002-05-18 at 14:43, Vedran Rodic wrote:
> On Fri, May 17, 2002 at 09:23:18PM +0200, Arpi wrote:
> > use dma to transfer frames to video ram, or memcpy?
>
> Do you know what drivers use DMA for this?
Only r128 yet, but it's quite fragile there, and when I played with
adding it to the rad
On Sat, 18 May 2002 18:26:52 +0100
José Fonseca <[EMAIL PROTECTED]> wrote:
> I also have to start using another X server in a sep window cause having
> to log out everytime I want to test is a PITA.
I'm not sure whether I get this correctly. Anyway, I have my 2D Xserver
running on vt7 and start
On 2002.05.18 18:02 Felix Kühling wrote:
> On Sat, 18 May 2002 15:56:00 +0100
> José Fonseca <[EMAIL PROTECTED]> wrote:
>
> > Nice report ;-)
>
> Thanks :)
>
> > Try with xfree-gdb (http://www.dawa.demon.co.uk/xfree-gdb/) to see if
> you
> > have better luck.
>
> Yep, that gave better results.
On Sat, 18 May 2002 15:56:00 +0100
José Fonseca <[EMAIL PROTECTED]> wrote:
> Nice report ;-)
Thanks :)
> Try with xfree-gdb (http://www.dawa.demon.co.uk/xfree-gdb/) to see if you
> have better luck.
Yep, that gave better results. Since I have only one computer here and
the display turns black
On Sat, May 18, 2002 at 02:57:24AM +0200, Vedran Rodic wrote:
> I think I found a cause for a problem described at
> http://marc.theaimsgroup.com/?l=dri-devel&m=101843821602258&w=2
>
> If I run a X11 application that updates the screen periodicaly
> (clock from KDE kicker, gkrellm), I'll see this
On Sat, 18 May 2002 11:30:28 -0400 (EDT)
Leif Delgass <[EMAIL PROTECTED]> wrote:
> Did you have a 2D accelerated server running on another vt? The DDX saves
> and restores its register state on mode switches, so it could be a problem
> with the FIFO depth or pattern registers being changed. Try
Leif,
On 2002.05.18 16:59 Leif Delgass wrote:
> ...
>
> I was just thinking that we could replace buffer aging with a check of
> BM_GUI_TABLE in freelist_get when searching the pending list, similar to
> what I'm doing with the dispatch. Since we know the physical address of
> each buffer, we c
On Sat, 18 May 2002, José Fonseca wrote:
> On 2002.05.18 10:33 Leif Delgass wrote:
> > OK, I finally committed my changes thus far as a checkpoint. I'm reading
> > BM_GUI_TABLE in the dispatch routine to see when we hit the hardware
> > pointer and wait once we reach it. So the dispatch is trea
Did you have a 2D accelerated server running on another vt? The DDX saves
and restores its register state on mode switches, so it could be a problem
with the FIFO depth or pattern registers being changed. Try testing
without another X server running if you haven't already. Also, does
anything s
On 2002.05.18 15:40 Felix Kühling wrote:
> On Sat, 18 May 2002 15:01:51 +0200
> Felix Kühling <[EMAIL PROTECTED]> wrote:
>
> > For this test I compiled everything with gcc-2.95.4. I had a different
> > problem after compiling with gcc-3.0. I have to try that again and
> check
> > for compile erro
On Sat, 18 May 2002 15:01:51 +0200
Felix Kühling <[EMAIL PROTECTED]> wrote:
> For this test I compiled everything with gcc-2.95.4. I had a different
> problem after compiling with gcc-3.0. I have to try that again and check
> for compile errors. The problem was that the X server segfaulted on
> s
On Sat, 18 May 2002 14:01:35 +0100
José Fonseca <[EMAIL PROTECTED]> wrote:
> Ian, this is what ATI tells to people when they request the specs and
> don't mention that its for the DRI project.
I did reply and mention that... we shall see... :-)
_
On 2002.05.18 13:38 Keith Whitwell wrote:
> Ian Molton wrote:
> >
> > Hi
> >
> > I'd like copies of the Radeon specs, please?
> >
> > ATI say they have given them to the DRI project, and I was told to get
> > my copy here.
>
> Some of us have specs, but I don't think we've ever received a license
Hi,
I updated my DRI tree and recompiled everything. With glxgears, and
quake1 things work fine and the framerate has increased again. glxgears
went from 190 to 240 :). With quake2 and quake3 the Xserver locks up
before anything is drawn. I can kill the X-server with the secure access
sysrq key s
On 2002.05.18 13:31 Ian Molton wrote:
> On Sat, 18 May 2002 12:40:51 +0100
> José Fonseca <[EMAIL PROTECTED]> wrote:
>
> > > > First thing you need is to download the cvs tree and build it. You
> > > > can
> > >
> > > I downloaded it and am trying to build it following the instructions
> > > you
On Fri, May 17, 2002 at 09:23:18PM +0200, Arpi wrote:
> use dma to transfer frames to video ram, or memcpy?
Do you know what drivers use DMA for this?
Vedran Rodic
___
Hundreds of nodes, one monster rendering program.
Now that's a supe
Ian Molton wrote:
>
> Hi
>
> I'd like copies of the Radeon specs, please?
>
> ATI say they have given them to the DRI project, and I was told to get
> my copy here.
Some of us have specs, but I don't think we've ever received a license to
distribute them... Given how protective they are about
Hi
I'd like copies of the Radeon specs, please?
ATI say they have given them to the DRI project, and I was told to get
my copy here.
:-)
___
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clus
On 2002.05.18 12:11 Ian Molton wrote:
> On Sat, 18 May 2002 11:08:22 +0100
> José Fonseca <[EMAIL PROTECTED]> wrote:
>
> > On 2002.05.18 10:41 Ian Molton wrote:
> > > Hi.
> > >
> > > What do I need to do to get started on DRI hacking?
> > >
> > > I want to track down a bug in radeon_dri.so
> > >
On Sat, 18 May 2002 11:32:59 +0100
José Fonseca <[EMAIL PROTECTED]> wrote:
>
> Ok,
>
> This is a draft for mach64. Please fell free to correct. What I'm not
> sure is marked with "?".
Cool. thanks.
___
Hundreds of nodes, one monster
On Sat, 18 May 2002 11:08:22 +0100
José Fonseca <[EMAIL PROTECTED]> wrote:
> On 2002.05.18 10:41 Ian Molton wrote:
> > Hi.
> >
> > What do I need to do to get started on DRI hacking?
> >
> > I want to track down a bug in radeon_dri.so
> >
> > how do I build it? what sources do I need?
>
> Ian
On 2002.05.18 10:33 Leif Delgass wrote:
> OK, I finally committed my changes thus far as a checkpoint. I'm reading
> BM_GUI_TABLE in the dispatch routine to see when we hit the hardware
> pointer and wait once we reach it. So the dispatch is treating the
> descriptor table as a ring, and it help
Ok,
This is a draft for mach64. Please fell free to correct. What I'm not sure
is marked with "?".
On 2002.05.18 10:44 Ian Molton wrote:
> Well, here is the updated list... anyone feel free to fill in features
> for the hardware they know...
>
> cmon, this is at worst 5 mins work for someone w
On 2002.05.18 10:41 Ian Molton wrote:
> Hi.
>
> What do I need to do to get started on DRI hacking?
>
> I want to track down a bug in radeon_dri.so
>
> how do I build it? what sources do I need?
Ian,
First thing you need is to download the cvs tree and build it. You can
follow the instructio
Well, here is the updated list... anyone feel free to fill in features
for the hardware they know...
cmon, this is at worst 5 mins work for someone who knows a given card...
3D features
---
Anti Aliasing
Fullscreen
Line / edge
Glyph (text)
Max Accelerated colourdepth / res
Filte
OK, I finally committed my changes thus far as a checkpoint. I'm reading
BM_GUI_TABLE in the dispatch routine to see when we hit the hardware
pointer and wait once we reach it. So the dispatch is treating the
descriptor table as a ring, and it helps. There's still lots of places to
optimize and
Hi.
What do I need to do to get started on DRI hacking?
I want to track down a bug in radeon_dri.so
how do I build it? what sources do I need?
___
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http:
30 matches
Mail list logo
