<div dir="ltr">Hi, Chih-Wei, Emil,<div> These series of patches was originally developed on the 11.0 branch, and later ported to 11.2. I don't think softpipe was working when I worked on this, Actually the first few patches is from when I tried to make softpipe work. There are some memory issue in mesa that cause softpipe/llvmpipe to crash when booting. I assumed it was due to jemalloc and ptmalloc difference. </div><div> Regarding the TASK and Change-Id sections in the comment, sorry about that. I should have removed them when I send out the patches, you can just remove them. </div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-04-28 23:52 GMT+08:00 Chih-Wei Huang <span dir="ltr"><<a href="mailto:cwhuang@android-x86.org" target="_blank">cwhuang@android-x86.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">2016-04-28 22:22 GMT+08:00 Emil Velikov <<a href="mailto:emil.l.velikov@gmail.com">emil.l.velikov@gmail.com</a>>:<br>
> Hi Chih-Wei,<br>
><br>
> Thanks for getting these out to the community.<br>
><br>
> On 28 April 2016 at 08:34, Chih-Wei Huang <<a href="mailto:cwhuang@android-x86.org">cwhuang@android-x86.org</a>> wrote:<br>
>> This is a series of patches developed by Jide Technolody to enable<br>
>> the llvmpipe for software rendering of Android.<br>
>> It makes a device without a Mesa supported GPU could run most modern<br>
>> Android apps.<br>
>><br>
> Afaict one should only need the extra Android.mk files to get llvmpipe<br>
> considering that softpipe already works.<br>
> Have you/the Jide folks tried the latter already ? Does it work<br>
> without these patches ?<br>
<br>
</span>Hmm, interesting point.<br>
Did you mean just adding Android.mk for llvmpipe<br>
is enough?<br>
<span class=""><br>
>> These patches are mainly developed and tested on the 11.0 and 11.2<br>
>> branches. They might not work with the Mesa master branch.<br>
>><br>
> Humble request - please always aim for master. Doing this will get you<br>
> the latest stable branch for free.<br>
> If you're targeting some old stable branch then you'll will have to<br>
> duplicate the effort to land things in master. And new functionality<br>
> goes _only_ in master<br>
<br>
</span>I clearly understand this point.<br>
Actually I've spent several days to try to<br>
make it work on the master branch.<br>
That's why it was delayed -- I supposed to send them<br>
in the last week.<br>
<br>
However, the master branch is always broken for android.<br>
There are a lot of build break I need to fix and workaround<br>
or I can't test it. After fixed all the errors and built it OK,<br>
however, it didn't work as expected.<br>
The system boots to Home but all display is garbled.<br>
I'm not sure if I made some mistakes on<br>
fixing the building errors or there are some changes<br>
that really broke these patches.<br>
(the latest commit I've tried in the master is 32cb7d61)<br>
I finally decide to give it up and send them as the current status.<br>
(otherwise it will take too much of my time and delay<br>
my other pending tasks)<br>
<br>
Unfortunately the situation is most mesa developers<br>
don't care android so they usually break android build<br>
or functions. Unless the situation is changed it's very hard<br>
for us to follow the master branch closely.<br>
<span class=""><br>
>> The patches depend on some patches developed by Varad Gautam which<br>
>> have not been merged in Mesa master yet, say<br>
>><br>
>> fc40946 egl: fixup: define droid_image_loader_extension<br>
>> d15901d egl: android: populate dri2_surf->window early<br>
>> cff1928 egl: android: use __DRI_IMAGE_LOADER to get color buffers<br>
>> b556be4 egl: android: experimental dma-buf fd support<br>
>><br>
>> The dependency may be removed but we haven't tested that yet.<br>
>><br>
> Afaict none of Varad's work should be required here. It adds an<br>
> alternative (better) method of the already existing functionality.<br>
<br>
</span>I also guess that but it need more time to verify that.<br>
<span class=""><br>
> Related: iirc things have gone wrong during the rebase of Varad's work<br>
> in Android-x86. Rob H recently sent some patches (based of Android-x86<br>
> ?) which has some strange/extra code in them.<br>
<br>
</span>Yes I notice that but again it need time<br>
to figure what patches are really needed.<br>
However due to the master branch status is horrible<br>
for android so I gave up.<br>
<br>
If possible, I'll ask Mauro to follow the master branch<br>
and work with others to fix android stuff<br>
for future android release (i.e., N).<br>
For marshmallow-x86 we will stay in mesa 11.2<br>
and I'll move my time to other pending tasks<br>
for a stable release.<br>
<span class=""><br>
>> WuZhen (7):<br>
>> st/dri: fix double free of dri_drawable<br>
>> tgsi: fix stack allocated struct may not be initialized<br>
>> gallium/swrast: fix dri_sw_dt->data free func not matching alloc func<br>
>> android: print debug info to logcat<br>
>> android: enable dlopen<br>
>> android: enable x86 asm and sse4 for x86 and x86_64<br>
>> android: support swrast<br>
><br>
> A couple of high level suggestions:<br>
> - Please split patches appropriately (more). Some patches are great<br>
> while others should become 3-4 separate ones.<br>
<br>
</span>Actually I think the first 6 patches are already good.<br>
The 7th patch is bigger and could probably be split.<br>
Could you suggest how to do it?<br>
<span class=""><br>
> - Drop the NO_REF_TASK, tested and Change-Id tags. Sadly these don't<br>
> bring much, plus non-Jide people are unlikely to have access to the<br>
> Gerrit and other instances where these are used.<br>
<br>
</span>These are Jide's internal comments I just kept it as.<br>
I've no opinion to keep or remove them.<br>
Let WuZhen decide.<br>
<span class=""><br>
> I'll try to look into the individual patches shortly.<br>
<br>
</span>Thanks!<br>
<span class=""><br>
--<br>
Chih-Wei<br>
Android-x86 project<br>
<a href="http://www.android-x86.org" rel="noreferrer" target="_blank">http://www.android-x86.org</a><br>
<br>
</span><span class="">--<br>
You received this message because you are subscribed to the Google Groups "Android-x86 development" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:android-x86-devel%2Bunsubscribe@googlegroups.com">android-x86-devel+unsubscribe@googlegroups.com</a>.<br>
To post to this group, send email to <a href="mailto:android-x86-devel@googlegroups.com">android-x86-devel@googlegroups.com</a>.<br>
</span>To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/android-x86-devel/CAKc24n0zF-Po%3DCXwLt7wHr5ogbV-LGOsDZWqkk%3D3b_pGfc2H-A%40mail.gmail.com" rel="noreferrer" target="_blank">https://groups.google.com/d/msgid/android-x86-devel/CAKc24n0zF-Po%3DCXwLt7wHr5ogbV-LGOsDZWqkk%3D3b_pGfc2H-A%40mail.gmail.com</a>.<br>
<div class="HOEnZb"><div class="h5">For more options, visit <a href="https://groups.google.com/d/optout" rel="noreferrer" target="_blank">https://groups.google.com/d/optout</a>.<br>
</div></div></blockquote></div><br></div>