[Bug 4150] r300 cairo with glitz backend locks X
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4150 --- Additional Comments From [EMAIL PROTECTED] 2005-11-08 11:22 --- (In reply to comment #16) (From update of attachment 2940 [edit]) wrong file?! It seems to me like this would be the infamous r300 lock case. Im going to disable r300 support to avoid confusion with stable and not stable chips. As far as the bitblt part goes, r300_cmdbuf.c needs to be converted to pass along drm_file_t so that we can call radeon_check_and_fixup_packet3(...). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: CVS Update: drm (branch: trunk)
On Tue, 2005-11-08 at 12:25 -0800, Eric Anholt wrote:
CVSROOT: /cvs/dri
Module name: drm
Repository: drm/shared-core/
Changes by: [EMAIL PROTECTED] 05/11/08 12:25:00
Log message:
Initial port of savage to FreeBSD for the AGP and !ShadowStatus case. Adds
drm_mtrr_{add,del} for handling the MTRR setup. Still has a LOR issue with
DRM_VERIFYAREA_READ/DRM_COPY_FROM_USER_UNCHECKED in savage_bci.c -- this
won't
^^
that should read savage_state.c. Also, for those playing at home, LOR
means lock order reversal -- one of a few different ways of getting
the fine-grained locking in FreeBSD wrong.
work with the fine-grained locking in use, and just doing a single copyin
to a
temporary will probably work fine. Also note that the module leaks
approximately 4 kb on unload.
--
Eric Anholt [EMAIL PROTECTED]
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
Looking for i915 build info
I am looking at adding vblank synchronization support to the i915 driver. I have a few questions on how all of the pieces fit together and where the source code comes from. From my understanding, the snapshots such as i915-20051107-linux.i386 contain source code that is built to update the kernel DRM modules (i915.ko and drm.ko). The snapshot also contains binary files (i915_dri.so and i810_drv.o) that are copied over the existing X modules. My question is this. Where is the source code that builds the new X modules? I found the code that builds the original modules in the X source but I can't find the source for the updated modules. I am very new to DRM/DRI so I may be missing something but it seems to me that adding vblank synchronization support will require modifications to both the DRM and DRI parts of the equation. Can somebody enlighten me? Any information is appreciated. Thanks, Dave Kavanagh --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Looking for i915 build info
Dave Kavanagh wrote: I am looking at adding vblank synchronization support to the i915 driver. I have a few questions on how all of the pieces fit together and where the source code comes from. From my understanding, the snapshots such as i915-20051107-linux.i386 contain source code that is built to update the kernel DRM modules (i915.ko and drm.ko). The snapshot also contains binary files (i915_dri.so and i810_drv.o) that are copied over the existing X modules. My question is this. Where is the source code that builds the new X modules? I found the code that builds the original modules in the X source but I can't find the source for the updated modules. I am very new to DRM/DRI so I may be missing something but it seems to me that adding vblank synchronization support will require modifications to both the DRM and DRI parts of the equation. Can somebody enlighten me? Any information is appreciated. For the DRM modules, you are better off looking at the DRM CVS tree. The clientside 3d module, i915_dri.so, is built from Mesa CVS, while the Device-Dependent X (DDX) driver, i810_drv.o, is built from X.org cvs. Believe me, it used to be even more complicated... Keith --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Looking for i915 build info
Am Dienstag, den 08.11.2005, 17:05 -0400 schrieb Dave Kavanagh: I am looking at adding vblank synchronization support to the i915 driver. I have a few questions on how all of the pieces fit together and where the source code comes from. From my understanding, the snapshots such as i915-20051107-linux.i386 contain source code that is built to update the kernel DRM modules (i915.ko and drm.ko). The snapshot also contains binary files (i915_dri.so and i810_drv.o) that are copied over the existing X modules. i810_drv.so in the latest version. ;-) We're using the DLLoader now. My question is this. Where is the source code that builds the new X modules? I found the code that builds the original modules in the X source but I can't find the source for the updated modules. The DDX (2D) driver modules are built from Xorg CVS HEAD. The DRI (3D) driver modules are built from Mesa CVS HEAD. I am very new to DRM/DRI so I may be missing something but it seems to me that adding vblank synchronization support will require modifications to both the DRM and DRI parts of the equation. I don't know what the status of this is in the i915 driver. But in general you are right. Both DRM and DRI need support for vblank synchronization, for example by using IRQs. Can somebody enlighten me? Any information is appreciated. Thanks, Dave Kavanagh Regards, Felix -- | Felix Kühling [EMAIL PROTECTED] http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Radeon detected Memory!
I don't know if you remember about radeon driver doesn't detect more than 128 MB of memory, Michel Daenzer as said that max driver capabilitie was 128Mb. So i have this patch to warn that driver has detected correct amount of memory but only using 128MB. like Roland has sugested. I've implemented a more complex if expression, that only allow memory override to lower values of 128MB. I don't know if my though's were correct, or if my implementation was correct. So before merge the patch give a quick look. P.S:I don't know of i'm sending this patch to the right place Pedro Maia radeon_driver.diff Description: radeon_driver.diff
