From: Anton Farygin <rider@altlinux.com> To: hardware@altlinux.ru Subject: [Hardware] [Fwd: [Savage40] New Savage DRM preview] Date: Sun, 09 Jan 2005 12:51:54 +0300 Message-ID: <41E0FEBA.10301@altlinux.com> (raw) [-- Attachment #1: Type: text/plain, Size: 4 bytes --] FYI [-- Attachment #2: [Savage40] New Savage DRM preview --] [-- Type: message/rfc822, Size: 6385 bytes --] From: "Felix Kühling" <fxkuehl@gmx.de> To: DRI-Devel <dri-devel@lists.sourceforge.net>, "X.Org" <xorg@lists.freedesktop.org>, savage40@probo.com Subject: [Savage40] New Savage DRM preview Date: Wed, 29 Dec 2004 18:29:42 +0100 Message-ID: <1104341382.4526.45.camel@trabant> Hi all, After a few coding night shifts over the holidays the development of the new Savage DRM driver finally reached a stage where I am pretty confident that no more binary-incompatible changes to the interfaces between DDX, DRM and the 3D driver will be needed. I uploaded my work in the form of three patches to http://freedesktop.org/~fxkuehl/savage. I am going to get this committed to the various CVS repositories ASAP so that all further work can happen under version control again. Anybody who is comfortable with compiling X.org, DRM and Mesa from source should apply these patches and test them. It's worth it! :-) (see the Feature summary below) IMPORTANT: If you get lockups with these patches try enabling ShadowStatus in xorg.conf. This fixed lockups related to vertex DMA on all hardware I tested. In fact, I would be surprised if anyone got away without lockups without ShadowStatus. Therefore a future version of the driver may refused to enable DRI if ShadowStatus is disabled. Feature summary: * Version numbers of DRM and DDX were bumped to 2.0.0 in order to reflect the binary incompatibility to previous versions. * Secure DRM and DDX drivers that do not allow unprivileged 3D applications direct access to the hardware. * Should be stable on a larger variety of hardware by using shadow status in the DRM if it is enabled in xorg.conf. * Better performance by using vertex DMA when possible. Because of experimentation with the binary interfaces I kept my work out of CVS for quite some time. I tried to limit the amount of changes to what was absolutely necessary in order to get things working properly. There are some features which will be implemented in the near future. Some of them are already sketched in the patches but not implemented yet. See the TODO list for details. TODO: * Apply clipping rectangles to 3D drawing commands. * Support for PCI cards. * Command DMA on Savage4-based hardware for better performance. * Use DMA for texture uploads. * Implement a fast path with less overhead that makes more efficient use of available hardware primitives. Best regards, Felix Kühling -- | Felix Kühling <fxkuehl@gmx.de> http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | _______________________________________________ Savage40 mailing list Savage40@probo.com http://www.probo.com/mailman/listinfo/savage40 _______________________________________________ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
reply other threads:[~2005-01-09 9:51 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=41E0FEBA.10301@altlinux.com \ --to=rider@altlinux.com \ --cc=hardware@altlinux.ru \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux hardware support This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/hardware/0 hardware/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 hardware hardware/ http://lore.altlinux.org/hardware \ hardware@altlinux.ru hardware@lists.altlinux.org hardware@lists.altlinux.ru hardware@lists.altlinux.com hardware@altlinux.org public-inbox-index hardware Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.hardware AGPL code for this site: git clone https://public-inbox.org/public-inbox.git