On Mon, 2009-01-19 at 17:25 -0500, Younes Manton wrote:
> > - Drivers probably shouldn't mix'n'match hardware and software steps,
> > although this is a driver preference, e.g.
> >
> > video_do_foo();
> > nouveau_do_bar();
> > video_do_baz();
> >
> > I would guess that the migration setup would take longer than just doing
> > video_do_bar() instead, but that's just my opinion. I'm sure that not
> > all chipsets are quite like that.
>
> I doubt this will be a problem, I can't think of any reason to fall
> back to software for a stage if the preceding stage was handled in
> hardware or shaders. There may be such an oddball case, but yeah no
> point in mixing hardware, software, and shaders if we have to read
> back from the GPU.
Sorry to get in the way, but if at some point in the pipe everything can
be done in hardware or shaders, maybe drivers should expose what they
can accelerate to let the app handle the rest (some smart frameworks
like gstreamer could take shortcuts).
OTOH that could require a more complex interface.
Xav
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
