On Sun, Sep 20, 2009 at 9:27 PM, Chia-I Wu <olva...@gmail.com> wrote:
> On Thu, Sep 10, 2009 at 06:24:24PM +0800, Chia-I Wu wrote:
>> On Thu, Sep 10, 2009 at 01:28:16PM +0800, Chia-I Wu wrote:
>> > On Thu, Sep 03, 2009 at 02:27:42PM +0800, Chia-I Wu wrote:
>> > > I am still cleaning up the implementation.  But I would like to know
>> > > your ideas about OpenGL ES support, and the path I take.  Thanks.
>> > After some cleanups, I think it is more suitable to split the patch
>> > series into 2 parts
>> > 1. Make features more modular
>> > 2. Support for OpenGL ES
>> This is a big series with 2 parts.  If the patch series is considered
>> not ready for master after reviewing, I would like to know if there is a
>> chance for the first part (patch 01~18) to be merged first, after
>> incorporating any feedbacks.
> The patch series has outdated.  Should I update re-submit now or should
> I wait until 7.6 is released?  It seems most people are busy with the
> release and LPC.

I think you should stick to working on Mesa/master; you don't need to
worry about the 7.6 branch.  In any case, I haven't had much time for
reviewing your later patches, especially the big ones.  Didn't you
apply for an account for git-write?


> I would also like to know which way is prefered for reviewing the
> patches.  The patches are ordered in such way that they
>
> 1. re-work mfeatures.h support
> 2. fix core mesa when certain features are disabled
> 3. add -c flags to python scripts to generate headers for use with
>   opengl es
> 4. add opengl es overlay and state trackers
> 5. add opengl es demos
>
> They might be too huge to review.  I am thinking, if it is clear to
> everyone that the purpose of (1) is to support opengl es, I want to
> submit that part first, and submit the rests after it is merged.  The
> reason is that it touches many files in core mesa that it causes
> conflicts easily.  Plus, that part is interesting in itself.

The mfeatures.h stuff doesn't have to be perfect.  Enough of it worked
to support GL ES as of last year though.  If you post the updated
patch, I'll take a look.  Your plan sounds OK otherwise.

-Brian

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to