Title: Samsung Enterprise Portal mySingle

Hi Ning,

    Thank you for your prompt reply.

    Forget to mention that the last info is "system_server[257]: segfault at 0 ip  (null) sp bfd7e16c" error 4 in system_server[8048000+32000]."

    Can you help me to check the issue.

 

    In addition, from Reference_Hardware, Tizen common is support Odroid U3. Now the target is "genericx86". If i want to boot image in Odroid U3, what should i do in detail.

    Thank you very much.

 

    And the git log is:

        commit 4a7b826daea8373bbc2845a49a33fc5be24af5b8
        Author: Patrick Ohly <[email protected]>
        Date:   Fri Jan 23 01:36:12 2015 -0800

        tizen-distro: pull meta-tizen from "master" branch

        As discussed in https://bugs.tizen.org/jira/browse/TC-1964 using
        the "master" branch and not maintaining a "tizen" branch with
        identical content for meta-tizen makes more sense.

    

    

Best wishes

Jianzhong Fang

 

------- Original Message -------

Sender : Wang, Ning W<[email protected]>

Date : 二月 15, 2015 08:55 (GMT+08:00)

Title : RE: [Dev] Boot tizen common image failed

 

<!--[if mso 9]-->

 

Hi,

 

Here is the reference hardware for Tizen Common: https://wiki.tizen.org/wiki/Common#Reference_Hardware. And I don’t think the lack of bluetooth module will cause boot failure.

 

Thanks,

Ning

From: Dev [mailto:[email protected]] On Behalf Of jianzhong fang
Sent: Sunday, February 15, 2015 8:42 AM
To: [email protected]
Cc:
刘春华
Subject: [Dev] Boot tizen common image failed

 

Hi all,

    When i boot the tizen common image which created by Yocto in a desktop by USB, it have some failure.

And one is bluetooth module failure. The desktop is based on X86, and have no bluetooth module.

So i want to check whether it has some special hardware requirements or special computers, not all X86 desktops.

    Thank you.

 

    Best wishes

    Jianzhong Fang

 

 

 

 

 

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

Reply via email to