Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2490
[EMAIL PROTECTED] changed:
What|Removed |Added
-
Vladimir Dergachev wrote:
Hi Jacob,
Could you repost your patch with diff -u option ? it is a bit
easier to read.
Thank you !
Yes, here it goes. See attachment. It may need more #ifdefs, I have not
tried running it on straight x86.
Jacob
diff -Naur old/agpgart_be.
By the way, though I did not manage to get r300 running with Xen yet,
the DRM module needed these changes, or the machine would crash:
cvs diff: Diffing .
Index: drm_memory.c
===
RCS file: /cvsroot/r300/r300_driver/drm/linux-core/drm
idr mentioned this is possible on the r100, all the info is actually in
the docs from what I can see, so only the Mesa side would need to be
done...
Anyone with R100 DDK, 7.7.10 and code in lib\3D\embm.c and chap7\bumpmap\
Probably wouldn't be that hard to implement
Dave.
--
David Airlie,
On Mon, 7 Feb 2005, Roland Scheidegger wrote:
> Geller Sandor wrote:
> >>I just removed the AGPFastWrite and DynamicClocks options. The crashes
> >>still happen though.
> >
> >
> > Looks like not only I have problems with the radeon driver. I update the
> > X.org, drm, Mesa CVS once a week, but ha
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2164
--- Additional Comments From [EMAIL PROTECTED] 2005-02-08 03:25 ---
Crea
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2164
--- Additional Comments From [EMAIL PROTECTED] 2005-02-08 03:27 ---
I've
Hello,
On Sat Nov 27 22:47:59 2004 UTC, there was a big commit into Mesa CVS by
brianp, with the following comment:
> Remove _mesa_ResizeBuffersMESA() call from _mesa_set_viewport().
> Now, the driver's Viewport routine should call _mesa_ResizeBuffersMESA()
> if necessary.
The r200 driver fails
On Tue, 8 Feb 2005 10:36:50 + (GMT), Dave Airlie <[EMAIL PROTECTED]> wrote:
>
> idr mentioned this is possible on the r100, all the info is actually in
> the docs from what I can see, so only the Mesa side would need to be
> done...
>
> Anyone with R100 DDK, 7.7.10 and code in lib\3D\embm.c a
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2490
--- Additional Comments From [EMAIL PROTECTED] 2005-02-08 06:43 ---
I do
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2164
[EMAIL PROTECTED] changed:
What|Removed |Added
-
Hi,
as first, it's the first time I play with dri, maybe I'm just omitting a
step, but in doubt I report.
I'm trying to use the r300 driver from http://r300.sourceforge.net/ on
aluBook 15" (cpu 7447/7457, radeon mobility 9600). This is what I obtain
following the instruction in r300-driver/README:
On Tue, 8 Feb 2005 17:38:11 +0100 (CET), Dario Laera <[EMAIL PROTECTED]> wrote:
> Hi,
> as first, it's the first time I play with dri, maybe I'm just omitting a
> step, but in doubt I report.
> I'm trying to use the r300 driver from http://r300.sourceforge.net/ on
> aluBook 15" (cpu 7447/7457, rade
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2195
--- Additional Comments From [EMAIL PROTECTED] 2005-02-08 08:51 ---
The
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2497
Summary: glut menues are broken in sw-tnl mode
Product: Mesa
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2498
Summary: x11-drm-20050104 borks on xorg startup
Product: DRI
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2498
--- Additional Comments From [EMAIL PROTECTED] 2005-02-08 10:07 ---
Crea
On Tue, 2005-02-08 at 16:57 +0500, Alexander E. Patrakov wrote:
>
> On Sat Nov 27 22:47:59 2004 UTC, there was a big commit into Mesa CVS by
> brianp, with the following comment:
>
> > Remove _mesa_ResizeBuffersMESA() call from _mesa_set_viewport().
> > Now, the driver's Viewport routine should c
On Tue, 08 Feb 2005 14:32:32 -0500, Michel Dänzer <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-02-08 at 16:57 +0500, Alexander E. Patrakov wrote:
> >
> > On Sat Nov 27 22:47:59 2004 UTC, there was a big commit into Mesa CVS by
> > brianp, with the following comment:
> >
> > > Remove _mesa_ResizeBuffer
ot;
#define DRIVER_DESC "ATI Radeon"
-#define DRIVER_DATE"20050207"
+#define DRIVER_DATE"20050208"
/* Interface history:
*
@@ -82,10 +82,12 @@
* - Add hyperz support, add hyperz flags to clear ioctl.
* 1.14- Add support
On Tue, 8 Feb 2005 14:39:38 -0500, Alex Deucher <[EMAIL PROTECTED]> wrote:
> On Tue, 08 Feb 2005 14:32:32 -0500, Michel Dänzer <[EMAIL PROTECTED]> wrote:
> > On Tue, 2005-02-08 at 16:57 +0500, Alexander E. Patrakov wrote:
> > >
> > > On Sat Nov 27 22:47:59 2004 UTC, there was a big commit into Mesa
On Tue, 08 Feb 2005 20:38:51 +0100, Roland Scheidegger
<[EMAIL PROTECTED]> wrote:
> Ok, I was FINALLY able to come up with something for texture tiling
> which seems to work - this was very very annoying, it _almost_ worked
> literally within minutes, but I needed a lot of time until it finally
> d
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2164
--- Additional Comments From [EMAIL PROTECTED] 2005-02-08 11:58 ---
It w
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2195
--- Additional Comments From [EMAIL PROTECTED] 2005-02-08 12:09 ---
(In
Am Dienstag, 18. Januar 2005 11:33 schrieb Keith Whitwell:
> Jacek Rosik wrote:
> > Hi,
> >
> > In radeonUpdateWindow and radeonUpdateViewportOffset functions in
> > radeon_state.c `tx' and `ty' values are calculated differently. In
> > UpdateWindow SUBPIXEL_X|Y values are added and in UpdateViewpo
Am Dienstag, den 08.02.2005, 20:38 +0100 schrieb Roland Scheidegger:
> Ok, I was FINALLY able to come up with something for texture tiling
> which seems to work - this was very very annoying, it _almost_ worked
> literally within minutes, but I needed a lot of time until it finally
> did really
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2502
Summary: system hangs after resume from suspend to disk with dri
7:48:59 - 1.35
+++ radeon.h8 Feb 2005 23:29:09 -
@@ -42,10 +42,10 @@
#define DRIVER_NAME"radeon"
#define DRIVER_DESC"ATI Radeon"
-#define DRIVER_DATE"20050125"
+#define DRIVER_DATE"20050208"
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2504
Summary: Xorg CVS + DRm CVS = Radeon driver Display borked,
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2504
--- Additional Comments From [EMAIL PROTECTED] 2005-02-08 17:42 ---
this
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2506
Summary: Radeon: Hardware Cursor messes up TV out.
Product: DRI
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2504
[EMAIL PROTECTED] changed:
What|Removed |Added
-
On Mon, 2005-02-07 at 13:40 +0100, Geller Sandor wrote:
>
> Is there any way I can help to track down the problem(s)? My machine
> doesn't have network connection, so I can use only scripts which run in
> the background. With expect and gdb maybe it is possible to get at least a
> backtrace from m
On Tue, 2005-02-08 at 14:59 +1100, Ben Skeggs wrote:
>
> Could someone with knowledge of r200_dri explain how vertex buffer
> uploads are put into framebuffer memory on r200?
AFAIK they aren't, the only data the radeon and r200 drivers upload to
the framebuffer is textures.
--
Earthling Miche
Michel DÃnzer wrote:
On Tue, 2005-02-08 at 14:59 +1100, Ben Skeggs wrote:
Could someone with knowledge of r200_dri explain how vertex buffer
uploads are put into framebuffer memory on r200?
AFAIK they aren't, the only data the radeon and r200 drivers upload to
the framebuffer is textures.
On Tue, 2005-02-08 at 00:12 +0500, Dimitry Naldayev wrote:
> Michel DÃnzer <[EMAIL PROTECTED]> writes:
>
> > On Sun, 2005-02-06 at 19:32 +0500, Dimitry Naldayev wrote:
> >> Michel DÃÂnzer <[EMAIL PROTECTED]> writes:
>
> I am about the X server and drm module --- what happens when we do vt
> switc
On Tue, 2005-02-08 at 02:30 +, Dave Airlie wrote:
> >
> > I fully support the idea of enabling gart texturing on the r200 driver. If
> > the old client texturing code can be kept around as an X config option, so
> > much the better, but it shouldn't stand in the way of gart texturing given
>
>
> But what if you mix clients with different configuration? That's why it
> has to be an X server option I think.
Yes figured this out chatting on IRC today... need to look at it again...
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb /
On Tue, 8 Feb 2005, Michel [ISO-8859-1] Dänzer wrote:
On Tue, 2005-02-08 at 14:59 +1100, Ben Skeggs wrote:
Could someone with knowledge of r200_dri explain how vertex buffer
uploads are put into framebuffer memory on r200?
AFAIK they aren't, the only data the radeon and r200 drivers upload to
the
39 matches
Mail list logo