-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
few days ago i was trying to play ut2003 on my Rage128 but, off course, with
no luck (s3c missing), is this feature one of the new things going to be
implemented in the near future?
Thnaks, and good work.
- --
!
Willy Gardiol - [EMAIL
I managed to get my pci radeon working with an evil hack, a proper fix
is needed but after using the pcigart patch, I did in
programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/radeon_drv.h
#define COMMIT_RING() do { \
+u32 test_read;
Do we know the causes of these error messages:
drmCommandWrite: -22
drmRadeonCmdBuffer: -22 (exiting)
I don't get them often when running apps under Linux, or native FreeBSD
apps under FreeBSD, but they're pretty common when running Linux apps
under FreeBSD. Given that I *have* seem them when
On Mon, 2003-02-03 at 11:50, Adam K Kirchhoff wrote:
Do we know the causes of these error messages:
drmCommandWrite: -22
drmRadeonCmdBuffer: -22 (exiting)
I don't get them often when running apps under Linux, or native FreeBSD
apps under FreeBSD, but they're pretty common when running
Willy Gardiol wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
few days ago i was trying to play ut2003 on my Rage128 but, off course, with
no luck (s3c missing), is this feature one of the new things going to be
implemented in the near future?
VIA/S3 has been contacted several
On Mon, 2003-02-03 at 12:45, Stefan Lange wrote:
VIA/S3 has been contacted several times already, whether they'll allow
the integration of S3TC-support in the DRI. Unfortunately they never
answered. So it's not very likely that you'll S3TC in DRI in the near
future. Things might change some
On Mon, 3 Feb 2003, Stefan Lange wrote:
VIA/S3 has been contacted several times already, whether they'll allow
the integration of S3TC-support in the DRI. Unfortunately they never
answered. So it's not very likely that you'll S3TC in DRI in the near
future. Things might change some time, if
please find attached a complete patch that allows pci Radeon cards to
work with DRI. It was created against the DRI CVS xc branch/trunk.
Thanks to MrCooper and M.Harris for their help.
Note: also contains the pcigart patch many often refer too.
Index:
-#define COMMIT_RING() do { \
- RADEON_WRITE( RADEON_CP_RB_WPTR, dev_priv-ring.tail ); \
+#define COMMIT_RING() do { \
+ /* read from PCI bus to ensure correct posting */ \
+ RADEON_READ( RADEON_CP_RB_WPTR ); \
+
On Mon, 2003-02-03 at 16:02, Keith Whitwell wrote:
-#define COMMIT_RING() do { \
- RADEON_WRITE( RADEON_CP_RB_WPTR, dev_priv-ring.tail ); \
+#define COMMIT_RING() do { \
+ /* read from PCI bus
On Mon, 2003-02-03 at 15:02, Keith Whitwell wrote:
-#define COMMIT_RING() do { \
- RADEON_WRITE( RADEON_CP_RB_WPTR, dev_priv-ring.tail ); \
+#define COMMIT_RING() do { \
+ /* read from PCI bus
On Mon, 2003-02-03 at 17:34, Alan Cox wrote:
On Mon, 2003-02-03 at 15:02, Keith Whitwell wrote:
-#define COMMIT_RING() do { \
- RADEON_WRITE( RADEON_CP_RB_WPTR, dev_priv-ring.tail ); \
+#define COMMIT_RING() do {
On Mon, 2003-02-03 at 15:53, Chris Ison wrote:
please find attached a complete patch that allows pci Radeon cards to
work with DRI. It was created against the DRI CVS xc branch/trunk.
Thanks, I'll commit this unless someone else comes up with a better
solution.
Note: also contains the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am quite happy to tell you that this is not true: i can play with discrete
satisfaction UT2003 under windows witha Rage128 AIW 16mb (ok, ok, 640x480
minimum detail, but it is enough for my playtime)
Maybe a bit jumpy on big maps...
:) i will
Michel Dänzer wrote:
On Mon, 2003-02-03 at 15:53, Chris Ison wrote:
please find attached a complete patch that allows pci Radeon cards to
work with DRI. It was created against the DRI CVS xc branch/trunk.
Thanks, I'll commit this unless someone else comes up with a better
solution.
Well,
On Mon, 2003-02-03 at 17:47, Keith Whitwell wrote:
Michel Dänzer wrote:
On Mon, 2003-02-03 at 15:53, Chris Ison wrote:
please find attached a complete patch that allows pci Radeon cards to
work with DRI. It was created against the DRI CVS xc branch/trunk.
Thanks, I'll commit this
Willy Gardiol wrote:
few days ago i was trying to play ut2003 on my Rage128 but, off course, with
no luck (s3c missing), is this feature one of the new things going to be
implemented in the near future?
As a few other people have mentioned, there is no S3TC support in the
DRI. Additionally,
On Mon, 3 Feb 2003, Keith Whitwell wrote:
please find attached a complete patch that allows pci Radeon cards to
work with DRI. It was created against the DRI CVS xc branch/trunk.
Thanks, I'll commit this unless someone else comes up with a better
solution.
Well, I'd like to at least
On Mon, 2003-02-03 at 17:05, Michel Dänzer wrote:
On Mon, 2003-02-03 at 17:34, Alan Cox wrote:
On Mon, 2003-02-03 at 15:02, Keith Whitwell wrote:
-#define COMMIT_RING() do { \
- RADEON_WRITE( RADEON_CP_RB_WPTR, dev_priv-ring.tail );
Remember, S3TC is no longer a needed by your driver to work with UT2003.
However, despite the attempts by Daniel Vogel to get ut2003 working with
the DRI drivers, the game now segfaults with my Radeon 8500.
Adam
On Mon, 3 Feb 2003, Ian Romanick wrote:
Willy Gardiol wrote:
few days ago i
I saw this posted on the dmx-devel (dmx.sf.net) ML today. Is anyone
familiar with the GLX proxy work? does it work with the DRI? Could
this be a solution for HW accelerated indirect rendering? what's teh
status of GLX Proxy and DMX? I'm very interested in it; also in
conjunction with DMX.
On Mon, 2003-02-03 at 18:09, Benjamin Herrenschmidt wrote:
On Mon, 2003-02-03 at 17:05, Michel Dänzer wrote:
On Mon, 2003-02-03 at 17:34, Alan Cox wrote:
On Mon, 2003-02-03 at 15:02, Keith Whitwell wrote:
-#define COMMIT_RING() do { \
-
export RADEON_NO_VTXFMT=1 helped me.. but its just a workaround
Am 2003.02.03 12:00:49 +0100 schrieb(en) Charl P. Botha:
On Mon, 2003-02-03 at 11:50, Adam K Kirchhoff wrote:
Do we know the causes of these error messages:
drmCommandWrite: -22
drmRadeonCmdBuffer: -22 (exiting)
I don't get
On Mon, Feb 03, 2003 at 02:27:43PM +, Alan Cox wrote:
On Mon, 2003-02-03 at 12:45, Stefan Lange wrote:
VIA/S3 has been contacted several times already, whether they'll allow
the integration of S3TC-support in the DRI. Unfortunately they never
answered. So it's not very likely that
Leif Delgass wrote:
Attached is a patch to the texmem branch with the changes we've been
discussing. I'd still like to take a closer look at the global heap, but
I've included the code to force initializing the global heap on the first
lock contention for now. I've changed the drm/ddx/texmem
This is just a friendly reminder that the weeking dri-devel IRC meeting will
be starting in the #dri-devel channel on irc.freenode.net at 2100 UTC (or
4:00PM EST or 1:00PST, if you prefer).
Time zone conversion available at:
http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Logs of previous IRC
I just answered your questions on the DMX list. Let's keep the discussion
there (or at least cc the DMX list) so that people on the DMX list don't miss out.
DMX, GLXProxy and Chromium really don't have anything to do with the DRI in
particular.
-Brian
Alex Deucher wrote:
I saw this posted
Thanks Brian. BTW, does anyone know of a good archive for dmx-devel?
the one on sourceforge doesn't work 9 times out of 10. I tried to add
the list to mail-archive.com but even subscribing seems to be broken at
the moment.
Alex
--- Brian Paul [EMAIL PROTECTED] wrote:
I just answered your
Yeah, it works, just a little weary of it cause remembering without the
read it won't work, but it still appears to work with the read at the
end.
You mean like this? Chris, does that work for you?
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI
Leif Delgass wrote:
It this looks OK, I will apply it to the branch.
I've poked around with the patch, and it looks good. There are only two
things that I would change. There should probably be a comment in
texmem.h that explains the double-duty that tObj does. I think the
meaning of
No they aren't supported in DRI. For existing apps, they would probably
Thanks for these very good explanation. My ergo: no use. So, it seems
Mach64 does not have any good usable compression technique.
Cheers,
--
Sergey
signature.asc
Description: This is a digitally signed message part
On Mon, 2003-02-03 at 22:31, Chris Ison wrote:
Yeah, it works,
Great!
just a little weary of it cause remembering without the read it won't work,
but it still appears to work with the read at the end.
Well, I think Ben has given the best explanation of what's going on so
far. Keith, are
Michel Dänzer wrote:
On Mon, 2003-02-03 at 22:31, Chris Ison wrote:
Yeah, it works,
Great!
just a little weary of it cause remembering without the read it won't work,
but it still appears to work with the read at the end.
Well, I think Ben has given the best explanation of what's going
On Mon, 2003-02-03 at 22:59, Keith Whitwell wrote:
Michel Dänzer wrote:
On Mon, 2003-02-03 at 22:31, Chris Ison wrote:
Yeah, it works,
Great!
just a little weary of it cause remembering without the read it won't work,
but it still appears to work with the read at the end.
This has been seen before, and fixes a known issue with PCI cards
locking up, the same fix possably fixes an issue occassionaly seen with
AGP card locking up.
It wasn't easy to track down and the fix was only found by accident, it
could well of remained alot longer if I hadn't gotten impatient
The DRI tree no longer contains all the X stuff it needs (hasn't for a
long time, actually) to build but instead relies on it to be installed
on the system.
There is a small glitch with current DRI compilation setup.
If ProjectRoot in (otherwise default) host.def is set to something other
I've been trying both as each have been updated in hopes of seeing a fix
for my 7500 and no such luck :\
anyhow i played around with some of the options in dri
normally with just running it it would load play part of the startup
logo then freeze system is still accessible so running gdb is an
I was under the impression that this doesn't work because it requires s3tc
texture compression, and that doesn't exist in the open-source drivers.
Ken
On 3 Feb 2003, Bret Towe wrote:
I've been trying both as each have been updated in hopes of seeing a fix
for my 7500 and no such luck :\
On Mon, 2003-02-03 at 17:01, Kenneth Culver wrote:
I was under the impression that this doesn't work because it requires s3tc
texture compression, and that doesn't exist in the open-source drivers.
Ken
one of the last patches for ut2k3 had a software decompresser built into
the render to
As has been posted on this list many times (including by myself), one of
the last two patches removed the requirement for a driver with S3TC :-)
Adam
On Mon, 3 Feb 2003, Kenneth Culver wrote:
I was under the impression that this doesn't work because it requires s3tc
texture compression, and
Hahah, ok, well I must have missed it. I havn't tried ut2k3 in a long time
because I recently upgraded from a geforce 3 to a radeon 9700 pro which
has no support in FreeBSD yet (at least no 3d support).
Ken
On Mon, 3 Feb 2003, Adam K Kirchhoff wrote:
As has been posted on this list many times
dri-devel,
dri-develdri-develN¬HSDMéX¬²'²Þu¼¢êÜxZ+á'µêé®+ Øþ >.)îÅj+Ô¨ëax6I硶Úÿ 0½«(~Üç(:âuëÞf¢)à+-¸z÷¥+-²Ê.Ç¢¸ ëa¶Úlÿùb²Û,¢êÜyú+éÞ·ùb²Û?+-wèýÚâuëÞ
42 matches
Mail list logo
