[Dri-devel] vblank and i810
Well I asked a question on dri-users and Keith said I'd be better asking here .. I want to get my OpenGL application to stop flickering on my i815 using a sync to the vertical refresh, work has apparently started on this for the radeon and g400, so, a) does someone intend working on the i810 driver? b) if !a, where do I start to work on this, I have a development system sitting here waiting :-), and I've no fear of X or kernels, Do I need a particular branch of the dri CVS tree or will the HEAD do fine? Do I need an updated X11/GL to support the new IOCTL? (am running XFree86 4.2.0) Can I avoid downloading/building the Xserver, just grab the DRI stuff? Will this be in 4.3 (I have to do a product and a stable release looks better to management!). Thanks, Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] problems with CVS head and i810
Well I built the CVS tree head and made the i810 modules and ran my test opengl program on it and it worked the first time then started spewing errors ala (II) I810(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x pgetbl_ctl: 0x7e40001 pgetbl_err: 0x0 ipeir: 0 iphdr: c2fb LP ring tail: a0 head: 94 len: f001 start 2ac000 eir: 0 esr: 1 emr: 3d instdone: ff7a instpm: 0 memmode: 4 instps: 10 hwstam: 9ac7 ier: 0 imr: 9ac7 iir: 0 Fatal server error: Active ring not flushed dmesg has this to say: [drm] Initialized i810 1.2.1 20020211 on minor 0 mtrr: base(0xf800) is not aligned on a size(0x12c000) boundary PCI: Found IRQ 11 for device 00:02.0 [drm:i810_wait_ring] *ERROR* space: 65508 wanted 65528 [drm:i810_wait_ring] *ERROR* lockup I had set the library path to pick up the newer version of the GL libs.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] [PATCH] i810 cleanup
This takes some of the stuff that was recently submitted to the xfree86.org for the i830 and tries to move the i810 along similiar lines... is all cosmetic apart from a new define for the FRONTBUFFER command this is what they call it in the i815 spec anyways. I'm submitting the equivalent patch to xfree86 (well slightly changed) for their tree also. Then I'll start moving over the i830 page flipping code from the xfree86 tree into an i810 driver. Anyone want to sync up our i830 with xfree86's? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person dri_diff Description: Binary data
Re: [Dri-devel] [PATCH] i810 cleanup
doh doh!! wasn't sync'ed properly with the tree (damn firewall!!)... this diff is a bit better and doesn't remove functionality... Dave. Dave Airlie said: This takes some of the stuff that was recently submitted to the xfree86.org for the i830 and tries to move the i810 along similiar lines... is all cosmetic apart from a new define for the FRONTBUFFER command this is what they call it in the i815 spec anyways. I'm submitting the equivalent patch to xfree86 (well slightly changed) for their tree also. Then I'll start moving over the i830 page flipping code from the xfree86 tree into an i810 driver. Anyone want to sync up our i830 with xfree86's? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person dri_diff Description: Binary data
Re: [Dri-devel] problems with CVS head and i810
Dave Airlie said: Which application is this? glxgears from RH4.2 blows it away also!! I might try constucting a brand new root file system for my development system using the DRI tree, I'm currently running X etc from the DRI tree in my home directory (un-installed). Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] [PATCH] i810 cleanup
Well the i830 page flip code is using async flips, the main thing I want to use page flipping for on my i815 is sync'ed flips so I don't see the tearing that is so really obvious and gives people headaches.. (don't need to be getting sued here!!). It's not the timing I'm worried about it's the tearing, it can be slow as long as its not really ugly... the i815 can't do async page flipping properly anyways there is a bug in the silicon I would assume they fixed it for the i830 ... Also my current application is a single 3D window taking up the full screen, I doubt I'll ever any 2d windows interfering which is handy for me... My major issue now is finding a CVS tree which works for me on my development platform that I can then add code to. As my patch doesn't affect anything other than cleanup can you check it in? Dave. The 830 page flipping code is turned off for some good reasons: - I haven't seen it work without really visible corruption on the flip - typically flashing and blank areas - It isn't actually all that fast - there is a delay while (presumably) the ramdac cache or fifo drains - this is comparable to the time to blit the window itself. The crossover point was about 300x300 on my test box, but would vary for different machines. - Because of the above, it is necessary to wait for the flip to finish before clearing the backbuffer starting the next frame, otherwise you see this happen. Actually this invalidates my explanation of the delay -- the fact that you can see the clear implies that the ramdac is still grabbing new values from the frontbuffer, so I don't really know what the delay arises from. Keith -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: [Dri-devel] [PATCH] i810 cleanup
Nice one, that gets rid of my tearing - thanks Matthew, it works except now I get some jumpiness on my screen when a new texture is coming on, I've got 5 rotating reels of 4 textured quads and when the new ones are about to come on the top of the reel it seems to jump a bit... Not sure if the fullscreen would help here.. I need to time each render and see if this one takes a lot longer than the others.. Dave. Sottek, Matthew J said: The easiest way to get rid of tearing is to make the ring buffer wait before the back-front blit. This is a very simple mechanism that will work even for windowed 3d, and if you are running just one 3d client the wait time should not alter your performance much. Or rather, the performance decrease should not be different than any other correct rendering. Just add a GFXCMDPARSER_LOAD_SCAN_LINES_INCL and a GFXCMDPARSER_WAIT_FOR_EVENT prior to the blit. This will hold the blit as long as it would tear on the screen. Small windows will not have to wait for a vblank, they only wait while the current scan intersects the blit. If you don't want to do that, you can just use the wait for event to block until the vblank as I mentioned before. This will make the rendering at least correct, you can then work on the page flipping as an optimization for full screen. -Matt -Original Message- From: Dave Airlie [mailto:[EMAIL PROTECTED]] Sent: Monday, December 16, 2002 6:57 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Dri-devel] [PATCH] i810 cleanup Well the i830 page flip code is using async flips, the main thing I want to use page flipping for on my i815 is sync'ed flips so I don't see the tearing that is so really obvious and gives people headaches.. (don't need to be getting sued here!!). It's not the timing I'm worried about it's the tearing, it can be slow as long as its not really ugly... the i815 can't do async page flipping properly anyways there is a bug in the silicon I would assume they fixed it for the i830 ... Also my current application is a single 3D window taking up the full screen, I doubt I'll ever any 2d windows interfering which is handy for me... My major issue now is finding a CVS tree which works for me on my development platform that I can then add code to. As my patch doesn't affect anything other than cleanup can you check it in? Dave. The 830 page flipping code is turned off for some good reasons: - I haven't seen it work without really visible corruption on the flip - typically flashing and blank areas - It isn't actually all that fast - there is a delay while (presumably) the ramdac cache or fifo drains - this is comparable to the time to blit the window itself. The crossover point was about 300x300 on my test box, but would vary for different machines. - Because of the above, it is necessary to wait for the flip to finish before clearing the backbuffer starting the next frame, otherwise you see this happen. Actually this invalidates my explanation of the delay -- the fact that you can see the clear implies that the ramdac is still grabbing new values from the frontbuffer, so I don't really know what the delay arises from. Keith -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: [Dri-devel] [PATCH] i810 cleanup
Well that's a dodgy application on my part.. it now works sync'd with it .. How should I do this without changing the kernel i810 module? is there an way from the OpenGL level to do this that I could propogate down? Dave. Dave Airlie said: Nice one, that gets rid of my tearing - thanks Matthew, it works except now I get some jumpiness on my screen when a new texture is coming on, I've got 5 rotating reels of 4 textured quads and when the new ones are about to come on the top of the reel it seems to jump a bit... Not sure if the fullscreen would help here.. I need to time each render and see if this one takes a lot longer than the others.. Dave. Sottek, Matthew J said: The easiest way to get rid of tearing is to make the ring buffer wait before the back-front blit. This is a very simple mechanism that will work even for windowed 3d, and if you are running just one 3d client the wait time should not alter your performance much. Or rather, the performance decrease should not be different than any other correct rendering. Just add a GFXCMDPARSER_LOAD_SCAN_LINES_INCL and a GFXCMDPARSER_WAIT_FOR_EVENT prior to the blit. This will hold the blit as long as it would tear on the screen. Small windows will not have to wait for a vblank, they only wait while the current scan intersects the blit. If you don't want to do that, you can just use the wait for event to block until the vblank as I mentioned before. This will make the rendering at least correct, you can then work on the page flipping as an optimization for full screen. -Matt -Original Message- From: Dave Airlie [mailto:[EMAIL PROTECTED]] Sent: Monday, December 16, 2002 6:57 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Dri-devel] [PATCH] i810 cleanup Well the i830 page flip code is using async flips, the main thing I want to use page flipping for on my i815 is sync'ed flips so I don't see the tearing that is so really obvious and gives people headaches.. (don't need to be getting sued here!!). It's not the timing I'm worried about it's the tearing, it can be slow as long as its not really ugly... the i815 can't do async page flipping properly anyways there is a bug in the silicon I would assume they fixed it for the i830 ... Also my current application is a single 3D window taking up the full screen, I doubt I'll ever any 2d windows interfering which is handy for me... My major issue now is finding a CVS tree which works for me on my development platform that I can then add code to. As my patch doesn't affect anything other than cleanup can you check it in? Dave. The 830 page flipping code is turned off for some good reasons: - I haven't seen it work without really visible corruption on the flip - typically flashing and blank areas - It isn't actually all that fast - there is a delay while (presumably) the ramdac cache or fifo drains - this is comparable to the time to blit the window itself. The crossover point was about 300x300 on my test box, but would vary for different machines. - Because of the above, it is necessary to wait for the flip to finish before clearing the backbuffer starting the next frame, otherwise you see this happen. Actually this invalidates my explanation of the delay -- the fact that you can see the clear implies that the ramdac is still grabbing new values from the frontbuffer, so I don't really know what the delay arises from. Keith -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org
RE: [Dri-devel] [PATCH] i810 cleanup
BTW: Did you go with wait for scanline or wait for vblank? The latter is more invasive... if you were doing multiple windowed clients there would only be ONE buffer flip per retrace to be shared between the clients. I just went with the wait for vblank (patch attached for demonstration purposes...) as I'm only doing a single 3d application full screen... and I'll probably just use that for our purposes here, as I need to keep a stable tree with minor patches - regulated industry isn't always the best :-) Dave. -Matt -Original Message- From: Dave Airlie [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 8:39 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [Dri-devel] [PATCH] i810 cleanup Well that's a dodgy application on my part.. it now works sync'd with it .. How should I do this without changing the kernel i810 module? is there an way from the OpenGL level to do this that I could propogate down? Dave. Dave Airlie said: Nice one, that gets rid of my tearing - thanks Matthew, it works except now I get some jumpiness on my screen when a new texture is coming on, I've got 5 rotating reels of 4 textured quads and when the new ones are about to come on the top of the reel it seems to jump a bit... Not sure if the fullscreen would help here.. I need to time each render and see if this one takes a lot longer than the others.. Dave. Sottek, Matthew J said: The easiest way to get rid of tearing is to make the ring buffer wait before the back-front blit. This is a very simple mechanism that will work even for windowed 3d, and if you are running just one 3d client the wait time should not alter your performance much. Or rather, the performance decrease should not be different than any other correct rendering. Just add a GFXCMDPARSER_LOAD_SCAN_LINES_INCL and a GFXCMDPARSER_WAIT_FOR_EVENT prior to the blit. This will hold the blit as long as it would tear on the screen. Small windows will not have to wait for a vblank, they only wait while the current scan intersects the blit. If you don't want to do that, you can just use the wait for event to block until the vblank as I mentioned before. This will make the rendering at least correct, you can then work on the page flipping as an optimization for full screen. -Matt -Original Message- From: Dave Airlie [mailto:[EMAIL PROTECTED]] Sent: Monday, December 16, 2002 6:57 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Dri-devel] [PATCH] i810 cleanup Well the i830 page flip code is using async flips, the main thing I want to use page flipping for on my i815 is sync'ed flips so I don't see the tearing that is so really obvious and gives people headaches.. (don't need to be getting sued here!!). It's not the timing I'm worried about it's the tearing, it can be slow as long as its not really ugly... the i815 can't do async page flipping properly anyways there is a bug in the silicon I would assume they fixed it for the i830 ... Also my current application is a single 3D window taking up the full screen, I doubt I'll ever any 2d windows interfering which is handy for me... My major issue now is finding a CVS tree which works for me on my development platform that I can then add code to. As my patch doesn't affect anything other than cleanup can you check it in? Dave. The 830 page flipping code is turned off for some good reasons: - I haven't seen it work without really visible corruption on the flip - typically flashing and blank areas - It isn't actually all that fast - there is a delay while (presumably) the ramdac cache or fifo drains - this is comparable to the time to blit the window itself. The crossover point was about 300x300 on my test box, but would vary for different machines. - Because of the above, it is necessary to wait for the flip to finish before clearing the backbuffer starting the next frame, otherwise you see this happen. Actually this invalidates my explanation of the delay -- the fact that you can see the clear implies that the ramdac is still grabbing new values from the frontbuffer, so I don't really know what the delay arises from. Keith -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person
Re: [Dri-devel] Re: Invitation for public discussion about the futureof X
patches. I guess this 'prolonged' period, is the stickling point for most. Why not simply have a second CVS repository, where most development would take place under, while the current repository would be the one used for (pre-/post-) releases with coarse-grain commits. Like stable and development branches, but with the branches being on different repositories. Why a second repository then, instead of just branches, and maybe restricting most developers to commit to branches and only allow some to commit to the trunk, for example? I don't see much advantage in a separate repository (but I may simply be missing it, clues appreciated :), but it makes merges more difficult. I think something like the gcc project has nowadays.. granted it took a fork to make them get up of their proverbials and get moving but I think now its a lot more open and releases are a lot more frequent and controlled.. I think XFree may have to go through a similiar process to gcc, I'd love to see it happen without the fork and giving out though :-), they also have toplevel maintainters and then architecture and stuff like that maintainers.. so for Xfree86 perhaps driver maintainters (who aren't toplevel people, like mharris for Radeon for example) should be appointed and they should be given free reign in their driver... outside their driver the toplevel people need to get involved ... Granted you don't have to listen to me :-) I've only submitted one patch in my life to XFree and that was only a cleanup!!... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This SF.net email is sponsored by: Tablet PC. Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] i810 sharing interrupts race condition..
I've just had the misfortune of having my NFSROOT system (lots of network
interrupts), have its card sharing interrupts with the i810 graphics..
once I run anything 3d the kernel oops..
The attached patch contains the quick fix which is to check in thr irq
handler if dev-dev_private is NULL or not before going using it .. also a
udelay patch included which I think the DRI tree has but the LK one
doesn't(arrgg too many trees :-)..
I've attached a second patch to
xc/xc/programs/Xserver/hw/xfree86/drivers/i810/i810_dri.c that may also
fix the problem but which I haven't tested,
What happens is the DMA cleanup occurs which frees the private data, and
an interrupt comes in from the network card most likely but the i810
driver is let know as the IRQ hasn't been deregistered yet..
This issue also will affect the i830 and gamma (not that anyone cares) but
maybe others as well as my DRI tree is old enough at this stage
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / [EMAIL PROTECTED]
pam_smb / Linux DecStation / Linux VAX / ILUG personIndex: drivers/char/drm/i810_dma.c
===
RCS file: /home/sapphire/saphcvs/kernel-2.4/drivers/char/drm/i810_dma.c,v
retrieving revision 1.1.1.2
diff -u -r1.1.1.2 i810_dma.c
--- drivers/char/drm/i810_dma.c 26 Feb 2003 01:37:26 - 1.1.1.2
+++ drivers/char/drm/i810_dma.c 24 Mar 2003 04:01:46 -
@@ -36,6 +36,7 @@
#include i810_drv.h
#include linux/interrupt.h /* For task queue support */
#include linux/module.h
+#include linux/delay.h
/* in case we don't have a 2.3.99-pre6 kernel or later: */
#ifndef VM_DONTCOPY
@@ -317,7 +318,7 @@
goto out_wait_ring;
}
- for (i = 0 ; i 2000 ; i++) ;
+ udelay(1);
}
out_wait_ring:
@@ -894,19 +895,23 @@
void i810_dma_service(int irq, void *device, struct pt_regs *regs)
{
drm_device_t *dev = (drm_device_t *)device;
- drm_i810_private_t *dev_priv = (drm_i810_private_t *)dev-dev_private;
+ drm_i810_private_t *dev_priv;
u16 temp;
- atomic_inc(dev-counts[_DRM_STAT_IRQ]);
- temp = I810_READ16(I810REG_INT_IDENTITY_R);
- temp = temp ~(0x6000);
- if(temp != 0) I810_WRITE16(I810REG_INT_IDENTITY_R,
+ if (dev-dev_private) {
+ dev_priv = (drm_i810_private_t *)dev-dev_private;
+
+ atomic_inc(dev-counts[_DRM_STAT_IRQ]);
+ temp = I810_READ16(I810REG_INT_IDENTITY_R);
+ temp = temp ~(0x6000);
+ if(temp != 0) I810_WRITE16(I810REG_INT_IDENTITY_R,
temp); /* Clear all interrupts */
- else
- return;
+ else
+ return;
- queue_task(dev-tq, tq_immediate);
- mark_bh(IMMEDIATE_BH);
+ queue_task(dev-tq, tq_immediate);
+ mark_bh(IMMEDIATE_BH);
+ }
}
void i810_dma_immediate_bh(void *device)
--- xc/xc/programs/Xserver/hw/xfree86/drivers/i810/i810_dri.c.orig 2003-03-24
15:17:38.0 +1100
+++ xc/xc/programs/Xserver/hw/xfree86/drivers/i810/i810_dri.c 2003-03-24
15:19:00.0 +1100
@@ -949,6 +949,11 @@
ScrnInfoPtr pScrn = xf86Screens[pScreen-myNum];
I810Ptr pI810 = I810PTR(pScrn);
+ if (info-irq) {
+ drmCtlUninstHandler(pI810-drmSubFD);
+ info-irq = 0;
+ }
+
I810CleanupDma(pScrn);
if (pI810-dcacheHandle)
Re: [Dri-devel] i810 sharing interrupts race condition..
I've attached a second patch to
xc/xc/programs/Xserver/hw/xfree86/drivers/i810/i810_dri.c that may also
fix the problem but which I haven't tested,
yeah you can ignore the patch, but the idea is correct I think, the patch
is bogus using variables from places that dont exist :-)...
of course what it should do it is more like :
--- xc/xc/programs/Xserver/hw/xfree86/drivers/i810/i810_dri.c.orig 2003-03-24
15:17:38.0 +1100
+++ xc/xc/programs/Xserver/hw/xfree86/drivers/i810/i810_dri.c 2003-03-24
16:21:08.0 +1100
@@ -948,6 +948,12 @@
{
ScrnInfoPtr pScrn = xf86Screens[pScreen-myNum];
I810Ptr pI810 = I810PTR(pScrn);
+ I810DRIPtr pI810DRI = (I810DRIPtr) pI810-pDRIInfo-devPrivate;
+
+ if (pI810DRI-irq) {
+ drmCtlUninstHandler(pI810-drmSubFD);
+ pI810DRI-irq = 0;
+ }
I810CleanupDma(pScrn);
---
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] question re 810 vs 830 drivers
I've noticed the i830 drivers have a unified memory allocation scheme for 2d and 3d, is there any reason this couldnt be used on the i810? Is there any major reasons the i830 driver couldn't be usd on the i810 with the functionality it doesn't need turned off? I'm just wondering the i810/i830 drivers look very close and I persume were once unified and got separated somewhere for a reason.. just wondering was the reason because of something lowlevel that wasn't compatible or the author didn't want to break an old chipset he had no access to? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] i810 drm page flipping support..
Correct. The patch looks good. Do you actually get a speedup from page flipping on the i810? Are there ever any visual corruptions that you would attribute to the hardware? I havent got the numbers on my home machine, but I got a definite speedup on an 800x600 glxgears, and an internal application, I'm going to get further numbers when our internal app stabilises a bit more .. The hardware seems to be solid except for the ASYNC flipping which has an errata and which I don't enable for that reason.. I'll apply the DRM patch tomorrow at work and start cutting up the rest of it... Dave. Keith --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] i810 drm page flipping support..
Do you actually get a speedup from page flipping on the i810? Are there ever any visual corruptions that you would attribute to the hardware? I havent got the numbers on my home machine, but I got a definite speedup on an 800x600 glxgears, and an internal application, I'm going to get further numbers when our internal app stabilises a bit more .. of course the main issue with FPS type mesaurements is that I have to use a SYNC'ed flip which means I get refresh rates, so glxgears is not useful (I did run it without sync and it did go faster if not a while lot uglier)_ my internal app is much more processor intensive so I'll try and convince it it wants to work (it has a lot of other issues :-) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] [trunk] i810_dma.c compilation error
wierd.. I've fixed this, but it built for me fine something wierd with RING_LOCALS? Dave. On Fri, 6 Jun 2003, Dieter [iso-8859-15] Nützel wrote: i810_dma.c: In function `i810_dma_dispatch_flip': i810_dma.c:834: parse error before `int' i810_dma.c:853: `pitch' undeclared (first use in this function) i810_dma.c:853: (Each undeclared identifier is reported only once i810_dma.c:853: for each function it appears in.) make[12]: *** [i810_dma.o] Error 1 Regards, Dieter --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Problem with latest trunk and i810?
But DIR doesn't seem to work with my i810 chipset. I'm attaching my 'dmesg' and 'XFree86.0.log'. Any help would be nice. :) (logs compressed because of the 40kb limit!) glxinfo says direct rendering is disabled. (II) I810(0): [dri] Unable to allocate backbuffer memory. Disabling DRI. (II) I810(0): [drm] removed 1 reserved context for kernel (II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xd08d4000 at 0x4 try making the 16384 video ram to 32768 or decrease your screen size.. start maybe at 1024x768... Dave. Thanks -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DecStation / Linux VAX / ILUG person --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] i810 page flipping mesa and dri patches
http://www.skynet.ie/~airlied/patches/dri i810_mesa.diff i810_drivers.diff The only contentious piece I believe is the changes to i810_accel.c that do the draws to both front and back buffers, but as I know these aren't good enough to do complete page flipping, so I've no problem not commiting these if people think they aren't helping anything and just cluttering up code.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] i810 page flipping mesa and dri patches
do the draws to both front and back buffers, but as I know these aren't good enough to do complete page flipping, so I've no problem not commiting these if people think they aren't helping anything and just cluttering up code.. You're already using a shadow type mechanism, right? Drawing twice like that would be redundant, unless you finished the job were able to get rid of the shadow code? nope didn't finish it.. I think the shadow code didn't work very well at all but I'll see about doing some more experiments,, I'm trying to get an i810 machine at home, I'll check in the bits without the accel stuff, as they are similiar to what is done in the other pf enabled drivers, it may be my copying stuff is clobbering my shadow stuff.. sound okay? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Problem with latest trunk and i810?
He looks to have something here, alright.. the key can be zero, I'm just updating to trunk at the moment to see if I can reproduce it.. the radeon_dri.c has a similiar issue but it isn't as serious in their case, they check for freeing the AGP memory if (info-agpMemHandle) they use the return value to do do the setup... (this might explain some of the radeon mode switcihing issues??) so as far as I can see we've probably 3 choices, a)add isValid variables to the I810Rec strucutre for each handle, b) switch to signed long types for the handles and use -1 as an illegal handle (the keys are only signed ints) c) leave types as unsigned longs and use 0x as an illegal handle value... and of course d) revert back to using memory-memory, requires whoever switched us to key to explain :-) Dave. On Mon, 7 Jul 2003, Keith Whitwell wrote: Ronald Baljeu wrote: On Mon, Jul 07, 2003 at 09:59:15AM +0100, Keith Whitwell wrote: Ronald Baljeu wrote: The traditional approach would be to do a binary search to narrow down which change caused the problems -- probably using the DRI cvs tree. Keith Ok, after several days of searching I think I found something here. In i810_dri.c of the Xfree CVS (I could not get into the DRI CVS) several calls are made to drmAgpAlloc(). To test whether this call was successful the returned handle is checked: if it is 0 it is assumed the call failed. Like this: drmAgpAlloc(pI810-drmSubFD, back_size, 0, NULL, agpHandle); if (agpHandle != 0) /* ok */ else /* error */ However I think 0 is a legal handle. Shouldn't the return value of the call be checked instead? Looking at the kernel modules and header files I noticed how this used to work this way. The agpHandle used to be a pointer internally (in the agp_memory struct), but it has been changed to a key. It's difficult to describe what I mean. Maybe this helps: xc/programs/Xserver/hw/xfree86/drivers/i810/i810_dri.c: call to drmAgpAlloc() as described above xc/programs/Xserver/hw/xfree86/os-support/linux/drm/xf86drm.c: body of drmAgpAlloc(), with a call to ioctl(DRM_IOCTL_AGP_ALLOC) xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/drm.h: #define DRM_IOCTL_AGP_ALLOC DRM_IOWR(0x34, drm_agp_buffer_t) xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/drm_drv.h: mapping DRM_IOCTL_AGP_ALLOC to DRM(agp_alloc) xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/drm_agpsupport.h: body of DRM(agp_alloc) In the body of DRM(agp_alloc) a small change was made from: entry-handle= (unsigned long)memory-memory; to: entry-handle= (unsigned long)memory-key; So, tracing this back from kernel to userland, this key is now passed as agpHandle in the example above, instead of the memory pointer. Now the handle can legally be 0, but the source of i810_dri.c still treats it like a pointer of which 0 indicates an error. Could this be the source of the problem? Or am I way off ;-) Ronald, If you're way off, at this point it sounds like you've got a better idea than I... I'm forwarding this to dri-devel in the hope that this rings a bell with someone there. From CVS you can tell who made the change - that might help to get a quick response... Keith --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Problem with latest trunk and i810?
and of course d) revert back to using memory-memory, requires whoever switched us to key to explain :-) Okay this was done by David Dawes back in April, and was taken from the XFree trunk, it looks like it is needed. so one of the other three approaches is needed... Dave. --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Problem with latest trunk and i810?
I'd lean towards using ~0 as the error value and keeping the existing types, etc. potential patch at: http://www.skynet.ie/~airlied/patches/dri/i810_drm_agp.diff I wonder if we should change the drmAgpAlloc function to set the handle to DRM_AGP_NO_HANDLE? Other drivers will need some fixin also if the soln is acceptable.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Problem with latest trunk and i810?
Yes, that would be cleaner. patch for not only the i810 but also the fixes for radoen/r128/mga drivers, along with the changes to xf86drm.[ch] ... http://www.skynet.ie/~airlied/patches/dri/agp_drm.diff I think XFree86 tree is going to need something along these lines also, but I don't have an XFree86 tree on my PC (apart from 4.3)... if no-one screams I'll apply it tomorrow... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Problem with latest trunk and i810? (fwd)
sent this from wrong address.. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person -- Forwarded message -- Date: Wed, 9 Jul 2003 08:56:17 +0100 (IST) From: Dave Airlie [EMAIL PROTECTED] To: Keith Whitwell [EMAIL PROTECTED] Cc: dri-devel [EMAIL PROTECTED], Ronald Baljeu [EMAIL PROTECTED] Subject: Re: [Dri-devel] Re: Problem with latest trunk and i810? On Wed, 9 Jul 2003, Keith Whitwell wrote: if no-one screams I'll apply it tomorrow... Looks like David has already ported applied it to XFree86. yeah but I'm hanging on bug 484 to make sure he is correct.. read 484, David believes there is a drm/driver issue... I'm not 100% convinced it is that important, of course he does know better than me :-), so I'll apply his fix to our tree and then we need to get the drm change into the kernel that David made. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Problem with latest trunk and i810?
On Wed, 9 Jul 2003, Keith Whitwell wrote: if no-one screams I'll apply it tomorrow... Looks like David has already ported applied it to XFree86. yeah but I'm hanging on bug 484 to make sure he is correct.. read 484, David believes there is a drm/driver issue... I'm not 100% convinced it is that important, of course he does know better than me :-), so I'll apply his fix to our tree and then we need to get the drm change into the kernel that David made. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] comment in test1-ac1 changelog..
Hi Alan (et dri-devel), In your -ac1 release you mention that you have a todo to look at the horribly out of date 2.5 DRM layer, AFAIK Linus is fairly in sync with the DRI tree on sf.. any recent changes I've made are in -test1, the 2.4 tree is probably more out of date (the agp key stuff isn't in 2.4 yet)... Are there changes to the DRM from 2.4 that haven't made it into the dri tree... I can take a look if this is the case.. have you any plans to sync up 2.4-ac with DRI and submit to Marcelo? Thanks, Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] comment in test1-ac1 changelog..
2.4-test works for the cards I've got, 2.5 crashes for radeon and seems to have i810 problems. I've not looked deeply into it yet since with 2.6.0 test I've got other radeon related problems that make X crash without DRI even. I think the latest Linus update should fix the i810 issue that was reported here, but there may still be some hiding, (that was the one with the key being 0) but I think any probs in 2.6.0-test1 we should also see in the the DRI tree... I might have a go later with 2.6.0-test1 and my i815 board... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] moving i810 to texmem, testing...
i might be able to get time to move the i810 to texmem soon, firstly as Keith has let me know, I need to move the i810 to using its own texture formats (it's still stuck back in the mesa3.4 days)... so is there a set of comphrensive tests that I can run before and after to make sure that I haven't messed things up too badly... some sort of texture mapping tester... that covers most of the cases... thanks, Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] i810 texture upload patch
http://www.skynet.ie/~airlied/patches/dri/i810_tex_upload.diff I used the texenv demos from Mesa 5.0 to test this, I tested it with the old driver and this one, and they both look the same.. however neither of them show the intensity row like my Nvidia card on my main desktop .. on the i810 I just get four boxes of differing greys, like the lumiance one (slightly different greys), but on the NVidia it is more like the Alpha row... if no issues I'll commit this, and move onto texmem proper.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] i810 texture upload patch
I used the texenv demos from Mesa 5.0 to test this, I tested it with the old driver and this one, and they both look the same.. Have you tried it with anything else? Quake3? Think Tanks demo? Any of the other Mesa demos? well I've got a very limited test system, it's NFSrooted of my main system, am getting an in-house i810 board soon hopefully at home so I can do some better work on it ... looks different than with the software rasterizer (i.e., LIBGL_ALWAYS_INDIRECT=y)? Could you make a screen shot available? looks the same with LIBGL_ALWAYS_INDIRECT...but for some reason I can't screen grab it .. I'll post some shots at http://www.skynet.ie/~airlied/dri/screen/ in a minute or two, one from my Nvidia and one from my i810, if someone could give texenv a go on something else, and tell me what it looks like .. The code is knocked off from the i830 alright, with the 32-bit stuff ripped out, the textures fixed for texenv.. my only worry is the ycbcr ones.. any good ycbcr tests out there? I'll check it in, as it shouldn't break anything ... Dave. p.s. I'll be getting a radeon mobility 7500, and mobility 9000 in the next few weeks hopefully (have specs already), so I might get some time on that all else depending company are considering using an in-house AGP card with mobility to supplement the i810 for some applications... -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Simple example fails w/direct rendering
this is something to do with double buffering no sure what is going wrong though, probably getting a doubled buffered visual and using it as single or somthing... adding glutInitDisplayMode(GLUT_RGB | GLUT_DOUBLE ); to the main before CreateWindow and glutSwapBuffers(); to the end if display make it work for me on my mach64... Dave. On Wed, 6 Aug 2003, Nathan Gray wrote: Hello, This is an example from an opengl tutorial that I'm trying out. If I run it with LIBGL_ALWAYS_INDIRECT it works fine, but with direct rendering I just get a blank window. I'm using the radeon driver from recent CVS (checked out yesterday anonymously) on a Dell Inspiron 4150 w/Radeon Mobility M7. Any ideas? Thanks, -n8 -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] i810 compatibility fix upgraded to latest tree..
Okay I've updated Matthew's DRM compatibility fix for the top of DRI tree, http://www.skynet.ie/~airlied/patches/dri/i810_compat.diff I'll apply it in a couple of days as it seemed to be agreed previously that it solves the problem.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] i810/i810 MAX_TEXLEVELS ...
I'm running my own internal application (lots of texturing) and I'm crashing out in the i810UploadTexImages, trying to upload a level 11 mipmap, but the i810tex.h has MAX_TEXLEVELS set to 10, so of course I'm corrupting memory earlier when assigning the pointers in i810SetTexImages, the i830 probably has the same issue, so fix a) is to check the number of levels isn't greater than MAX_TEXLEVELS at some stage,.. how do I decide which level to dump? just dump the last one? or b) up MAX_TEXLEVELS - but I assume this is hardware limitation, I'll read my i810 data sheet.. but Keith do you remember? Regards, Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] [Bug 555] glplanet from X screensaver displaysincorrectly under XF4.3 and DRI-HEAD
Can anyone do this test for me? just run the /usr/X11R6/lib/xscreensaver/glplanet on an i830 or above chipset and tell me if you can see through the earth, (i.e. it looks transparent) Either let me know or add it to bug 555 ... Dave. --- Additional Comments From [EMAIL PROTECTED] 2003-05-08 14:19 --- Hm, better you ask this on the DRI-DEVEL list. I'd need to dig out my i855 and I won't be able to do this anytime soon. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] aligning i810 2.4 kernel and CVS DRMs...
okay ignore parts of that that cast stuff.. that was some tiredness sneaking in.. hw_status_page is a void *... I know this now :-) so just look at the module changes and tell me if they are okay for 2.6.. Dave. On Fri, 8 Aug 2003, Dave Airlie wrote: Okay my first patch is up at http://www.skynet.ie/~airlied/patches/dri/drm_i810_diff1.diff This takes any obvious changes from the 2.4.20 kernel and 2.4.20-19.8 I have on my PC, my only issue is whether this breaks in a 2.6 kernel (I don't have 2.6 time on my hands yet :-)... is all the module parameter stuff the same in 2.6 if so then I'll commit this... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] aligning i810 2.4 kernel and CVS DRMs...
Okay my first patch is up at http://www.skynet.ie/~airlied/patches/dri/drm_i810_diff1.diff This takes any obvious changes from the 2.4.20 kernel and 2.4.20-19.8 I have on my PC, my only issue is whether this breaks in a 2.6 kernel (I don't have 2.6 time on my hands yet :-)... is all the module parameter stuff the same in 2.6 if so then I'll commit this... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] aligning i810 2.4 kernel and CVS DRMs...
On Fri, 8 Aug 2003, Michel Dänzer wrote: BTW, doesn't the solution for the incompatibility discussed in http://www.geocrawler.com/mail/thread.php3?subject=%5BDri-devel%5D+i810+DRM+compatibility+fixlist=680 work after all? i can adapt that patch and put it in the dri tree, I wasn't aware of it before now .. it doese look like a cleaner solution alright so any objections...? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] i810/i810 MAX_TEXLEVELS ...
On Mon, 11 Aug 2003, Brian Paul wrote: or b) up MAX_TEXLEVELS - but I assume this is hardware limitation, I'll read my i810 data sheet.. but Keith do you remember? The ctx-Const.MaxTextureLevels field should be set to the appropriate value during context initialization in the driver. Looks like this is being done at round line 162 of i810context.c. 11 levels implies a max texture size of 1024x1024. Thanks Brian, I've checked a patch in to make I810_TEX_MAXLEVELS 11, as the context code uses up to 11, I think i830 may suffer from a similiar issue but I don't have one Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Kernel tree CVS merge..
okay I'm happy to apply the i810 portion and will do so soon, someone else
want to look after the other pieces or should I do them also?
Dave.
On Thu, 14 Aug 2003, Linus Torvalds wrote:
Ok,
I just did another kernel merge to pick up the i810 compatibility bits,
and decided it is time to try to merge back some of the stuff that has
accumulated in the standard kernel and that makes it more painful than
necessary to examine the diffs for differences.
This is mostly whitespace changes (some of it new from Dave Jones, some of
it quite old), and some other minor things: moving some counter and lock
initializations slightly earlier to where the data structure they are in
are allocated and initialized, so that interrupts can't even by mistake
see them partially done.
It also removes the printk() for the AGP version, since that is actually
done by the AGP layer anyway.
I'd appreciate it if all (or even most) of this could find itself back
into the DRI CVS tree, to make it easier to read the code and merge it
(some of the whitespace fixes are literally broken whitespace in the DRI
tree - comments that end up being in strange columns etc).
Apart from moving some initializations around and the aforementioned
printk removal, this should not actually affect semantics at all.
Oh, and the thing will apply with a few offsets, since I edited the patch
to remove stuff that you don't want at this point. My tree doesn't contain
all of the 2.4.x compatibility crud etc.
You can apply (or not apply) everything independently, so feel free to
cherry-pick the patches. I did edit out anything that looked even remotely
like it could cause discussion (ie this does _not_ contain the
cpu_relax() stuff that I have in my tree, for example).
Thanks,
Linus
-
diff -u --recursive /home/torvalds/dri-kernel/Kconfig ./Kconfig
--- /home/torvalds/dri-kernel/Kconfig 2003-04-22 14:30:23.0 -0700
+++ ./Kconfig 2003-08-14 13:05:45.137737925 -0700
@@ -24,10 +24,10 @@
config DRM_GAMMA
tristate 3dlabs GMX 2000
- depends on DRM n
+ depends on DRM
help
- This is the old gamma driver, disabled for now unless somebody
- tells me it actually might work.
+ This is the old gamma driver, please tell me if it might actually
+ work.
config DRM_R128
tristate ATI Rage 128
@@ -49,7 +49,7 @@
config DRM_I810
tristate Intel I810
- depends on DRM AGP
+ depends on DRM AGP AGP_INTEL
help
Choose this option if you have an Intel I810 graphics card. If M is
selected, the module will be called i810. AGP support is required
@@ -57,7 +57,7 @@
config DRM_I830
tristate Intel 830M, 845G, 852GM, 855GM, 865G
- depends on DRM AGP
+ depends on DRM AGP AGP_INTEL
help
Choose this option if you have a system that has Intel 830M, 845G,
852GM, 855GM or 865G integrated graphics. If M is selected, the
@@ -72,3 +72,12 @@
Choose this option if you have a Matrox G200, G400 or G450 graphics
card. If M is selected, the module will be called mga. AGP
support is required for this driver to work.
+
+config DRM_SIS
+ tristate SiS video cards
+ depends on DRM AGP FB_SIS
+ help
+ Choose this option if you have a SiS 630 or compatibel video
+ chipset. If M is selected the module will be called sis. AGP
+ and SiS FB support is required for this driver to work.
+
diff -u --recursive /home/torvalds/dri-kernel/drm_agpsupport.h ./drm_agpsupport.h
--- /home/torvalds/dri-kernel/drm_agpsupport.h2003-07-25 20:04:22.0
-0700
+++ ./drm_agpsupport.h2003-08-14 13:05:45.361704630 -0700
@@ -106,7 +105,8 @@
if ( dev-agp-cant_use_aperture )
return -EINVAL;
#endif
- if ((retcode = drm_agp-acquire())) return retcode;
+ if ((retcode = drm_agp-acquire()))
+ return retcode;
dev-agp-acquired = 1;
return 0;
}
@@ -147,7 +143,8 @@
*/
void DRM(agp_do_release)(void)
{
- if (drm_agp-release) drm_agp-release();
+ if (drm_agp-release)
+ drm_agp-release();
}
/**
@@ -201,7 +198,8 @@
unsigned longpages;
u32 type;
- if (!dev-agp || !dev-agp-acquired) return -EINVAL;
+ if (!dev-agp || !dev-agp-acquired)
+ return -EINVAL;
if (copy_from_user(request, (drm_agp_buffer_t *)arg, sizeof(request)))
return -EFAULT;
if (!(entry = DRM(alloc)(sizeof(*entry), DRM_MEM_AGPLISTS)))
@@ -227,11 +225,12 @@
entry-pages = pages;
entry-prev = NULL;
entry-next = dev-agp-memory;
- if (dev-agp-memory) dev-agp-memory-prev = entry;
+ if (dev-agp-memory)
+ dev-agp-memory-prev = entry;
dev-agp-memory = entry;
request.handle = entry-handle;
-request.physical =
Re: [Dri-devel] Kernel tree CVS merge..
Okay I've applied my piece along with a number of other similiar
whitespace cleanups .. to align with the kernel style ..
Dave.
On Fri, 15 Aug 2003, Dave Airlie wrote:
okay I'm happy to apply the i810 portion and will do so soon, someone else
want to look after the other pieces or should I do them also?
Dave.
On Thu, 14 Aug 2003, Linus Torvalds wrote:
Ok,
I just did another kernel merge to pick up the i810 compatibility bits,
and decided it is time to try to merge back some of the stuff that has
accumulated in the standard kernel and that makes it more painful than
necessary to examine the diffs for differences.
This is mostly whitespace changes (some of it new from Dave Jones, some of
it quite old), and some other minor things: moving some counter and lock
initializations slightly earlier to where the data structure they are in
are allocated and initialized, so that interrupts can't even by mistake
see them partially done.
It also removes the printk() for the AGP version, since that is actually
done by the AGP layer anyway.
I'd appreciate it if all (or even most) of this could find itself back
into the DRI CVS tree, to make it easier to read the code and merge it
(some of the whitespace fixes are literally broken whitespace in the DRI
tree - comments that end up being in strange columns etc).
Apart from moving some initializations around and the aforementioned
printk removal, this should not actually affect semantics at all.
Oh, and the thing will apply with a few offsets, since I edited the patch
to remove stuff that you don't want at this point. My tree doesn't contain
all of the 2.4.x compatibility crud etc.
You can apply (or not apply) everything independently, so feel free to
cherry-pick the patches. I did edit out anything that looked even remotely
like it could cause discussion (ie this does _not_ contain the
cpu_relax() stuff that I have in my tree, for example).
Thanks,
Linus
-
diff -u --recursive /home/torvalds/dri-kernel/Kconfig ./Kconfig
--- /home/torvalds/dri-kernel/Kconfig 2003-04-22 14:30:23.0 -0700
+++ ./Kconfig 2003-08-14 13:05:45.137737925 -0700
@@ -24,10 +24,10 @@
config DRM_GAMMA
tristate 3dlabs GMX 2000
- depends on DRM n
+ depends on DRM
help
- This is the old gamma driver, disabled for now unless somebody
- tells me it actually might work.
+ This is the old gamma driver, please tell me if it might actually
+ work.
config DRM_R128
tristate ATI Rage 128
@@ -49,7 +49,7 @@
config DRM_I810
tristate Intel I810
- depends on DRM AGP
+ depends on DRM AGP AGP_INTEL
help
Choose this option if you have an Intel I810 graphics card. If M is
selected, the module will be called i810. AGP support is required
@@ -57,7 +57,7 @@
config DRM_I830
tristate Intel 830M, 845G, 852GM, 855GM, 865G
- depends on DRM AGP
+ depends on DRM AGP AGP_INTEL
help
Choose this option if you have a system that has Intel 830M, 845G,
852GM, 855GM or 865G integrated graphics. If M is selected, the
@@ -72,3 +72,12 @@
Choose this option if you have a Matrox G200, G400 or G450 graphics
card. If M is selected, the module will be called mga. AGP
support is required for this driver to work.
+
+config DRM_SIS
+ tristate SiS video cards
+ depends on DRM AGP FB_SIS
+ help
+ Choose this option if you have a SiS 630 or compatibel video
+ chipset. If M is selected the module will be called sis. AGP
+ and SiS FB support is required for this driver to work.
+
diff -u --recursive /home/torvalds/dri-kernel/drm_agpsupport.h ./drm_agpsupport.h
--- /home/torvalds/dri-kernel/drm_agpsupport.h 2003-07-25 20:04:22.0
-0700
+++ ./drm_agpsupport.h 2003-08-14 13:05:45.361704630 -0700
@@ -106,7 +105,8 @@
if ( dev-agp-cant_use_aperture )
return -EINVAL;
#endif
- if ((retcode = drm_agp-acquire())) return retcode;
+ if ((retcode = drm_agp-acquire()))
+ return retcode;
dev-agp-acquired = 1;
return 0;
}
@@ -147,7 +143,8 @@
*/
void DRM(agp_do_release)(void)
{
- if (drm_agp-release) drm_agp-release();
+ if (drm_agp-release)
+ drm_agp-release();
}
/**
@@ -201,7 +198,8 @@
unsigned longpages;
u32 type;
- if (!dev-agp || !dev-agp-acquired) return -EINVAL;
+ if (!dev-agp || !dev-agp-acquired)
+ return -EINVAL;
if (copy_from_user(request, (drm_agp_buffer_t *)arg, sizeof(request)))
return -EFAULT;
if (!(entry = DRM(alloc)(sizeof(*entry), DRM_MEM_AGPLISTS)))
@@ -227,11 +225,12 @@
entry-pages = pages;
entry-prev = NULL;
entry-next = dev-agp-memory;
- if (dev-agp
[Dri-devel] texmem changes for sarea and DRM..
In i810_dri.h there is a warning.. /* WARNING: Do not change the SAREA structure without changing the kernel * as well */ for texmem I want to apply the same patch as.. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dri/xc/xc/programs/Xserver/hw/xfree86/drivers/i810/i830_dri.h.diff?r1=1.6r2=1.7 from the i830 .. however this makes a change to the SAREA and I can find no corresponding info in the DRM, is the new TextureRegion structure the same size as the old one and it just works? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] i810 texmem patch..
Okay I've gotten around to updating the i810 driver to texmem interface... http://www.skynet.ie/~airlied/patches/dri/i810_texmem.diff I've a couple of issues perhaps someone can help with: 1. In texstate.c UpdateTexUnit for most drivers (except i830) the following appears: driUpdateTextureLRU( (driTextureObject *) t ); /* XXX: should be locked */ I've taken this approach as well.. but should it be locked? if so how? is the i830 correct should I try to do something similiar? 2. context.c driCalculateMaxTextureLevels from the i830 has a big FIXME beside it about how the intel chips don't pack as well as everyone elses, 3. I 've noticed I've had to increase my Videoram from 16384 (to run my internal application, else I get some all white textures..), so I've probably messed up some allocation somehwere. .should texmem need more RAM? apart from all that it seems to work :-) patch is also missing the sarea change .. it generates a warning... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] High-resolution monitors (T221)
I recently got from ATI Embedded, an eval kit for the M7 and M9 and these cards have dual DVI, granted they don't fit in a PC case too well ( one connector comes out the top of the card :-), but they are only eval boards for embedded designers.. Dave. On Mon, 1 Sep 2003, Alex Deucher wrote: Linus, Some dell OEM radeon cards offered Dual DVI ports and I believe there are some other oems (tyan?) that will be offering Dual DVI cards. the radeon 9000s and newer only have one tdms trandsmitter built in, but an additional external one can be added on to drive the second DVI port. for multi-head 3D on radeon hardware, check out my mergedfb patch: http://bugs.xfree86.org/show_bug.cgi?id=276 Unfortunately, due to a hardware limitation with the scissor registers, you are limited to 2048x2048 for 3D. your framebuffer can be as large as 8192x8192 (limits for the 2D engine). you can use mergedfb at resolutions higher than 2048x2048, however, any 3D windows larger than 2048x2048 will not display. Alex --- Linus Torvalds [EMAIL PROTECTED] wrote: Ok, this is pretty off-topic, but I'm wondering what the status is for open-source support of 3D-capable drivers for such studly monitors as the IBM T221. Yes, it's still expensive as hell, but it isn't nearly as bad as it was a few years ago when it was very limited availability, and cost USD $20k+. These days it is only $9k or so and apparently is actually available in the sales channel. The thing is a 3840x2400 pixel monster, and to drive it at reasonable frequencies you actually need to support a quad DVI setup where it looks basically like four monitors running at 1920x1200. And from what I can gather by googling, the outputs need to be synchronized, so you really need to have a card like the NVidia Quadro4 XGL or similar (ie you can apparetly _not_ drive it with multiple separate video cards). Apparently it also does work with just a single DVI thing (ie reports of it working with the Radeon 8500 at least on macs), probably at a much reduced frequency (ie a single DVI link should be able to drive the thing at something like 10Hz refresh rate - I think the Radeon 8500 supports two links on its single DVI-I interface, so should get up to 20Hz?). The binary-only NVidia driver supports it at the full 40Hz frequency, so I know I can get the thing to work under Linux in case I decide to waste the money on it (or, preferably, convince my employer to do so ;) However, I was wondering if anybody knows of somebody using it with proper opensource drivers.. Or is just otherwise confident for some technical reason that it should work.. I'd want 3D acceleration to work, but I don't care if it ends up being limited to smaller areas (ie if the canvas size has to be limited to 2048x1536 or something, who cares?). Damn, but it's a drool-inducing piece of hardware. Linus __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] i810 texmem patch..
driUpdateTextureLRU( (driTextureObject *) t ); /* XXX: should be locked */ I've taken this approach as well.. but should it be locked? if so how? is the i830 correct should I try to do something similiar? Because this function call modifies the global (ie shared memory) LRU, it should be locked, eg. with LOCK_HARDWARE() macros. Why isn't it? I can't remember - there might not be any good reason. I could try and do something similiar to the i830 where it does the updateLRU in its EmitHwState function.. but am wondering why no other driver has an issue.. or doesn't notice it perhaps.. 2. context.c driCalculateMaxTextureLevels from the i830 has a big FIXME beside it about how the intel chips don't pack as well as everyone elses, 3. I 've noticed I've had to increase my Videoram from 16384 (to run my internal application, else I get some all white textures..), so I've probably messed up some allocation somehwere. .should texmem need more RAM? I've recently had some reports about texture corruption in the i830 driver when using lots of textures. Something is lurking in there, I think. If I use a lot of textures my program should still run but run slower? it shouldn't show white textures.. which is what it does if I lower the videoram to 16MB, I got this before the texmem change as well if I ran with a low VideoRam setting .. So I think I'll check in the changes I have over the next couple of days as I don't think they really make things any worse.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] i810 texmem patch..
If I use a lot of textures my program should still run but run slower? it shouldn't show white textures.. which is what it does if I lower the videoram to 16MB, I got this before the texmem change as well if I ran with a low VideoRam setting .. Yes, it should just run slower. I'm suprised texmem makes a difference -- this is really worth investigating to find out what texmem is doing differently (assuming you have the time to do so). texmem doesn't make a huge difference I can do this with the old codebase as well, I was ignoring it out of ignorance, and just upping my Videoram value.. now I think about it it was broken :-) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] question on i830_wait_ring
Does switching to a VT before suspend and switching back after help any? Dave. On Tue, 2 Sep 2003, Robos wrote: Hi dear developers :) Thanks a lot for your efforts! Now my (newbie) question: my i830 dri powered xserver sometimes restarts after suspend-to-ram (loosing all open windows) with this error message in dmesg: [drm:i830_wait_ring] *ERROR* space: 52232 wanted 131064 [drm:i830_wait_ring] *ERROR* lockup I have this with all versions of the dri modules and the cvs doesn't differ from any release file. From what I gather (newbie programmer) from xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/i830_dma.c does i830_wait_ring try to get space as much as passed as an arg to it. If the ring-head doesn't change anymore the ticks start to sum up till jiffies is larger than 10 (HZ*100) and then it jumps out of this allocation routine, complaining with the above error message. Whats the reason that this happens? What are these 131064? Are these bytes? This xserver restarting is really bad since all open docs, editors and webpages get lost... Thanks in advance Robos -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Sourceforge CVS
dri.freedesktop.org sound good? I love the idea of moving to freedesktop.org right now to deal with the anonymous cvs issue, provide cvsup, and probably a more responsive set of admins. Is there consensus on this? I'm all for it, if there's a solution for anonymous CVS. I'm with this as well.. I'm getting well pissed at SF these days :-), Havoc, your comment on pserver being like telnet isn't really applicable, anon only pserver is as secure as any anon only service, I wouldn't even think about using non-anon pserver but I don't think DRI will ever need such a thing.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: CVS Update: xc (branch: trunk)
On which server are you doing these commits? From the looks of it, you're doing them on the SourceForge server. I thought we weren't going to do that anymore. Is the freedesktop server ready for prime-time (i.e., does it have the latest CVS ,v files)? I guess it doesn't matter at the moment, as Michel tells me that Eric can't get the latest repository tarball from SF. But now when he does that he'll get the merged stuff too. yeah sf.net had yet another CVS hickup and lost all the tarballs, it could be a while before they are made available agani.. I think we will need to draw a line in the sand at some point, and pause development for probably a week, so no-one commits anything anywhere, wait about 48 hrs (at least at a guess about 4 days) until the tarball catches up with the frozen CVS, grab tarball, move to freedesktop, start developing again.. afaik the tarballs are generated from the backup server making them about as useful as Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] cvs tarball from sf.net..
Okay there is one in my a/c on freedesktop.org with Sep 12 00:20 on it, but I'm sure it is from the backup server not the primary.. so it is probably missing 24 hrs of commits.. the history file in CVSROOT is probably the best place to start... god knows how long it will be until sf update the tarrball again.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Kernel back-merge ...
I applied the radeon.h and the Kconfig patches (redone, since whitespace got mangled in the email). I've posted a more agressive whitespace cleanup of i810_dma.c. I don't want to commit such a big whitespace diff without the i810 maintainer's approval. http://people.freebsd.org/~anholt/dri/files/i810-whitespace.diff Well it looks fine to me... I'd prefer someone to else to patch it, as it was me who messed up some of the merging last time (*must reconfigure editor properly.. and maybe run Lindent*)... If Linus thinks your patch goes far enough for him.. Dave. Keith, what's the status of the new i830 stuff? Is it going to be merged to trunk soon, or should we put things in trunk in the meantime (I'm thinking of this i830 fix, the BSD fixes you've made)? -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / [EMAIL PROTECTED] pam_smb / Linux DECstation / Linux VAX / ILUG person --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] CVS merge problem solved + suggestion for cvs policy
Hmm. These problems only arise because of the way the merge was done? Why not just document the right way to do the merge? I'd agree with Keith the proper way to merge needs documenting, CVS vendor import is what is needed, the XFree CVS is vendor imported into our DRI tree, the changes from the last XFree merge are then merged onto the trunk for files that we have changed... I recently (with some help) manually cleaned up some Linux-VAX development CVS trees that had been hand merged not using vendor stuff, it just takes judicious use of the cvs admin -b command... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] texture problem with i810
I've noticed an issue with the i810 chipset that I'm wondering if anyone can shed light on it.. I've it narrowed down to the fact that the texture upload code never gets called for my texture, so the card doesn't know what to display, hence it displays white space. To repeat - get an i81x (may be an issue on i830 also.. ) get texture demo from Mesa-5.0 take wrs_logo.rgb from Mesa-5.0 and use xv to make it 1024x864 and save it, convert to a pnm, run texture with the image file... Now if you've got your VideoRAM setting set to 16384 you get white space, if you set the VideoRAM setting to 18000 the image displays... So I know 16384 is plenty of VideoRAM so why the whitespace? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] valgrinding DRI..
I'm trying to valgrind my application and in the process DRI :-), However I can't get over the Mesa MMX checks, is there any env variable I can set so Mesa doesn't do all the stuff that requires SIGFPE and I can force it to use a certain type of instruction set? I've been just setting ALWAYS_INDIRECT for now but that doesn't find any issues in my DRI driver (not that I think there are any but it never hurts to look)... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- 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 the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] r100 and TEXTURE_RECTANGLE_NV
Does the r100 support the rectangle textures extension? or is the driver borked? I have a CVS from a week or so ago and texrect seems to now function correctly... is this a chip limitation or driver bug? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] i810/5 and rectangular textures..
in the i810/5 manual I have, it mentions bit 31 of dword 2 the MAP_INFO register allows non power of dimensions, and bit 14 of MAP_COORD_SETS is whether the set is normalized or not .. does anyone know if this is possible? I've hacked together NV_texture_rectangle support but it doesn't seem to work (go figure :-) anyway my initial hack of patch is at http://freedesktop.org/~airlied/i810_rect_tex.diff Anyone any ideas, it's not really important, my prime concern is now the radeon m7, but it would be nice to have support for the i810 in my software.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] GL_MESA_ycbcr_texture and GL_NVX_ycrcb
Hi all, I've just implemented output for ffmpeg to opengl using rectangular ycbcr textures, and the speed is quite good (compared to non-ycbcr mipmapped textures :-), but now I've noticed of course I can't use it on the NVIDIA (*evil*) closed source drivers... (a couple of developers using NV cards...) I don't mind that much and maybe NVIDIA will pickup the MESA extension at some stage, but I've spotted an extension called GL_NVX_ycrcb in my extension list and I wonder has anyone here heard of it? I know go ask NVIDIA and I will just thought someone on this list might have seen or heard of it (google turns up nought).. Thanks, Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] (no subject)
Well I've traced this a bit, an operation appears to be hanging the chipset, Keith, maybe you can tell me, in i830_span.c you no longer have a HW_LOCK or HW_UNLOCK defined for the i830 has something happened elsewhere that makes these unnecessary, what blender seems to be doing is loading up a string of glBitmaps to create its frontend, and after a bunch of these a HW_LOCK call from i810WriteRGBAPixels_565 calls DMAFinish which doesn't seem to have finished for some reason from the previous one, any ideas why this might happen? Dave. just happened to have blender here on my system, ran it on my test box boom .. kernel goes into a frenzy of (see below), machine stops responding to network and everything, kernel is alive (sysrq works for me ) I'm running FC1 - their 2.4.22-1.2115.nptl kernel with top of CVS i810 stuff... I'll take a look but I'm not exactly fully with the whole 3d graphics card and DRI mysteries yet :-) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] i810 breakage in past few days..
the i810 got broken by the texture changes over the last few days, the imesa-i810Screen pointer wasn't setup before the call to mesa_create_context and it in turn called i810SetTexFilter which used IS_I815 which used i810Screen, I've checked in a fix (I've just moved all the pointer assignments before the function calls ..) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] i810 bug causes a wierd DRM bug ..
There is something wrong with the i810 driver at the moment, when I just run an X server, run anything that exits, when the X server recycles something is being kept allocated across the recycle and a drmAgpBind fails on the server coming back up, however when that fails the clean up calls DRICloseScreen which does an drmUnlock with pDRIPriv-myContext which is 0 which causes the kernel to throw [drm:i810_unlock] *ERROR* Process 1469 using kernel context 0 error up .. pDRIPriv-myContext isn't actually set until DRIFinishScreenInit so there is no way to unlock the context... should dri.c have a if (pDRIPriv-myContext0) check before unlocking the context? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] i810 bug causes a wierd DRM bug ..
btw the i810 bug is triggered by setting VideoRam to a big number (65536 in my case makes it fail on the recycle...) Dave. On Mon, 2 Feb 2004, Dave Airlie wrote: There is something wrong with the i810 driver at the moment, when I just run an X server, run anything that exits, when the X server recycles something is being kept allocated across the recycle and a drmAgpBind fails on the server coming back up, however when that fails the clean up calls DRICloseScreen which does an drmUnlock with pDRIPriv-myContext which is 0 which causes the kernel to throw [drm:i810_unlock] *ERROR* Process 1469 using kernel context 0 error up .. pDRIPriv-myContext isn't actually set until DRIFinishScreenInit so there is no way to unlock the context... should dri.c have a if (pDRIPriv-myContext0) check before unlocking the context? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] r200 new revolutionary lighting
I would, but I can't. Maybe Eric can do it, but I think there should be others with Eric's access ability so these others can do it too. I think contacting keithp if Eric is away... Dave. Alan. --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] about the i810 card and crashing
can you send me also the i810 line from your dmesg? dmesg | grep i810 should do it .. sarg has a fairly old i810 driver, something must have broken since then .. Dave. OpenGL renderer string: Mesa DRI I810 20010321 OpenGL version string: 1.2 Mesa 3.4.2 -- Marko Dimiskovski --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] about the i810 card and crashing
Just to follwup I can run blender with some artefacts but nothing serious on OpenGL renderer string: Mesa DRI I810 20020221 OpenGL version string: 1.2 Mesa 4.0.4 which is XFree 4.3.0 from Fedora Core One, also using the latest DRM [drm] Initialized i810 1.4.0 20030605 on minor 0: Intel i815 GMCH So something has regressed since XF4.3 in the DRI driver, if I can afford the time I'll see what I can dig out .. I think 4.4 will have this regression.. Dave. OpenGL renderer string: Mesa DRI I810 20010321 OpenGL version string: 1.2 Mesa 3.4.2 -- Marko Dimiskovski --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] fix for i810 issues of late..
Since Keith's tnl_dd_dmatmp.h patches on the 11 Dec last year, the poor i810 has been seriously fubar, I've just gotten time to look at it now (well I've been staring at it on and off for weeks with a blank) The fix is up at http://freedesktop.org/~airlied/i810_render_fix.diff I've taken it from the i830 code, and I've modified scale_prim so that the 3rd element is also a fallback case, Keith can you tell me if my numbers are correct for the i810? or at least where you got the numbers for the i830... if no major objections I'll apply it soon, I'd like to just figure out the values for scale_prim are correct... fixes, blender and tri sample program among others... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] about the i810 card and crashing
Just to follwup I can run blender with some artefacts but nothing serious on OpenGL renderer string: Mesa DRI I810 20020221 OpenGL version string: 1.2 Mesa 4.0.4 which is XFree 4.3.0 from Fedora Core One, also using the latest DRM [drm] Initialized i810 1.4.0 20030605 on minor 0: Intel i815 GMCH So something has regressed since XF4.3 in the DRI driver, if I can afford the time I'll see what I can dig out .. I think 4.4 will have this regression.. Okay the 4.4 snapshot from ftp://ftp.xfree86.org/pub/XFree86/snapshots/4.3.99.902 is okay, so the merge to the Mesa tree seems to be what broke this and also the Mesa sample tri is broken badly as well... OpenGL renderer string: Mesa DRI I810 20021125 OpenGL version string: 1.2 Mesa 5.0.2 again running the latest DRM.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] manytex on i8xx systems..
Can someone run ./manytex -randomsize -mipmap from the Mesa progs/tests on an i830 or above with the latest DRI and tell me does it look the same as LIBGL_ALWAYS_INDIRECT=y case? Some of the textures are corrupting on the i810 and I want to see if it is just another case where something got fixed in the i830 Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] libGL error: unable to load DRM
however, when I ran glxgears, I get a libGL error saying it couldn't load the drm and it was reverting to indirect rendering :/ do you have your board agp module installed? and insmodded? this in't done automatically since 2.6 kernels .. for Intel you need modprobe intel-agp somewhere.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] fix for i810 issues of late..
This is GL_LINE_LOOP? That makes sense. Interesting - this should only be a heuristic to choose the fastest path, not have any correctness value. Correctness should be ensured by i810_validate_render, from t_dd_dmatmp.h. Can you try find out what's going wrong with that? okay I've figured this out a bit further, the bug is in i810_render_line_loop_verts from t_dd_dmatmp.h choose_render returns GL_FALSE for these because there is no value in hw_prim[2], however validate_render returns GL_TRUE as it just checks whether the hardware has LINE_STRIPS not LINE_LOOP, and then when it uses the i810_render_line_loop_verts function it locks the card up ... I see the code uses LINE_STRIPS to LINE_LOOP but it seems to be in-correct, well it locks the card, I've no idea if it is correct or not!! Dave. p.s. I've checked out the latest version of t_dd_dmatmp.h in case you were going to ask :-) -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] fix for i810 issues of late..
I see the code uses LINE_STRIPS to LINE_LOOP but it seems to be in-correct, well it locks the card, I've no idea if it is correct or not!! Hi Keith, To my untrained eye it looks like the test at the start of the render_line_loop_verts is incorrect, but maybe I am just covering up the problem, with this change blender and tri work without my previous patch... but maybe I'm just moving the issue :-) patch below.. Dave. Index: t_dd_dmatmp.h === RCS file: /cvs/mesa/Mesa/src/mesa/tnl_dd/t_dd_dmatmp.h,v retrieving revision 1.5 diff -u -r1.5 t_dd_dmatmp.h --- t_dd_dmatmp.h 4 Feb 2004 16:59:30 - 1.5 +++ t_dd_dmatmp.h 5 Feb 2004 04:53:25 - @@ -216,9 +216,9 @@ INIT( GL_LINE_STRIP ); if (flags PRIM_BEGIN) -j = start; - else j = start + 1; + else +j = start; /* Ensure last vertex won't wrap buffers: */ -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] fix for i810 issues of late..
Hi Keith, To my untrained eye it looks like the test at the start of the render_line_loop_verts is incorrect, but maybe I am just covering up the problem, with this change blender and tri work without my previous patch... but maybe I'm just moving the issue :-) patch below.. apologies to the list and Keith for the noise, but that patch was bogus, still digging it out, it must be an out by one somewhere but I can't see where it is happening ... I'm learning way more about Mesa internals that I ever cared to !!! I think I'll give up for today and go at it again later, perhaps the i810 just can't do this in hardware and I need to fallback or perhaps the number of vertices being output is out by one .. who knows :-) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] fix for i810 issues of late..
I think I'll give up for today and go at it again later, perhaps the i810 just can't do this in hardware and I need to fallback or perhaps the number of vertices being output is out by one .. who knows :-) Okay I found it and checked in the fixes for it, the macro expansion was catching the code on ALLOC_VERTS(nr+1) for i810,i830 and mga, these all did nr * x type things, instead of (nr) * x in their ALLOC_VERTS macro expansions.. Funny enough I now know how the mesa vertex code works very well!!! I'll be hiding for a while I think.. my brain is fried... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] mach64 and new tree
I noticed it came up during the IRC meeting this week about moving the mach64 up to the top of tree, So how should this be done in terms of CVS, the mach64 driver as is insecure, so I'd rather not put into an official tree until those issues are sorted out, I know Jose has some ideas on these and I'll see if I can track him down at some point, but for now I'd like to bring the current branch up to the top of tree at least, So should I use the mesa tip and start a new mach64 branch on the DRI tree or should I make a branch on both trees? oh yeah I'm unsure who brought it up on IRC so if you are on the list speak up :-) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64 and new tree
track him down at some point, but for now I'd like to bring the current branch up to the top of tree at least, So should I use the mesa tip and start a new mach64 branch on the DRI tree or should I make a branch on both trees? oh yeah I'm unsure who brought it up on IRC so if you are on the list speak up :-) I've just brought the mesa driver from mach64-0-0-6 so it compiles in the top of the Mesa tree (I doubt it works, but building is a good start) so if someone tells me where to put it I'll commit it for a start point tomorrow (I'm GMT+10, should probably use .au a/c :-) I'll work on the XFree bits and the DRM should be similiar enough soon.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64 and new tree
tomorrow (I'm GMT+10, should probably use .au a/c :-) I'll work on the XFree bits and the DRM should be similiar enough soon.. I think it should be fine to go in at Mesa head. Okay what about the DRI tree bits? DRM and changes to ATI driver?, should I go with mach64-0-0-7 or should I just make sure the ati bits work and not add mach64 to the host.def (I can see that messing up the snapshots a bit though), or maybe I just add a big huge warning to the DRM module and the X startup stating the mach64 DRM is inherently insecure and shouldn't be used on multi-user systems? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] mach64-0-0-7-branch...
Okay everything should be checked in and building, it doesn't work yet though :-) I'll hopefully get time over the next few days to hack on it again, I'm in the middle of moving apartments and work only pay me the odd hack to i810/radeon stuff, the mach64 is personal (as my laptop has it), if I get a monitor at some stage I might even get dual-head working!! Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] mach64-0-0-7-branch status..
Okay I've checked in the DRM and Xserver changes to the above branch, I've added the PCI ids I think are correct for the chip variations, I'll hopefully get around to testing it in the next couple of days, (just have to drag out the laptop :-) If anyone else has a chance feel free to give it a go .. I'm not sure the Mesa driver works yet!! Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64-0-0-7-branch status
It's great that you are picking this up. It's been on my todo list for a long while but free time is nonexistant for me these days (full time grad student + half time research assistant = - half time DRI developer?!) well a few things came together, I got specs at work for the rage pro that I found we had thought about using in a previous product, and I wanted a couple of things in the later DRI to work on my laptop, (and Aussie TV turns to worse muck during the summer :-) I actually have a near complete texmem conversion that's been gathering dust for a while. I'll try to clean it up and send a patch in the next few days. if you can't no worries, texmem conversion for i810 was the first conversion I did.. :-), I'll have to leave it alone for a few days and see if anyone can find any issues with it .. (I just checked in another load of fixes for specular and color that I had wrong ...), I'm gonna dig around at work and see if I can get a PCI or AGP M64 card, there might be one in a corner somewhere :-) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] mach64-0-0-7-branch status
Okay the last few fixes make tuxracer and glxgears work again, so the new branch should be as useable as the old one, I think there are still a few cleanups in the native vertex code (using macros for a few things), and then a texmem converison might be in order. But it's good enough for me to get on with some real work on my laptop :-) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64-0-0-7-branch status
While I'm at it (see driinterface-0-0-3-branch mails) I could update the snapshot scripts to build mach64-0-0-7-branch snapshots. please do it, I'm sure a bit more testing would help a lot ... Thanks, Dave. Dave. Felix --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64 and new tree
So should we just work on getting everything running on newtree then and not worry about the security issues for now? Sounds good to me, I'll look into disabling DMA by default, if we have the option we are okay, my only issue is though should there be something in the DRM that it affects? I can't see how XF86Config could make it safe, if I have a DRM that allows it I can access it from userspace process without DRI or XFree86... I think the branch now works as well as the older branch the last couple of commits I did last night fixed up the issues with specular/fog stuff that I messed up a bit.. we are now using packed vertices, So texmem changes, and a bit more testing, my issue is I can't keep both trees built on my laptop :-), so I'm hoping I don't need to change the old tree for debugging to track down anything I break!!.. And Jose if you have any work done on the DRM interface change in any state or any ideas, could you drop it somewhere so I can start looking at it maybe.. I don't care if it does anything I'm more trying to get the ideas you were proposing than a working DRM ... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] mach64-0-0-7 branch illness and snapshots..
Okay I wasn't as complete as I thought, the Mesa and the DRM I was using were from the branch but I never updated my 2d driver, it was still the old branch... so then I noticed something else which might cause problems with the snapshots When I updated and using the XFree86 from the snapshot directory, I was missing an I2C symbol, the ati driver in DRI CVS seems to need a newer version of libi2c.a, mine was from Fedora Core 1... The 2d driver builds now but 3d seems to crap it out .. it'll be a day or two until I figure it out .. I might need to get a serial console together.. (or a network).. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64-0-0-7 branch illness and snapshots..
When I updated and using the XFree86 from the snapshot directory, I was missing an I2C symbol, the ati driver in DRI CVS seems to need a newer version of libi2c.a, mine was from Fedora Core 1... The 2d driver builds now but 3d seems to crap it out .. it'll be a day or two until I figure it out .. I might need to get a serial console together.. (or a network).. Okay the 2D driver is now in a lot better state and should work fine ... the libi2c.a issue is still there I think.. Dave. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64-0-0-7 branch illness and snapshots..
-X starts up fine now, window manager comes up, etc. -xvinfo reports xv working, playing mpeg with mplayer confirms this. -glxinfo reports correct info -glxgears locks up. Rest of X is locked, but mouse can be moved around. I can ssh in, but can't seem to kill the X server. A reboot is required to get the screen working again. wierd is their anything in dmesg? send me a copy of it .. I've just had a game of tuxracer and it works great for me .. I've also started two glxgears side by side ... and exited them.. does gears lock up after you try to exit it or straight away? if it is on exit, I'd re-build the tree and confirm yuou have the latest 2d driver as that is what was happening me before about 8 hours ago.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64-0-0-7 branch illness and snapshots..
As for the glxgears thing, I got some output from it when I ran it with gdb from an ssh session: glxgears: vblank.c:338: driWaitForVBlank: Assertion `interval != (unsigned)-1' failed. try updating from CVS both trees, I fixed this I just can't remember which tree it went into :-) I think it was the Mesa one, I'll take a look at the DMA failure case later on .. when I'm more with awake On a side note, what kind of stuff should I put in my host.def to build a nice static debuging server? I googled for this and found a few things, but they I change the XF86Drivers line to just ati, the DriDrivers line to just mach64, define GlxBuiltInMach64 to YES and comment out DoLoadableServer line and I think that works.. I've also used the gdb mentioned in the Wiki I think to debug the normal server ... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] xfree crash when switching to console (Mach64)
I added daenzer's package repository to my sources.list ( http://people.debian.org/~daenzer/dri-mach64-unstable/ ) and installed the mach64 patched packages to enable DRI support and XV. The drm-modules didn't compile (due i think to 2.6 kernel), so i patched it again with John Flinchbaugh's patch ( http://www.hjsoft.com/blog/link/Mach64_DRI_on_Linux_2.6 ). You might want to try the snapshots from the DRI site, but I currentyl see the crash as ewll, especially if while gdm is starting I hit C-A-F1, X restarts, I currently don't have a network connection or serial terminal for my laptop at home to debug thr X server to see what happens, I'm sure it is some hardware state not getting saved somewhere.. Hopefully in the next week or two I'll get a chance to either bring laptop to work or hook something up at home .. Dave. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64 dri on freebsd 5.2
What is the status of mach64 dri support on freebsd 5.2 ? nobody has tested it for a while, so I say it suffers from bitrot... mach64-0-0-7 is the DRI branch to go with, and Mesa head, the code should all be there, just needing some updates for FreeBSD 5.2, I'll look into it over the next while (need to sleep for a day or two :-) Dave. Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] mach64 dri on freebsd 5.2
Thank you! It dies in xc/programs/Xserver/GL/mesa/X/xf86glx.c : xf86glx.c: In function `__MESA_setVisualConfigs': xf86glx.c:481: error: `kernel8' undeclared (first use in this function) xf86glx.c:481: error: (Each undeclared identifier is reported only once xf86glx.c:481: error: for each function it appears in.) xf86glx.c:482: error: `DitherValues' undeclared (first use in this function) If I remove those two variables, the build continues past that point. I don't yet know if it completes because my laptop takes a long time to build X. I've moved the fix over the from the trunk so it should work, it compies on Linux for me .. can't test it at work though.. Dave. thanks again. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Building DRM for 2.6.3. And mach64 randr.
I was building mach64 drm for 2.6.3. I had the worst time convincing Makefile.linux and inturn Makefile.kernel that it was not lessthan25 and lessthan2552. I finaly gave up once I saw I had to gointo all the .h and .c files and add #defines there as well. Also I don't have a mach64 pro I'm running 2.6.3 on my laptop with mach64 from mach64-0-0-7-branch of DRI CVS, compiles and seems to run okay, you certainly shouldn't need to edit anything... I also have the same chipset as you ... all the mach64 really does is triangle and texturing, not much else.. so it depends on what you run on it to decide if it goes faster.. tuxracer certainly does :-) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Mesa Linux solo and r100..
Hi, I've just tried getting a solo Mesa working on 2.4.25, latest DRM from DRI CVS and top of tree Mesa on r100, my framebuffer console comes up, but when I start the server the screen is corrupted, when I run the test app I can see the garbage on screen change so it looks close to working, Does anyone have this working? on any card, I might try porting the i810 or mach64 to Solo over the next couple of days as an additional test but I'd like to see a working one first.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mesa Linux solo and r100..
Hi, I've just tried getting a solo Mesa working on 2.4.25, latest DRM from DRI CVS and top of tree Mesa on r100, I got it working on 2.6.3 in the end, there must be some issue with the fb in 2.4.25 or something .. I'll start looking into it soon.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Mach64 DRM module problems
Send your cards PCI ids to the list, Mike what card have you the DRM shouldn't load for any card that doesn't have the triangle engine really.. Dave. On Thu, 11 Mar 2004, Mike Mestnik wrote: At first I thought it just might have been my system. In debuging the problem I found ought that my chip dose not have triangle setup. It's not likely that it will be supported by DRI. However the 2d driver gave me xrendr support, this will help with TV out for me. As for the kmod if you post the errors to [EMAIL PROTECTED] some one there might be able to help. --- Mikko Rauhala [EMAIL PROTECTED] wrote: Hi Just noticed that you were having about the same problems as me compiling the mach64 drm module for 2.6.3. I was just wondering if you've made any progress on it? I tried both the unofficial deb linked to by dri.sourceforge.net and the mach64-0-0-7-branch module directory, no go both ways. Thanks. -- Mikko Rauhala - [EMAIL PROTECTED] - URL:http://www.iki.fi/mjr/ Transhumanist - WTA member - URL:http://www.transhumanism.org/ Singularitarian - SIAI supporter - URL:http://www.singinst.org/ ATTACHMENT part 2 application/pgp-signature name=signature.asc __ Do you Yahoo!? Yahoo! Search - Find what you[92]re looking for faster http://search.yahoo.com --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: [Mesa3d-dev] removing redundant SAREA/IOCTL defines
It shouldn't be very hard to do this for: sis, tdfx, i810, i830, savage, gamma so are we making the Mesa tree the DRM master repo as opposed to the DRI tree? I don't remember much discussion on this either way, What about? mach64, unichrome Where are the DRM drivers for these two? mach64 is in mach64-0-0-7-branch on DRI tree, I'd prefer not to bring it in yet, I'm meant to be doing some work on it at some stage .. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Mach64 DRM module problems
from my laptop 01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) (prog-if 00 [VGA]) looks the same to me and mine works :-) so yours should ... On Fri, 12 Mar 2004, Mike Mestnik wrote: I don't know, if it loads or not, I stoped trying when I found ought that only Rage pro was supported. However the 2d driver workes fine. 01:00.0 Class 0300: 1002:4c4d (rev 64) 01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) (prog-if 00 [VGA]) Subsystem: Dell Computer Corporation: Unknown device 00bc Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (2000ns min), Cache Line Size: 0x08 (32 bytes) Interrupt: pin A routed to IRQ 11 Region 0: Memory at fd00 (32-bit, non-prefetchable) [size=16M] Region 1: I/O ports at ec00 [size=256] Region 2: Memory at fcfff000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at unassigned [disabled] [size=128K] Capabilities: [50] AGP version 1.0 Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=none Capabilities: [5c] Power Management version 1 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- --- Dave Airlie [EMAIL PROTECTED] wrote: Send your cards PCI ids to the list, Mike what card have you the DRM shouldn't load for any card that doesn't have the triangle engine really.. Dave. On Thu, 11 Mar 2004, Mike Mestnik wrote: At first I thought it just might have been my system. In debuging the problem I found ought that my chip dose not have triangle setup. It's not likely that it will be supported by DRI. However the 2d driver gave me xrendr support, this will help with TV out for me. As for the kmod if you post the errors to [EMAIL PROTECTED] some one there might be able to help. --- Mikko Rauhala [EMAIL PROTECTED] wrote: Hi Just noticed that you were having about the same problems as me compiling the mach64 drm module for 2.6.3. I was just wondering if you've made any progress on it? I tried both the unofficial deb linked to by dri.sourceforge.net and the mach64-0-0-7-branch module directory, no go both ways. Thanks. -- Mikko Rauhala - [EMAIL PROTECTED] - URL:http://www.iki.fi/mjr/ Transhumanist - WTA member - URL:http://www.transhumanism.org/ Singularitarian - SIAI supporter - URL:http://www.singinst.org/ ATTACHMENT part 2 application/pgp-signature name=signature.asc __ Do you Yahoo!? Yahoo! Search - Find what you[92]re looking for faster http://search.yahoo.com --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person __ Do you Yahoo!? Yahoo! Search - Find what you[92]re looking for faster http://search.yahoo.com -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] miniglx and DDX version checking
The current miniglx fakes up some DDX version numbers but these only work for the radeon drivers, (4.0) is used, but the i810 drivers is only on version 1.0, Is there any need for this to be checked at all should the _SOLO defines in utils.c:driCheckDriDdxDrmVersions be extended to cover the DDX check? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] mach64 should build again..
I've fixed up the mach64-0-0-7-branch it should build and run again.. haven't tested it yet, no enough disk space on my laptop.. tomorrow hopefully.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Switching dri over to new drm tree
This was installed from a snapshot. Snapshots up to March 2 worked, anything after that did not have working direct rendering. But since the snaps are generated from the head... I've seen this error posted here before but I haven't seen a resolution, maybe I missed it. Ian, does this look at all like it could be related to your libGL, etc. changes? I'll try and test this tomorrow at work.. have been off doing some non graphics works... Dave. Keith --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] mach64 and USE_NEW_INTERFACE
I've checked in the changes for the mach64 to use the new interface, I haven't turned it on as I had to change some stuff I'm unsure off... I've had to set modes-drawableType = GLX_WINDOW_BIT | GLX_PIXMAP_BIT; the r200 just had the GLX_WINDOW_BIT .. Apart from that, 24-bit needs looking at.. not sure I've enough RAM for it :-) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Switching dri over to new drm tree
anything after that did not have working direct rendering. But since the snaps are generated from the head... I've seen this error posted here before but I haven't seen a resolution, maybe I missed it. Ian, does this look at all like it could be related to your libGL, etc. changes? yup if I just build HEAD and install it it works fine.. so it looks like a snapshot + older libGL issue.. I'm not really setup for testing that sorta thing here... I've always been a build HEAD and install :-) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] initial DRM conversion script..
I've thrown together a really simple script to make the DRM tree into a Linux kernel type setup.. its in the DRM tree under scripts/create_lk_drm.sh usage is from the top of of the DRM and you provide the output dir and either 2.4 or 2.6 to produce the correct type of tree.. I'm sure there are many things that could be done to this, feel free :-) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: DRM reorganization
Hi, The patch you've been carrying for a while has a number of bogons, like duplicating pci.ids inside the radeon driver for no good reason. Davej can you expand on this a bit, Linus was involved in the discussion on this way back when.. thread at: http://marc.theaimsgroup.com/?t=10661828131r=2w=2 it's not just a re-creation of pci ids, the DRM drivers now know what cards they can work on, the only think I can think of perhaps is removing the strings and getting them from the pci.ids... In the past most of the merges were done by Linus. I don't recall seeing a 'dri maintainer' per se ever sending resync patches. Linus merged during 2.5 and maybe that has gotten us a bit relaxed :-), Eric Anholt may be the best person on getting the DRM in shape but he is away, I'm not sure if I can step up either, maybe I can at least update the patch Andrew has... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
