--- Ian Romanick <[EMAIL PROTECTED]> wrote: > Alex Deucher wrote: > > I'm thinking about implementing a textured video option on radeon > for > > mergedfb (or non-mergedfb too for that matter). It would be useful > > since video windows could span heads in mergedfb mode and you could > > also have multiple Xv windows at the same time rather than just one > > with the overlay unit. My questions are as follows: > > > > 1. looking at the mga textured video code, it disables the DRI > when it > > is in use. is there any reason for this? > > Boy howdy is there ever! It is easy for the 2D driver and the 3D > driver > to work together because they don't share any state. Specifically, > they > don't share texture memory state, 3D hardware register state, or > vertex > engine state. As soon the 2D driver start using texture mapping > hardware for Xv, all that state becomes shared. If you're going to > go > to the effort of making the server-side driver and the client-side > (DRI) > driver share all that state, you may as well go just a small bit > further > and get the client-side driver loaded server-side. :) If nothhing > else, > that would make maintainence easier.
Ummm... ok... so by this you mean, linking the radeon_dri.o into radeon_drv.o so that I can call functions from the 3D driver in the 2D driver and hence share state? Sorry if I mis-understand... Alex __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
