So what about using the XFree86 CVS X server with the DRI CVS DRM and 3D
driver?
This works perfectly, only using the DRM and the GL driver, (and adding
ForcePCIMode the the config), it worked fine, further proof the 2d drivers
deperately need updating. I have noticed some issues with DRI, but
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 04:54 ---
I patched everything as described by Fredo, but DRI Rendering is still NO. Here
is why (I think), who can have a good guess/tip to solve this?
drmOpenDevice: minor is 0
http://bugs.xfree86.org/show_bug.cgi?id=533
[EMAIL PROTECTED] changed:
What|Removed |Added
AssignedTo|[EMAIL PROTECTED] |dri-
|
http://bugs.xfree86.org/show_bug.cgi?id=533
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 05:44 ---
This should work in XFree86 CVS already; both a new 2D driver and DRM are
needed. You can use my dri-trunk-sid packages, see
On Mon, 2003-07-28 at 18:25, Dieter Ntzel wrote:
Am Montag, 28. Juli 2003 12:48 schrieb Michel Dnzer:
On Mon, 2003-07-28 at 09:28, Dieter Ntzel wrote:
gcc
-I/tmp/INSTALL/SOURCE/dri-trunk/HEAD/xc/programs/Xserver/hw/xfree86/os-su
pport/linux/dr m/kernel -D__KERNEL__
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugs.xfree86.org/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at them, and
http://bugs.xfree86.org/show_bug.cgi?id=344
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 06:47 ---
This looks the same as the XFree86 bug #271. I've just added a bit to it, so you
may want to look at that bug number.
--
Configure bugmail:
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 07:18 ---
Please read all comments before posting. Both of you probably need to replace
the DRM module that comes with the 2.4 kernel with the DRM module from the
patched XFree.
On Sun, 2003-07-27 at 23:02, Marcelo E. Magallon wrote:
a couple months from now I might find myself with a bit of free time in
my hands, which I'd like to partially spend working on (free) software
project. In the last year or so I haven't been following the DRI
development in any
http://bugs.xfree86.org/show_bug.cgi?id=344
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://bugs.xfree86.org/show_bug.cgi?id=271
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Additional
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 07:27 ---
The module is the right one. Fredi and me are working on this. It is sure that
the rigth module right place!! But the problem is this:
drmOpenDevice: node name is
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 07:49 ---
Do modprobe radeon and figure out why it fails
When that works you can worry about the X stuff.
--
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
Am Dienstag, 29. Juli 2003 11:34 schrieb [EMAIL PROTECTED]:
http://bugs.xfree86.org/show_bug.cgi?id=533
[EMAIL PROTECTED] changed:
What|Removed |Added
---
- AssignedTo|[EMAIL
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 08:10 ---
Created an attachment (id=437)
-- (http://bugs.xfree86.org/attachment.cgi?id=437action=view)
The kernel patch for 2.4.22-pre8
The kernel patch for 2.4.22-pre8
--
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 08:08 ---
I rediffed the kernel patch against vanilla 2.4.22-pre8. I looked at the
agpgart changes from 2.4.18 to 2.4.22-pre8 and adapted the patch accordingly
(hopefully). this
Am Dienstag, 29. Juli 2003 00:14 schrieb Ian Romanick:
Dieter Ntzel wrote:
Q3A:
After Ian's contex patch/fixes quake3-smp doesn't work anylonger.
Empty black window, no CPU cycles were burnt.
Can you identify exactly which set of changes introduced the problem?
I'll try.
I made several
Am Montag, 28. Juli 2003 23:04 schrieb Ian Romanick:
Roland Scheidegger wrote:
You need this patch
http://sourceforge.net/mailarchive/forum.php?thread_id=2054806forum_id=7
177 for nwn to work (unless you're using the beta 3 client or older, you
definitely need it for 1.29, haven't checked
Michel Daenzer [EMAIL PROTECTED] wrote:
CVSROOT: /cvsroot/dri
Module name: xc
Repository: xc/xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/
Changes by: [EMAIL PROTECTED] 03/07/29 03:11:48
Log message:
* IRQ code cleanup suggested by Linus Torvalds
* i830
Roland Scheidegger wrote:
Keith Whitwell wrote:
Bertrand Lamy wrote:
hello everybody
I have found 3 bugs in the DRI driver. See the attached file for
description. Each program is the 'minimal' code to get the bug.
I also give my computer configuration.
I am quite sure that the bugs lie in the
Am Dienstag, 29. Juli 2003 12:13 schrieb Michel Dnzer:
On Mon, 2003-07-28 at 18:25, Dieter Ntzel wrote:
Am Montag, 28. Juli 2003 12:48 schrieb Michel Dnzer:
On Mon, 2003-07-28 at 09:28, Dieter Ntzel wrote:
gcc
-I/tmp/INSTALL/SOURCE/dri-trunk/HEAD/xc/programs/Xserver/hw/xfree86/o
If I had an SMP box I'd be able to track this down on my own. Instead
all I have are these stinking nearly-top-of-the-line uniprocessor boxes. :)
You can't get hyperthreading running on any of them?
Keith
---
This SF.Net email sponsored
On Tue, 2003-07-29 at 14:53, Martin Spott wrote:
Michel Daenzer [EMAIL PROTECTED] wrote:
CVSROOT:/cvsroot/dri
Module name:xc
Repository: xc/xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/
Changes by: [EMAIL PROTECTED] 03/07/29 03:11:48
Log message:
*
On Maw, 2003-07-29 at 16:05, Keith Whitwell wrote:
The semantics surrounding readbuffer's are a bit non-obvious, and there may be
some bugs in either my understanding or mesa's implementation wrt that function.
It's worth examining the other drivers posting questions on mesa-devel where
http://bugs.xfree86.org/show_bug.cgi?id=271
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 11:47 ---
This makes sense; the chip can apparently be busy for more than 10 milliseconds,
and a reset may actually make things worse. I don't think raising the default
timeout
This patch enables triangle strips and fans support on G400.
- New drm should be compatible with old userspace and vice versa.
- I threw that cull_dualtex stuff out. I moved the spcial case to
EmitHWStateLocked() and it's only used when an old drm is detected. It
is needed because the old drm
On Tue, 2003-07-29 at 18:19, Ville Syrjl wrote:
- I bumped the drm version to 3.2.0 and used that to detect wacceptseq
ioctl support. What's the guideline with this sort of thing?
It looks like you got it right basically. :) You don't need to check the
major version though.
--
Earthling
Alan Cox wrote:
Sort of being: if you use NoAccel for the 2D and providing you run
glxgears with none of the window obscured. I'm still trying to get my
head around the span code and why it doesn't want to call my
SetReadBuffer function. Hopefully with that resolved it'll run the
screensavers
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 13:43 ---
First of all, thanks to everyone working on this code - my IGP320M based
laptop now has accelerated 3D.
At least, some of the time. Other times it kernel panics.
After
On Tue, Jul 29, 2003 at 10:42:02AM -0600, Keith Whitwell wrote:
Ville Syrjälä wrote:
This patch enables triangle strips and fans support on G400.
- New drm should be compatible with old userspace and vice versa.
- I threw that cull_dualtex stuff out. I moved the spcial case to
[EMAIL PROTECTED] wrote:
--- Additional Comments From [EMAIL PROTECTED] 2003-28-07 22:23 ---
Hi, Just wanted to share my positive experience with Hui Yu's patches.
I just bought a Sony VAIO FRV-25 (w/o the modem problem) running Gentoo, here's
an lspci after Hui's patches:
I had this
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 14:41 ---
I've been watching this ever since I opened it. It's at the point where I'm
ready to try it out. Is there a patch for the 2.5 kernels? I'm running 2.5.69
now in order to
On Maw, 2003-07-29 at 18:36, Ian Romanick wrote:
I would like to make one request, though. When you're working on this
area of the driver could you please make sure that the driver will work
if the read buffer and the write buffer are different. With the
exception of the MGA driver,
http://www.heise.de/newsticker/data/ola-29.07.03-007/
http://www.sgi.com/newsroom/press_releases/2003/july/opengl15.html
Brian any timeline, yet? ;-)
Regards,
Dieter
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites
Dieter Nützel wrote:
http://www.heise.de/newsticker/data/ola-29.07.03-007/
http://www.sgi.com/newsroom/press_releases/2003/july/opengl15.html
Brian any timeline, yet? ;-)
Nope.
-Brian
---
This SF.Net email sponsored by: Free pre-built
[EMAIL PROTECTED] wrote:
I just bought a Sony VAIO FRV-25 (w/o the modem problem) running Gentoo, here's
an lspci after Hui's patches:
And I just bought a FRV27. I had the patches for this stuff days ago, but I did
not get a chance to post them since I was at OLS. This patch is against 2.4.21
Hi,
as I'm going to clean up vsync related stuff on the config-0-0-1-branch
I read the code for dynamic glx extension registration in
xc/lib/GL/dri/dri_glx.c and xc/lib/GL/glx/glxextensions.[ch]. I stumbled
over this comment in front of __glXRegisterExtensions:
** In older versions of libGL
Felix Kühling wrote:
Hi,
as I'm going to clean up vsync related stuff on the config-0-0-1-branch
I read the code for dynamic glx extension registration in
xc/lib/GL/dri/dri_glx.c and xc/lib/GL/glx/glxextensions.[ch]. I stumbled
over this comment in front of __glXRegisterExtensions:
** In older
On Tue, 2003-07-29 at 19:31, Ian Romanick wrote:
Michel Dnzer wrote:
On Tue, 2003-07-29 at 09:06, Chris wrote:
This works perfectly, only using the DRM and the GL driver, (and adding
ForcePCIMode the the config),
This will remain necessary until PCI GART is deemed stable with AGP
Jérôme Marant wrote:
Michel Dänzer [EMAIL PROTECTED] writes:
Yes, like that. And fishes appear as rectangles, as well as
trees.
BTW, does setting RADEON_AGPTEXTURING_FORCE_DISABLE work around it? If
so, Ian is working on fixing it.
I've tried export RADEON_AGPTEXTURING_FORCE_DISABLE=1 and it
Am Dienstag, 29. Juli 2003 18:05 schrieb Keith Whitwell:
Martin Spott wrote:
Keith Whitwell [EMAIL PROTECTED] wrote:
Anyway, I'm glad this fixed your problem.
Yep, now I can continue to promote the use ATI boards in the FlightGear
manua ;-)
If anyone likes, I now have a different
Michel Dnzer wrote:
On Tue, 2003-07-29 at 19:31, Ian Romanick wrote:
Michel Dnzer wrote:
On Tue, 2003-07-29 at 09:06, Chris wrote:
This works perfectly, only using the DRM and the GL driver, (and adding
ForcePCIMode the the config),
This will remain necessary until PCI GART is deemed stable
Felix Kühling wrote:
Hi,
as I'm going to clean up vsync related stuff on the config-0-0-1-branch
I read the code for dynamic glx extension registration in
xc/lib/GL/dri/dri_glx.c and xc/lib/GL/glx/glxextensions.[ch]. I stumbled
over this comment in front of __glXRegisterExtensions:
** In older
Am 2003.07.29 22:41:30 +0200 schrieb(en) Ian Romanick:
...
2. I don't like the hackish handing of the pre-1.3 DRM case. Are there
other PCI IDs that need the 128MB offset? Do we even support the
pre-1.3 DRM anymore? If we don't support the pre-1.3 DRM (and don't
intend to fix the
Ian Romanick wrote:
Jérôme Marant wrote:
Michel Dänzer [EMAIL PROTECTED] writes:
Yes, like that. And fishes appear as rectangles, as well as
trees.
BTW, does setting RADEON_AGPTEXTURING_FORCE_DISABLE work around it? If
so, Ian is working on fixing it.
I've tried export
On Tue, 29 Jul 2003 13:58:58 -0700
Ian Romanick [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Hi,
as I'm going to clean up vsync related stuff on the config-0-0-1-branch
I read the code for dynamic glx extension registration in
xc/lib/GL/dri/dri_glx.c and
http://bugs.xfree86.org/show_bug.cgi?id=314
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--
Configure
On Tue, 2003-07-29 at 22:41, Ian Romanick wrote:
1. I don't like the hard-coding of 2*1024*1024 as the size of the
indirect buffers. This was copied directly from the R200 driver, but I
don't like it. We may want to change the size of this buffer at some
point, and hard-coding the
On Maw, 2003-07-29 at 21:45, Ian Romanick wrote:
user-space. The thought of writing the code to walk the PCI device tree
looking for an AGP controller is not a pleasant one, but I may be over
complicating things in my mind.
Linux at least exposes some of the PCI info publically (see libpci,
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 18:45 ---
Given the 2.4 code, which is now on my todo list the 2.5 code shouldn't be hard.
Might be worth asking Dave Jones
--
Configure bugmail:
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 18:55 ---
Alan, please hold off releasing this in any kernels until everything has been
properly integrated in the DRI tree.
--
Configure bugmail:
Felix Kühling wrote:
On Tue, 29 Jul 2003 13:58:58 -0700
Ian Romanick [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Do the __driRegisterExtensions functions in the drivers rely on being
called during initialisation?
In fact I believe it could be dangerous if __driRegisterExtensions was
called
Alan Cox wrote:
On Maw, 2003-07-29 at 21:45, Ian Romanick wrote:
user-space. The thought of writing the code to walk the PCI device tree
looking for an AGP controller is not a pleasant one, but I may be over
complicating things in my mind.
Linux at least exposes some of the PCI info
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-29-07 19:59 ---
I already ported the agpgart driver to 2.5.73. It seems to work. I can post it if it
might be helpful, probably it builds perfectly on 2.6.0-pre2 as well (haven't tested
With a lot of the cards you can tell just be looking at the device (or
subsystem) ID, but I don't think that's the case with the Radeons.
Don't they use the same PCI device ID for both AGP and PCI versions?
They do for the chips, don't know about the subsystems. Hui?
IIRC, bit 0 of the
Antoine REVERSAT wrote:
I just compiled dri from the CVS for my radeon 9000 Mobbility card (r250 lf) and it
wont work as good as it is expected to (I.E : 30 fps in Quake3) The thing is when i do
a glxinfo it is reported as a r200 chip which it isn't... So i'd like to know if you
are aware of
On Wed, 2003-07-30 at 02:59, hy0 wrote:
With a lot of the cards you can tell just be looking at the device (or
subsystem) ID, but I don't think that's the case with the Radeons.
Don't they use the same PCI device ID for both AGP and PCI versions?
They do for the chips, don't know
On Tue, Jul 29, 2003 at 09:44:48PM +0200, Michel Dänzer wrote:
The DDX driver needs to know to decide whether to enable the DRI with
PCI GART or disable it, but the kernel might be in a better position to
find out (though some XFree86 hackers might disagree :)...
well, seeing as how using AGP
58 matches
Mail list logo
