[Dev] [SDK/Emulator] Start testing emulator based on QEMU 2.0

Stanislav Vorobiov s.vorobiov at samsung.com
Tue Apr 29 09:30:11 GMT 2014


Hi, Jinhyung

Ok, thanks, it looks I didn't pulled that.

On 04/29/2014 01:12 PM, Jinhyung Jo wrote:
>  
> 
> Hi, Stanislav
> 
>  
> 
> I'm sorry about your uncomfortable.
> 
> I made a mistake in maru_camera source.
> 
> Please patch with this submit https://review.tizen.org/gerrit/#/c/20167/.
> 
>  
> 
> Thanks.
> 
>  
> 
> ------- *Original Message* -------
> 
> *Sender* : Stanislav Vorobiov<s.vorobiov at samsung.com> Expert Engineer/SRR-Tizen S/W Group/삼성전자
> 
> *Date* : 2014-04-29 17:51 (GMT+09:00)
> 
> *Title* : Re: [Dev] [SDK/Emulator] Start testing emulator based on QEMU 2.0
> 
>  
> 
> Hi,
> 
> Also, on windows, qemu crashes on exiting. I suggest running qemu under gdb always, in that case "on exit crash" errors could be caught early.
> 
> On 04/29/2014 12:48 PM, Stanislav Vorobiov wrote:
>> Hi,
>>
>> Also, on windows, if I add "-device maru_camera_pci" to qemu command line - it crashes in camera code. I
>> didn't study this in detail.
>>
>> On 04/29/2014 12:01 PM, Stanislav Vorobiov wrote:
>>> Hi, SeokYeon
>>>
>>> Regarding e39fc0b88fb99018819129bd3dea9395e9c73071, is moving work_queue to vigs dir necessary ?
>>> I mean, this is shared code, it should be independent of yagl/vigs or whatever.
>>>
>>> On 04/25/2014 05:12 PM, SeokYeon Hwang wrote:
>>>> I forgot something.
>>>>
>>>> @ Stanislav,
>>>> Please check commit e39fc0b88fb99018819129bd3dea9395e9c73071.
>>>> It is modification of VIGS/YaGL codes.
>>>>
>>>> @ Sood and HAXM developers
>>>> Please check commit 92d5793f73c463576a17d6a281cf7b3c8804aea0.
>>>> It is about HAXM sources.
>>>>
>>>> Thanks.
>>>>
>>>> -----Original Message-----
>>>> From: Dev [mailto:dev-bounces at lists.tizen.org] On Behalf Of SeokYeon Hwang
>>>> Sent: Friday, April 25, 2014 10:02 PM
>>>> To: 'Stanislav Vorobiov'; dev at lists.tizen.org
>>>> Subject: Re: [Dev] [SDK/Emulator] Start testing emulator based on QEMU 2.0
>>>>
>>>> Hi, stanislav,
>>>>
>>>> It is working with 3.4 kernel and 3.12 kernel( + your "Intel HDA" patch) on
>>>> all host platforms.
>>>> On windows without "Intel HDA" patch, Kernel 3.12 hang-up is occurred.
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Stanislav Vorobiov [mailto:s.vorobiov at samsung.com]
>>>> Sent: Friday, April 25, 2014 7:09 PM
>>>> To: SeokYeon Hwang; dev at lists.tizen.org
>>>> Subject: Re: [Dev] [SDK/Emulator] Start testing emulator based on QEMU 2.0
>>>>
>>>> Hi, SeokYeon
>>>>
>>>> It's working with kernel 3.12 and on all host platforms ? Or are you testing
>>>> on linux only for now ?
>>>>
>>>> On 04/25/2014 01:17 PM, SeokYeon Hwang wrote:
>>>>> Hi, all.
>>>>>
>>>>>  
>>>>>
>>>>> A emulator based on QEMU 2.0 is working now. It is in tizen_qemu_2.0
>>>> branch.
>>>>>
>>>>> 1.     Based on QEMU 2.0.
>>>>>
>>>>> 2.     Applied the arguments that are modified recently. (You need latest
>>>> emulator-manager to test.)
>>>>>
>>>>> 3.     Removed all "implicit function declaration" warnings.
>>>>>
>>>>> 4.     Compiler options appended : -Werror=implicit-function-declaration
>>>> -Werror=implicit-int
>>>>>
>>>>>  
>>>>>
>>>>> These are known issues.
>>>>>
>>>>> 1.     Attach "SDCard" is not working.
>>>>>
>>>>> 2.     Enabled "Host keyboard" is not working.
>>>>>
>>>>> They should be fixed ASAP.
>>>>>
>>>>>  
>>>>>
>>>>> I think it can be merged 5 May (same day new kernel applied), If there
>>>>> are
>>>> no critical issues.
>>>>>
>>>>>  
>>>>>
>>>>> Please tell me any opinion about this.
>>>>>
>>>>>  
>>>>>
>>>>> Thanks.
>>>>>
>>>>>  
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Dev mailing list
>>>>> Dev at lists.tizen.org
>>>>> https://lists.tizen.org/listinfo/dev
>>>>>
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> Dev at lists.tizen.org
>>>> https://lists.tizen.org/listinfo/dev
>>>>
>>>>
>>>
>>
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.tizen.org
> https://lists.tizen.org/listinfo/dev
> 
>  
> 
>  
> 
>  
> 



More information about the Dev mailing list