From: "Konstantin A. Lepikhov" <lakostis@altlinux.ru> To: ALT Linux Devel Mailing List <devel@altlinux.ru> Subject: [devel] [Re: [R300] new snapshot ?] Date: Mon, 23 May 2005 17:14:35 +0400 Message-ID: <20050523131434.GA30595@lks.home> (raw) [-- Attachment #1: Type: text/plain, Size: 2359 bytes --] Hi! JFYI - текущий статус поддержки DRI для R300. Оказывается, она даже стабильнее, чем для R200 :) ----- Forwarded message from Nicolai Haehnle <prefect_@> ----- Date: Thu, 19 May 2005 16:07:44 +0200 From: Nicolai Haehnle <prefect_@> To: Keith Whitwell <keith@> Cc: Vladimir Dergachev <volodya@>, Aapo Tahkola <aet@>, Jerome Glisse <j.glisse@>, Ben Skeggs <d4rk74m4@>, dri-devel@ Subject: Re: [R300] new snapshot ? X-Authenticated: #5817363 User-Agent: KMail/1.8 X-Y-GMX-Trusted: 0 On Thursday 19 May 2005 09:20, Keith Whitwell wrote: > Vladimir Dergachev wrote: > > > > Hi Aapo, Ben, Jerome, Nicolai: > > > > I recently checked fresh code from CVS and was pleasantly surprised > > to see that all Quake3 levels that were broken are now perfect - in fact > > I cannot find anything that is amiss ! > > > > Do you think it would be a good idea to tag the current code and make > > a snapshot ? Sure, anytime :) > So have you guys given any consideration to moving the r300 driver into > mesa proper? CVS access shouldn't be a problem, fwiw... There are two main points that have stopped me from pushing for the inclusion of the driver into Mesa proper: 1. Kernel-level security holes We should take care of full command-stream verification before moving the driver into Mesa CVS. It's easy to say "We can do that later", but if we say that it's likely that it won't be done in a long time. 2. DRM binary compatibility We still don't know the meaning of many of the registers. Some registers are labelled "dangerous" which means we might have to do some more checks in the kernel to make sure user processes can't do harmful stuff. This means that we might have to *remove* some of the cmdbuf commands that exist today in the future. If the others believe moving r300 to Mesa is a good idea, then I'll do some auditing to the DRM code. Once I (or somebody else) has done this, I'm okay with moving the driver as long as we don't enforce DRM binary compatibility yet. cu, Nicolai ----- End forwarded message ----- -- WBR, Konstantin chat with ==>ICQ: 109916175 Lepikhov, speak to ==>JID: lakostis@jabber.org aka L.A. Kostis write to ==>mailto:lakostis@pisem.net.nospam ...The information is like the bank... (c) EC8OR [-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-05-23 13:14 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-23 13:14 Konstantin A. Lepikhov [this message] 2005-05-23 13:42 ` Alexey I. Froloff 2005-05-23 13:48 ` [devel] " Konstantin A. Lepikhov
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=20050523131434.GA30595@lks.home \ --to=lakostis@altlinux.ru \ --cc=devel@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 Team development discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/devel/0 devel/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 devel devel/ http://lore.altlinux.org/devel \ devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru public-inbox-index devel Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.devel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git