Re: adding dri support
Rogelio Serrano schrieb: I have reinvented the wheel and now have standalone opengl on framebuffer by hacking egl support into tinygl. I have also copied over code from mesa and it looks like Ihave reinvented mesa too. Which graphics card has the most open specs so i could start reinventing the wheel again and write a 3d driver from scratch? The SiS 530 is fully documented, but it's a bit outdated and AFAIK there's no 3D driver for it yet. AFAIK The Vodoo cards are fully documented and the driver is so bad it could need a rewrite. Philipp --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: adding dri support
On Tue, 31 Jan 2006 12:44:24 +0800 Rogelio Serrano [EMAIL PROTECTED] wrote: I have reinvented the wheel and now have standalone opengl on framebuffer by hacking egl support into tinygl. I have also copied over code from mesa and it looks like Ihave reinvented mesa too. Would you put this code in a CVS in sourceforge or as a tar/gz somewhere ? I would really like to have a look at it. Thanks khaqq --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: adding dri support
On Maw, 2006-01-31 at 10:24 +0100, Philipp Klaus Krause wrote: The SiS 530 is fully documented, but it's a bit outdated and AFAIK there's no 3D driver for it yet. AFAIK The Vodoo cards are fully documented and the driver is so bad it could need a rewrite. The Voodoo 3 and higher need a lot of support above the DRI layer fixing to get some features like SLI working at all. Right now the 2D engines in X don't support SLI. Voodoo2 is also documented but DRI for it while practical might be a little esoteric. I've always wanted to add DRI to it but never had the justification/time ;) --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [PATCH] new radeon memory map fixes
On Fri, 2006-01-27 at 12:15 +1100, Benjamin Herrenschmidt wrote: On Thu, 2006-01-26 at 10:43 +1100, Benjamin Herrenschmidt wrote: Xorg driver patch: http://gate.crashing.org/~benh/radeon-memmap-7.0-2.diff Just noticed something else: this seems to only read OV0_SCALE_CNTL but not write it back with RADEON_SCALER_ENABLE disabled. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5341] System locks up when starting X w/ DRI on a Radeon RV370 (X300)
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=5341 --- Additional Comments From [EMAIL PROTECTED] 2006-02-01 05:41 --- I'm afraid Ben's three patches did _not_ help my FreeBSD-6.0-STABLE (updated 1/30/06) system with an X300 PCIe Dell dual-head. I've also tried killing the HyperThreading, the second head, etc., to no avail. This, on the standard X.org 6.9 as installed through ports. I remade xorg-libraries after patching the radeon_driver.c file. (--) PCI:*(1:0:0) ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] rev 0, Mem @ 0xd000/27, 0xdfde/16, I/O @ 0xdc00/8, BIOS @ 0xdfe0/17 (--) PCI: (1:0:1) ATI Technologies Inc RV370 [Radeon X300SE] rev 0, Mem @ 0xdfdf /16 The X log does not get written when it locks up. What else can I post that would help? -- 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. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5341] System locks up when starting X w/ DRI on a Radeon RV370 (X300)
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=5341 --- Additional Comments From [EMAIL PROTECTED] 2006-02-01 06:01 --- Created an attachment (id=4523) -- (https://bugs.freedesktop.org/attachment.cgi?id=4523action=view) Fix current DRM on FreeBSD The virtual field of struct drm_sg_mem_t was not initialized in drm_sg_alloc which caused crashes. This patch addresses this issue and also makes current DRM compile on FreeBSD. -- 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. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5341] System locks up when starting X w/ DRI on a Radeon RV370 (X300)
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=5341 --- Additional Comments From [EMAIL PROTECTED] 2006-02-01 06:09 --- (In reply to comment #19) I'm afraid Ben's three patches did _not_ help my FreeBSD-6.0-STABLE (updated 1/30/06) system with an X300 PCIe Dell dual-head. I've also tried killing the HyperThreading, the second head, etc., to no avail. This, on the standard X.org 6.9 as installed through ports. I remade xorg-libraries after patching the radeon_driver.c file. Try the patch I attached with CVS versions of DRM and xorg. I also needed to apply two of Ben's patches (radeon-memmap-7.0-2.diff and radeon-memmap-drm-3.diff). The patch fixes an issue that only exists with non-agp radeon cards. The X log does not get written when it locks up. What else can I post that would help? I was able to get the vital debugging information via a serial console only. Just compile kernel with DDB in and attach another computer with a null-modem cable. There is more help about this subject in the FreeBSD developers handbook. Oh... And don't forget to set sysctl hw.dri.0.debug to 1 to see the DRM debug messages. -- 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. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5341] System locks up when starting X w/ DRI on a Radeon RV370 (X300)
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=5341 --- Additional Comments From [EMAIL PROTECTED] 2006-02-01 07:04 --- (In reply to Comment #21) I'm afraid my g-world firewall is blocking my direct CVS access. I'll have to set up a redirect through my outside server as I do for CVSup. Thanks for the rapid response, Markus! I understand what I need to do and will do it. Just one q: Where will I find Ben's memmap patches? -- 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. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5601] ATI radeon IGP 320M with dri enabled in blender corrupts screen
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=5601 [EMAIL PROTECTED] changed: What|Removed |Added Version|unspecified |CVS --- Additional Comments From [EMAIL PROTECTED] 2006-02-01 10:23 --- This problem is not limited to radeon. R200 has exactly the same problem, if you switch off tcl. As a guess, I'd say it's because the t_vertex implementation was ported from r200 to radeon so it shares the same bugs... -- 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. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
texture memory management question
Hello All, I have a question about texture memory management in the r200 driver. What is a primary need for a separate memory layout version for every client? Would not it be simpler if there was only one memory heap in the sarea with a global LRU list? Then there would be no need for heap layout synchronization and region aging, as well as for a global LRU region list. And that would possibly allow for economical memory management (we don't need to kick out up to 2MB of other people's textures at once, we only need as much as we need). Also, this would allow for texture sharing if we somehow could find out that someone else is using exactly the same texture. Was that solution considered when the r200/radeon driver was being designed? What difficulties that I have overseen would it imply? Sorry for offtopic as this is not really related to the current r300 development activities. Thank you. Mikhail Bautin
[Bug 5341] System locks up when starting X w/ DRI on a Radeon RV370 (X300)
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=5341 --- Additional Comments From [EMAIL PROTECTED] 2006-02-01 18:07 --- (In reply to comment #22) Just one q: Where will I find Ben's memmap patches? Sorry. I tought I mentioned this. You can find the patches from http://gate.crashing.org/~benh/ -- 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. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
