--- Tim Roberts <[EMAIL PROTECTED]> wrote: > Alex Deucher wrote: > > >--- Felix Kühling <[EMAIL PROTECTED]> wrote: > > > > > >>3. Separate commands and data > >> > >>Right now commands and data are submitted to the chip as one data > >>stream, either via the BCI or via DMA buffers. For easier security > >>checking command and data streams should be separated. Savage chips > >>can > >>handle vertex buffers and indexed drawing commands. I couldn't find > a > >>way to specify the vertex format for indexed drawing commands. > Either > >>it is automagically deduced from various state bits (specular and > >>enabled > >>texture units come to mind) or vertices vertex buffers are always > >>complete. This would also mean that their format differs between > >>Savage3D and Savage4 since the Savage3D has only one texture unit. > >>These > >>are things that I'dd have to find out by experiment. But maybe > >>someone > >>happens to know it or has better documentation than I do. > >> > >Perhaps, we can save some experimenting time. Tim, do you remember > off > >hand which of these modes we can use with savage4/3d/etc? > > > > > > I'm sorry, I've parsed this twice and I'm still not I sure I > understand > what question is being asked. > > My spec for the Savage3D is complete. However, they actually removed > > the 3D section from both of the Savage4 register specs they sent me, > so > it is somewhat difficult for me to do comparisons. If you can ask a > more specific question, I'd be happy to help. >
Felix can probably phrase this better than I since he has worked more closely with the 3D code. however, I think what he is asking is how should vertex commends be formatted when sent to the 3D engine when using indexed drawing commands? We want to separate drawing commands and data so that we can do DMA securely to prevent someone writing anywhere in memory. > Note, however, that it is hardly worth the trouble to spend time on > the > Savage3D. There were so many problems in the 2D engine that, by the > time it became stable, the much improved Savage4 was available. Few > of > the Savage3Ds ever saw the light of day. Well, there are quite a few savage IX and MX chips around and they share the 3D engine with the savage3D. that's what we are developing on. Alex > > -- > - Tim Roberts, [EMAIL PROTECTED] > Providenza & Boekelheide, Inc. > __________________________________ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools ------------------------------------------------------- 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=1356&alloc_id=3438&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
