Re: [Mesa3d-dev] [PATCH-RFC] st_api, EGLImage, and flush_frontbuffer

[Chia-I Wu <ol...@gm...>]

On Fri, Mar 12, 2010 at 3:11 AM, Jakob Bornecrantz <ja...@vm...> wrote:
> Thanks for doing this Chia-I, also a very excellent summary. Last time we
> talked about st_api IIRC we both agreed that the way we implemented EGLImage
> was wrong. However I think that we have waited long enough to move the state
> trackers over to st_api.
> Would it to much trouble for you if we didn't do EGLImage in the first
> gallium-st-api feature branch? My feeling is that they are two separate
> issues and I think we should be able to quickly resolve moving the state
> trackers over to st_api and then move on to EGLImage. Looking at the patches
> the only affected one is the VG state tracker while the rest should just be
> not to apply the EGLImage related patches. I can do this later tonight and
> send out a series and give you something to work on.
> I really want to move the state trackers over to st_api and I don't want the
> EGLImage issues holding us back. I also think that that part of the patch
> series looks excellent and I don't foresee any difficulties getting this
> merged ASAP.
> Again thanks for doing this I know the inter state tracker interactions are
> a mess.
I've pushed a new branch, gallium-st-api, for the development of st_api.  It
consists of this patch series with EGLImage bits stripped out.  I also like to
have the branch merged sooner than later.

-- 
ol...@Lu...