On Fri, 2005-01-07 at 04:10 +0100, Roland Scheidegger wrote:
>
> The dri and drm seem fairly straightforward, though I'm not sure the way
> I handled communication between especially drm and ddx is how it's meant
> to be. dri got a bit unlucky, as ddx can't know at startup if it will be
> able to
On Wed, 2005-01-05 at 09:27 -0500, Alex Deucher wrote:
> Ok, so last night I think I figured out why pageflipping was borked
> with mergedfb. Unfortunately the fix requires changes to the drm and
> sarea. I'm wondering what the best way to do this is and maintain
> compatability. When crtc1 is a
On Mon, 10 Jan 2005, Keith Conger wrote:
Hi,
Here ya go:
0xff03
Also as of this morning the cvs HEAD's driver no longer displays the
gears for me.
This is probably because I left the pipeline using agp buffer upload
of vertices instead of immediate one.
Try editint r300_render.c, r300_run_rend
On Mon, 10 Jan 2005, Nicolai Haehnle wrote:
On Monday 10 January 2005 04:42, Vladimir Dergachev wrote:
Update of /cvsroot/r300/r300_driver/r300
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv1824
Modified Files:
r300_render.c
Log Message:
For some reason we need r300Flush when using textur
With applying byte swapping to get_short & get_int in
r300_demo i successfully run all the demo except the
--vb-triangles, --eb-triangles & --idx-triangles where i see
nothing guess this is related to cp engine that need some
byte swapping no ? Or does that Keith successfully running
glxgears (even
On Monday 10 January 2005 04:42, Vladimir Dergachev wrote:
> Update of /cvsroot/r300/r300_driver/r300
> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv1824
>
> Modified Files:
> r300_render.c
> Log Message:
> For some reason we need r300Flush when using textures. Perhaps the problem
is
Hi,
Here ya go:
0xff03
Also as of this morning the cvs HEAD's driver no longer displays the
gears for me.
Keith
On Mon, 2005-01-10 at 09:44 -0500, Vladimir Dergachev wrote:
>
> On Mon, 10 Jan 2005, Keith Conger wrote:
>
> > Hi,
> >
> > Sorry this took so long. r300_driver prints -16580608 a
Vladimir Dergachev wrote:
On Mon, 10 Jan 2005, Keith Conger wrote:
Hi,
Sorry this took so long. r300_driver prints -16580608 as fbLocation. As
for X I can't seem to get it to print it, I'll keep working on this
though.
Could you change the format to 0x%08x (instead of %d) ? This way it
will be p
On Mon, 10 Jan 2005, Keith Conger wrote:
Hi,
Sorry this took so long. r300_driver prints -16580608 as fbLocation. As
for X I can't seem to get it to print it, I'll keep working on this
though.
Could you change the format to 0x%08x (instead of %d) ? This way it will
be printed as hex, easier to re
Hi,
Sorry this took so long. r300_driver prints -16580608 as fbLocation. As
for X I can't seem to get it to print it, I'll keep working on this
though.
Thanks,
Keith
On Thu, 2005-01-06 at 13:58 -0500, Vladimir Dergachev wrote:
> >
> >>
> >> This is especially puzzling since your computer do
Jerome Glisse wrote:
I think it's related to r300 driver because i get something
with the r300 demo. I get the depth buffer with r300 demo
but not the color one. I think this is due to radeon base address
or to the R300_RB3D_COLOROFFSET0 setup, moreover there
is a need for some endian swapping with
Hi,
Finally i find my bug in AGP but r300 still not work.
You will see below revelant part of my xorg log.
I think it's related to r300 driver because i get something
with the r300 demo. I get the depth buffer with r300 demo
but not the color one. I think this is due to radeon base address
or to th
12 matches
Mail list logo
