[Dri-devel] drm_clip_rect_t vs XF86DRIClipRectRec in i810..

2004-05-02 Thread Dave Airlie
In Keiths bunch of changes to make the drivers build in Mesa tree he changed the i810_dri .h from using drm_+clip_rect_t to XF86DRIClipRectRec, this break solo, if I change it back it'll probably break dri target... which is correct? Dave. -- David Airlie, Software Engineer

Re: [Dri-devel] r100/200 drawpixels acceleration

2004-05-02 Thread Stephane Marchesin
Dieter Nützel wrote: I get this with current Mesa CVS and DRI CVS for r200: [snip errors] Sorry, a correct patch is attached. Note that to try it, you need : - to draw less than 64KB of pixels (that is ~16000 RGBA8 pixels) - to specify glPixelZoom(1.F,-1.F); - to use the correct pixel format :

[Dri-devel] [Bug 2628] New: Unable to handle kernel paging request at virtual address b29c4104

2004-05-02 Thread bugme-daemon
http://bugme.osdl.org/show_bug.cgi?id=2628 Summary: Unable to handle kernel paging request at virtual address b29c4104 Kernel Version: 2.6.6-rc3-mm1 Status: NEW Severity: normal Owner: [EMAIL PROTECTED] Submitter:

Re: [Dri-devel] drm_clip_rect_t vs XF86DRIClipRectRec in i810..

2004-05-02 Thread Jon Smirl
I thought the long term goal for the Mesa tree is to get rid of all X based type pollution. Every time X based types start getting into the Mesa tree Mesa ends up being dependent on the X header files. Since mesa is used in other places than X we don't want this. So I would think the answer is

[Dri-devel] [Bug 2628] Unable to handle kernel paging request at virtual address b29c4104

2004-05-02 Thread bugme-daemon
http://bugme.osdl.org/show_bug.cgi?id=2628 --- Additional Comments From [EMAIL PROTECTED] 2004-05-02 08:10 --- :01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc Rage Fury Pro/Xpert

[Dri-devel] Pci init code for mesa solo

2004-05-02 Thread Stephane Marchesin
Hi, The attached patch adds pci init code for mesa solo with the radeon driver thanks to a new configuration option in miniglx.conf. Stephane Index: src/glx/mini/driver.h === RCS file: /cvs/mesa/Mesa/src/glx/mini/driver.h,v

[Dri-devel] Re: [Mesa3d-dev] Pci init code for mesa solo

2004-05-02 Thread Stephane Marchesin
Stephane Marchesin wrote: Hi, The attached patch adds pci init code for mesa solo with the radeon driver thanks to a new configuration option in miniglx.conf. And of course, you're not interested in my debugging printf's. A patch without my printfs is attached. Sorry for the noise. Stephane

[Dri-devel] agpgart module loading problem after recompile of DRM

2004-05-02 Thread George Lengel
Hello everyone, I don't know if there is a more appropriate list for this, but I hope someone here can help with my problem. I pulled the latest CVS for the DRI drivers to update the system for my Savage 4.0 card. I wanted to see if I got better 3D performance and possibly fix a few small

[Dri-devel] [drm] initial PCI patch

2004-05-02 Thread Dave Airlie
Hi all, please review: http://freedesktop.org/~airlied/drm_pci_mods.diff This patch starts importing some of Jon Smirls work to the DRM tree, it is 2.6 only at the moment, I'll fix 2.4 for checkin... It makes the DRM use the Linux PCI code, and is a first step on the way to hotplug support...

Re: [Dri-devel] [drm] initial PCI patch

2004-05-02 Thread Jon Smirl
Thanks for fixing my horrible bug it look like I didn't handle unload correctly. Obviously any code going into DRM needs to be checked by multiple developers. 1) drm_probe can fail. Should it check for errors before setting fb_loaded=1? DRM_INFO(Falling back to old detect to due to framebuffer

Re: [Dri-devel] [drm] initial PCI patch

2004-05-02 Thread Dave Airlie
1) drm_probe can fail. Should it check for errors before setting fb_loaded=1? not sure, the fb is still loaded whether the probe fails or not .. some other driver exists on that device.. 2) Does this work? DRM(fb_loaded=1); or should it be DRM(fb_loaded)=1? it works but is also a typo :-)