Hi, see below.

On 03/14/2014 12:01 PM, VanCutsem, Geoffroy wrote:
> On Fri, 2014-03-14 at 10:30 +0400, Stanislav Vorobiov wrote:
>> Hi, see my comments below.
>>
>> On 03/14/2014 05:42 AM, 황석연 wrote:
>>> Hi, all.
>>>
>>>  
>>>
>>> We have a plan to upgrade emulator kernel to 3.12.x (latest longterm 
>>> version).
>>>
>>> It is progressing on branch tizen_linux_3.12.
>>>
>>>  
>>>
>>> @ stanislav,
>>>
>>> Does it have any impact on VIGS/YaGL ?
>> Yes, VIGS kernel driver will have to be modified for DRM interface changes, 
>> I'll start
>> upgrading it.
> 
> Are you pushing this VIGS kernel driver upstream?
No, I'll push to emulator kernel git

> 
>>
>>>
>>>  
>>>
>>> @ IVI team,
>>>
>>> Does it have any impact on IVI ?
>> Just a small comment on this one, I think it'll have positive impact since 
>> we'll be able to turn SMACK
>> back on. Currently it's disabled because 3.4 SMACK support isn't enough to 
>> run Tizen IVI, but 3.12 should
>> be enough.
> 
> As an end-goal, it would be nice to be able to just use the official
> Tizen IVI kernel. Is VIGS all that's missing in it to allow you to use
> it?
It's more than that, there're also other virtual devices. And even if it was 
only VIGS, pushing
it upstream is not an easy task, one reason is because VIGS kernel driver is 
useless without:
* QEMU VIGS device - this would have to be pushed to QEMU upstream
* libdrm - VIGS has it's own part in libdrm
* xf86-video-vigs - For X11-based systems VIGS has it's own X video driver for 
2D acceleration
Also, there're 3D acceleration components (it's called YaGL), which are also 
obviously needed:
* YaGL kernel driver
* YaGL OpenGL implementation
* QEMU YaGL device

> Intel Corporation NV/SA
> Kings Square, Veldkant 31
> 2550 Kontich
> RPM (Bruxelles) 0415.497.718. 
> Citibank, Brussels, account 570/1031255/09
> 
> This e-mail and any attachments may contain confidential material for the 
> sole use of the intended recipient(s). Any review or distribution by others 
> is strictly prohibited. If you are not the intended recipient, please contact 
> the sender and delete all copies.
> 

_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to