Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=716
[EMAIL PROTECTED] changed:
What|Removed |Added
--
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=967
[EMAIL PROTECTED] changed:
What|Removed |Added
--
Roland Scheidegger wrote:
Ian Romanick wrote:
This is wrong, and may break valid applications. The supported
compressed formats should be listed no matter what.
Ok, I'll drop that. It was really just a crazy idea, though I've figured
out it won't do any good anyways (apps like QuakeIII will alw
Ian Romanick wrote:
Since I'm not a lawyer, I'm not going to comment on any of the IP
legality of this patch. I am in no way offering any form of legal
advice. I do have a comment about the correctness of it that may also
apply to similar future (i.e., FXT1) patches.
Roland Scheidegger wrote:
Since I'm not a lawyer, I'm not going to comment on any of the IP
legality of this patch. I am in no way offering any form of legal
advice. I do have a comment about the correctness of it that may also
apply to similar future (i.e., FXT1) patches.
Roland Scheidegger wrote:
Index: texcompress
On Thu, 18 Dec 2003 14:30:21 -0300
Rafael Maximo <[EMAIL PROTECTED]> wrote:
> At 12:38 PM 18/12/2003, Felix Kühling wrote:
>
> >The device node is created by XFree86 when it looks for the DRM. Make
> >sure that the directory /dev/dri exists and that the Xserver has
> >permission to create new dev
At 12:38 PM 18/12/2003, Felix Kühling wrote:
The device node is created by XFree86 when it looks for the DRM. Make
sure that the directory /dev/dri exists and that the Xserver has
permission to create new device nodes in it. The Xserver runs as root,
so that should not be a problem, but I vaguely
Hi There,
Is it possible to disable the side address mechanism
of Radeon 7000 by using command register(offset
CAP_PTR +8) bit SBA_ENABLE? and how?
SBA_ENABLE is read/writable. I'm not even able to turn
it off without X is running.
Thanks in advance,
--Craig
_
On Thu, 18 Dec 2003 10:40:55 -0300
Rafael Maximo <[EMAIL PROTECTED]> wrote:
> Felix,
>
> I tested your driver on my savage4 and i couldn't make the 3D
> driver work (i changed the code to enable direct render on savage4), the
> Xfree86 just can't find /dev/dri/cardX and i loaded agpgar
Wow. Thanks for all those quick and helpful reponses :-)
Adam
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from
On Thu, 2003-12-18 at 15:12, Adam K Kirchhoff wrote:
>
> (WW) RADEON(0): [agp] AGP not available
> (II) RADEON(0): [drm] removed 1 reserved context for kernel
> (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe0882000 at 0x48267000
> (WW) RADEON(0): DRI forced on with virtual screen of great
Adam K Kirchhoff wrote:
So I decided to give 2.6.0 a shot this morning :-)
My Radeon 8500 (which previous worked with 2.4.22) refuses to enable
direct rendering:
(WW) RADEON(0): [agp] AGP not available
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192
in 2.6 there are two agp related kernel modules that need to be loaded.
agpgart and your agp chipset specific module (via, sis, ati, etc.).
Alex
--- Adam K Kirchhoff <[EMAIL PROTECTED]> wrote:
>
> So I decided to give 2.6.0 a shot this morning :-)
>
> My Radeon 8500 (which previous worked with
On Thu, 2003-12-18 at 15:12, Adam K Kirchhoff wrote:
> So I decided to give 2.6.0 a shot this morning :-)
>
> My Radeon 8500 (which previous worked with 2.4.22) refuses to enable
> direct rendering:
>
> (WW) RADEON(0): [agp] AGP not available
> (II) RADEON(0): [drm] removed 1 reserved context for
So I decided to give 2.6.0 a shot this morning :-)
My Radeon 8500 (which previous worked with 2.4.22) refuses to enable
direct rendering:
(WW) RADEON(0): [agp] AGP not available
(II) RADEON(0): [drm] removed 1 reserved context for kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe088
Felix,
I tested your driver on my savage4 and i couldn't make the 3D
driver work (i changed the code to enable direct render on savage4), the
Xfree86 just can't find /dev/dri/cardX and i loaded agpgart and savage
modules without warnings but it just doesn't create the device, i checked
Jacek Popławski wrote:
On Thu, Dec 18, 2003 at 02:43:09AM +0100, Roland Scheidegger wrote:
and I don't know if any open-source
compressors exist which could easily be included in mesa
On Thu, 18 Dec 2003 09:02:44 +0100
"Mario Premke" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> the new SavageDDR DRI driver compiles and seems to run. glxinfo doesn't show
> 'Indirect Rendering' any more, but starting q3demo or a
> 3D screensaver the X-Server crashes and restarts, is that what is mea
Hello,
the new SavageDDR DRI driver compiles and seems to run. glxinfo doesn't show 'Indirect
Rendering' any more, but starting q3demo or a
3D screensaver the X-Server crashes and restarts, is that what is meant by: ' ... -
almost certain lockups on vt switches and when
moving 3D windows ...' ?
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-12-18 02:26 ---
>I had the same
20 matches
Mail list logo
