<body><div style="font-family: '微软雅黑'; font-size: 10.5pt;">Thanks for your reply.<div>I heard of virgil is not enough mature. So I think <span style="font-size: 10.5pt;">"passthough into host 3d api" is a easy way for now. </span><span style="font-family: Helvetica, Arial, PingFang, 苹方, 'Hiragino Sans GB', 冬青黑体, 'Microsoft YaHei', 微软雅黑, Tahoma, SimSun, 宋体, STXihei, 华文细黑, Heiti, 黑体, sans-serif; font-size: 10.5pt; background-color: rgb(255, 255, 255);"> And "</span><span style="font-family: Helvetica, Arial, PingFang, 苹方, 'Hiragino Sans GB', 冬青黑体, 'Microsoft YaHei', 微软雅黑, Tahoma, SimSun, 宋体, STXihei, 华文细黑, Heiti, 黑体, sans-serif; font-size: 10.5pt; background-color: rgb(255, 255, 255);">gles pipes" @Luo meantioned is the same meaning?</span></div><div><br></div><div>The 3D feature for other linux distribution just like Ubuntu is our good reference. But it is not easy to run hardware 3D in Ubuntu successfully. I don't why. If it works well, we will start to analyze the difference between the addtion of Ubuntu and Android-x86 as entry point. If you know some detail to tell us, it is will much helpful, thanks.</div><div><br></div><div>btw. Cross wall from China mainlan<span style="font-size: 10.5pt;">d is not stable in these days. We can't access andorid-x86/google/</span><a href="http://android.com" class="yo-genlink" target="_blank" style="font-size: 10.5pt;">android.com</a><span style="font-size: 10.5pt;"> and etc~~. And we are busy for some other affair. We will take more time from the end of this month.</span></div><div><br></div><div>best</div><div>Dong Hao<br>
<div class="yomail-sig" style="margin:0;padding:0;"><div class="yomail-sig" style="padding: 0px 0px 0px 20px; margin: 0px 0px 0px -20px;"><span> </span><hr class="-eMc-email-sig" style="width: 101px;border: 0;border-top: 1px solid #ccc;" align="left"> <a href="http://www.yomail.com/?utm_source=signature" style="font-size:10.5pt;font-family:微软雅黑;">Sent from YoMail for Gmail</a></div></div>
<br>
<div class="gmail_quote -eMc-quote" style="margin: 0px 0px 0px 0.8ex; display: block;">
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<div style="PADDING-RIGHT: 8px; PADDING-LEFT: 8px; FONT-SIZE: 12px;COLOR:#000000; BACKGROUND: #efefef; PADDING-BOTTOM: 8px; PADDING-TOP: 8px">
<div>
<b>发件人：</b> <a href="mailto:huisinro@yahoo.com" target="_blank">Huihong Luo</a>
</div>
<div>
<b>发送时间：</b> 2017-07-23 21:59:43
</div>
<div>
<b>收件人：</b>
<a href="mailto:cwhuang@android-x86.org" target="_blank">Chih-Wei Huang</a>
</div>
<div>
<b>抄送：</b>
<a href="mailto:michael.thayer@oracle.com" target="_blank">Michael Thayer</a>;
<a href="mailto:vbox-dev@virtualbox.org" target="_blank">vbox-dev@virtualbox.org</a>;
<a href="mailto:zhengxuwen@c2engine.com" target="_blank">zhengxuwen</a>;
<a href="mailto:tim3385@gmail.com" target="_blank">tim3385</a>
</div>
<div>
<b>主题：</b> Re: [vbox-dev] fw:Re: 3d acceleration of android-x86 for virtualbox
</div>
</div>
</div>
<blockquote style="margin:0;">
<div dir="ltr">
Another option, which is more doable, is to use emulator's gles pipes. <br><br>Sent from my iPhone<br><br>> On Jul 19, 2017, at 4:35 AM, Chih-Wei Huang <<a href="mailto:cwhuang@android-x86.org" class="yo-genlink">cwhuang@android-x86.org</a>> wrote:<br>> <br>> 2017-07-19 7:05 GMT+08:00 tim3385 <<a href="mailto:tim3385@gmail.com" class="yo-genlink">tim3385@gmail.com</a>>:<br>>> <Michael Thayer> 在 2017-07-18 16:20:43 写道:<br>>> Hello Dong Hao,<br>>> <br>>> (Is that the right way to address you?)<br>>> <br>>> 15.07.2017 19:57, tim3385 wrote:<br>>> [...]<br>>>> vboxguest, vboxvideo and vboxsf have been probed into android-x86.<br>>>> We are finding the entrance of translate android-x86 3d implement to<br>>>> host OS.<br>>>> <br>>>> We have a few questions about virtualbox, thanks^^:<br>>>> <br>>>> 1 "external_vboxguest-linux-module" is a driver for virtualbox's virtual<br>>>> hardware, is my understanding right?<br>>> <br>>> The vboxguest module drives the virtual "guest" device which does most<br>>> of the work of letting the Guest Additions communicate with the host.<br>>> <br>>>> 2 There is a sentense "Hardware 3D acceleration under Ubuntu 10.10 and<br>>>> Fedora 14 have been tested and confirmed as working"<br>>>> in <a href="http://www.virtualbox.org/manual/ch04.html#guestadd-video" class="yo-genlink" target="_blank">http://www.virtualbox.org/manual/ch04.html#guestadd-video</a> . Can you<br>>>> introduce the theory? eg. where is the entrance that The additon<br>>>> translate 3d api invoke to host?<br>>> <br>>> I see that our manual needs some adjusting not to refer to precise guest<br>>> versions which get out of date quickly. To repeat: the theory is that<br>>> we replace <a href="http://libgl.so" class="yo-genlink" target="_blank">libGL.so</a>.1 on the guest with our own one: <a href="http://vboxogl.so" class="yo-genlink" target="_blank">VBoxOGL.so</a>, with<br>>> various dependencies VBoxOGL*.so. Those marshall OpenGL API calls<br>>> (though they deal with some things locally in the address space of the<br>>> caller) which they send through the guest device using the HGCM<br>>> transport (though it can also be done through the graphics device using<br>>> the HGSMI transport) to the host for rendering. See the make file<br>>> src/VBox/Additions/common/crOpenGL/Makefile.kmk<br>>> for an overview of what goes into those libraries. The source files are<br>>> rather scattered over the tree, and some are auto-generated, but if you<br>>> want to do something here you will not get around doing a lot of reading<br>>> of source. We could probably answer specific questions, but generic<br>>> explanations of "how it works" will probably not help much without that<br>>> reading.<br>>> <br>>> See though my suggestion by private e-mail of modifying the vboxvideo<br>>> graphics device to be able to channel Qemu's virgl rendering protocol<br>>> through to the host. You would be able to leave the guest rendering<br>>> code in Mesa almost unmodified (just changed enough to recognise<br>>> vboxvideo as a supported device) and re-use the host rendering code (the<br>>> virglrenderer library) which would just need to be hooked, more or less<br>>> unmodified, into our host code. The changes to vboxvideo itself should<br>>> be reasonably trivial too. In comparison, reworking our current 3D code<br>>> will be a lot of work.<br>> <br>> Hi Michael,<br>> Thank you for the detailed reply.<br>> Let me sum it up to see if I understand<br>> your words correctly:<br>> <br>> * Modify Mesa to recognize vboxvideo<br>> * Modify vboxvideo to send virgl rendering protocol to the host<br>> * Hook virglrenderer to vbox host code<br>> <br>> I have concern about the third step.<br>> As I know currently virglrenderer only supports Linux.<br>> (though I saw some Windows's patches are ongoing)<br>> That would limit our supported hosts.<br>> Besides, I think currently virglrenderer is still not stable<br>> or complete enough. As I tested on QEMU with virgl,<br>> many 3D benchmark apps don't work.<br>> (just crash or black screen)<br>> The only famous benchmark app that works on it<br>> is GLXBench.<br>> <br>> I'm still thinking if it's possible to use your current 3D code<br>> directly. Could you give us more ideas how it work<br>> for Linux or Windows guests? Or point us which<br>> code to read. Thanks a lot!<br>> <br>>>> 3 We want to do some modification based<br>>>> on "external_vboxguest-linux-module". Could you please give us some<br>>>> suggestions or samples?<br>>> <br>>> That is hard without knowing what you want to do.<br>>> <br>>>> 4 About android-x86: is there some way to directly(like by usb<br>>>> wire) connect host to android-x86 in virtualbox by adb? We only found<br>>>> the way "adb connect IP" can success, and the "IP" must be a lan IP<br>>>> but 127.0.0.1 so that the transfer speed would be low.<br>>> <br>>> Not that I know of, though I don't know much about adb. In theory you<br>>> could write a virtual USB device to do that, but I suspect you have<br>>> already set more than enough work for yourself.<br>>> <br>>>> 5 How can sound card of virtualbox Android-x86 work fine?<br>>> <br>>> Sound is being worked on. What problems are you experiencing?<br>>> <br>>> Regards<br>>> Michael<br>>> <br>>>> best<br>>>> Dong Hao<br>>>> <br>>>> ------------------------------------------------------------------------<br>>>> Sent from YoMail for Gmail <<a href="http://www.yomail.com/?utm_source=signature>" class="yo-genlink" target="_blank">http://www.yomail.com/?utm_source=signature></a><br>>>> <br>>>> < Michael Thayer <mailto:<a href="mailto:michael.thayer@oracle.com" class="yo-genlink">michael.thayer@oracle.com</a>>> 在 2017-07-12<br>>>> 19:17:49 写道:<br>>>> <br>>>> 10.07.2017 10:52, tim3385 wrote:<br>>>>> Dear Sirs:<br>>>>> <br>>>>> I want to make virtualbox addition for android-x86 to improve the<br>>>>> efficient of 3d and 2d.<br>>>>> Mr. Chih-Wei Huang, current project maintainer of android-x86, has<br>>>> given<br>>>>> me some reference about android-x86 3d acceleration. They just discuss<br>>>>> this with VWare.<br>>>>> <br>>>>> I want to look for somebody who can help me begin. thanks.<br>>>> Hello Tim (is that the right name to address you by?),<br>>>> <br>>>> I'm afraid that no one has a lot of time to help you with this. I will<br>>>> make a quick suggestion about where you could start looking. You will<br>>>> probably have most luck studying the code and asking precise questions<br>>>> when things are not clear.<br>>>> <br>>>> You will probably want to start by looking at the X11 <a href="http://libgl.so" class="yo-genlink" target="_blank">libGL.so</a> and its<br>>>> dependencies. This is a purely user-space library which marshalls the<br>>>> OpenGL command stream and some information from GLX commands and sends<br>>>> it to the host, currently via the "guest" device, on Windows through the<br>>>> graphics device. On the host the 3D content is rendered to a host<br>>>> window - a separate one from the normal guest screen window, which<br>>>> sometimes causes unwanted artefacts when 2D and 3D guest rendering are<br>>>> mixed.<br>>>> <br>>>> It will probably take you a while to get used to our build system to<br>>>> work out what goes into <a href="http://libgl.so" class="yo-genlink" target="_blank">libGL.so</a> (including generated files), but you<br>>>> will probably have to go through that.<br>>>> <br>>>> Hope that helps for a start.<br>>>> <br>>>> Regards<br>>>> Michael<br>>> [...]<br>> <br>> <br>> <br>> -- <br>> Chih-Wei<br>> Android-x86 project<br>> <a href="http://www.android-x86.org" class="yo-genlink" target="_blank">http://www.android-x86.org</a><br>> _______________________________________________<br>> vbox-dev mailing list<br>> <a href="mailto:vbox-dev@virtualbox.org" class="yo-genlink">vbox-dev@virtualbox.org</a><br>> <a href="https://www.virtualbox.org/mailman/listinfo/vbox-dev" class="yo-genlink" target="_blank">https://www.virtualbox.org/mailman/listinfo/vbox-dev</a><br><br>
</div>
</blockquote>
</div>
</div></div></body>