User Tools

Site Tools


eg-gap_genivi_yocto_tizenivi_gap_analysis

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
eg-gap_genivi_yocto_tizenivi_gap_analysis [2015/10/14 04:43]
mbc
eg-gap_genivi_yocto_tizenivi_gap_analysis [2015/10/14 10:19] (current)
mbc
Line 1: Line 1:
 ====== GENIVI/​Yocto/​Tizen IVI gap analysis ====== ====== GENIVI/​Yocto/​Tizen IVI gap analysis ======
-(as of 2015/10/13)+source : **IoT.bzh** ​(as of 2015/10/13) 
 + 
 +**Original document :** [[http://​iot.bzh/​download/​public/​2015/​Audit_on_GENIVI_components_in_AGL_Phase-1.pdf|Audit_on_GENIVI_components_in_AGL_Phase-1.pdf]] 
 + 
 +**Appendix :** [[http://​iot.bzh/​download/​public/​2015/​Audit_on_GENIVI_components_in_AGL_Phase-1_ANNEX.pdf|Audit_on_GENIVI_components_in_AGL_Phase-1_ANNEX.pdf]] 
 +----
  
 ===== Introduction ===== ===== Introduction =====
Line 21: Line 26:
   * [[http://​git.yoctoproject.org/​cgit/​cgit.cgi/​poky/​log/?​h=dizzy|Poky 1.7 '​Dizzy'​]]   * [[http://​git.yoctoproject.org/​cgit/​cgit.cgi/​poky/​log/?​h=dizzy|Poky 1.7 '​Dizzy'​]]
   * [[http://​git.openembedded.org/​meta-openembedded/​log/?​h=dizzy|OpenEmbedded 1.7 '​Dizzy'​]]   * [[http://​git.openembedded.org/​meta-openembedded/​log/?​h=dizzy|OpenEmbedded 1.7 '​Dizzy'​]]
 +
 +----
  
 ===== GENIVI Components ===== ===== GENIVI Components =====
Line 49: Line 56:
 | glib-networking ​      ​| ​ 2.38.0 ​  ​| ​ 2.38.0 ​  ​| ​ 2.38.0 ​   |  ?  | Network subset of glib library requiring additional dependencies | | glib-networking ​      ​| ​ 2.38.0 ​  ​| ​ 2.38.0 ​  ​| ​ 2.38.0 ​   |  ?  | Network subset of glib library requiring additional dependencies |
  
-[1] : maintained in Poky, but not the default version +[1] : maintained in Poky, but not the default version ​\\
 [2] : forked and maintained in GENIVI [2] : forked and maintained in GENIVI
  
Line 101: Line 107:
   * Parted   * Parted
  
-**Side notes** +__Side notes__ : As a side note, recent GENIVI build instructions [[http://​git.yoctoproject.org/​cgit/​cgit.cgi/​meta-ivi/​tree/​README.md|do not contain the GPLv3 mention anymore]]. Does this mean that GENIVI now allows GPLv3 packages ? A formal clarification on GPL licensing policies would be more than welcome.
-As a side note, recent GENIVI build instructions [[http://​git.yoctoproject.org/​cgit/​cgit.cgi/​meta-ivi/​tree/​README.md|do not contain the GPLv3 mention anymore]]. Does this mean that GENIVI now allows GPLv3 packages ? A formal clarification on GPL licensing policies would be more than welcome.+
  
-**Suggestions** +__Suggestions__ : Whether GENIVI would allow GPLv3, it would then be possible to switch to more recent versions of many packages (except for Gettext).
-Whether GENIVI would allow GPLv3, it would then be possible to switch to more recent versions of many packages (except for Gettext).+
 If it does not, then we have to keep these older versions until a suitable replacement is found. If it does not, then we have to keep these older versions until a suitable replacement is found.
 Potential replacements include : Potential replacements include :
-  ​* **Bash :** [[http://​gondor.apana.org.au/​~herbert/​dash/​|Dash]] - [[http://​www.kornshell.com/​|ksh]] +  * Bash : [[http://​gondor.apana.org.au/​~herbert/​dash/​|Dash]] - [[http://​www.kornshell.com/​|ksh]] 
-  ​* **Gawk :** [[http://​www.cs.princeton.edu/​~bwk/​btl.mirror|BWK awk]]  +  * Gawk : [[http://​www.cs.princeton.edu/​~bwk/​btl.mirror|BWK awk]]  
-  ​* **Coreutils :** [[http://​www.landley.net/​toybox|Toybox]] +  * Coreutils : [[http://​www.landley.net/​toybox|Toybox]] 
-  ​* **Parted :** [[http://​sourceforge.net/​projects/​gptfdisk/​|GPT fdisk]]+  * Parted : [[http://​sourceforge.net/​projects/​gptfdisk/​|GPT fdisk]] 
 +\\
  
 == Package misalignment == == Package misalignment ==
Line 119: Line 124:
 The Tizen IVI version is a bit older. As there is no technical explanation,​ this is most likely to be a mistake or an oversight. Updating should be straightforward. ​ The Tizen IVI version is a bit older. As there is no technical explanation,​ this is most likely to be a mistake or an oversight. Updating should be straightforward. ​
  
-**Suggestions** ​Stick to the Yocto/​OpenEmbedded version.+__Suggestions__ : Stick to the Yocto/​OpenEmbedded version.
  
 +\\
 == Custom patches == == Custom patches ==
  
Line 128: Line 134:
 The patches are security fixes, one of which (CVE 2015-1315 for Unzip) was released subsequently to TIzen IVI's latest release (mid-February 2015). Using these Yocto-patches versions is a no-brainer. The patches are security fixes, one of which (CVE 2015-1315 for Unzip) was released subsequently to TIzen IVI's latest release (mid-February 2015). Using these Yocto-patches versions is a no-brainer.
  
-**Suggestions** ​Keep the Yocto versions, with custom patches.+__Suggestions__ : Keep the Yocto versions, with custom patches.
  
 +\\
 == Nonexistent packages == == Nonexistent packages ==
  
 There are some packages which simply do not have any correspondence between distributions. This mostly happens for "​administrative"​ packages (i.e. used for compilation or production of the final image) or for strategical reasons. There are some packages which simply do not have any correspondence between distributions. This mostly happens for "​administrative"​ packages (i.e. used for compilation or production of the final image) or for strategical reasons.
  
-= Packages present in Tizen IVI, but NOT in GENIVI/​Yocto =+\\ 
 +== Packages present in Tizen IVI, but NOT in GENIVI/​Yocto ​==
   * Procps-ng : "​procps"​ is the traditional package providing /​proc-related command-line tools (ps, top, skill...). However, it has not been updated for years and requires lots of custom patches for today'​s uses ; hence why Tizen IVI prefers to use its "​procps-ng"​ fork instead.   * Procps-ng : "​procps"​ is the traditional package providing /​proc-related command-line tools (ps, top, skill...). However, it has not been updated for years and requires lots of custom patches for today'​s uses ; hence why Tizen IVI prefers to use its "​procps-ng"​ fork instead.
 Yocto 1.7, though, unfortunately does not provide this package. Yocto 1.7, though, unfortunately does not provide this package.
  
-**Suggestions** ​Keep the Tizen IVI version, store it in the AGL tree, and submit it to the upstream Yocto project meanwhile. This way, future AGL releases may be able to use Procps-ng directly without maintaining the packaging.+__Suggestions__ : Keep the Tizen IVI version, store it in the AGL tree, and submit it to the upstream Yocto project meanwhile. This way, future AGL releases may be able to use Procps-ng directly without maintaining the packaging.
  
-= Packages present in GENIVI/​Yocto,​ but NOT in Tizen IVI =+\\ 
 +== Packages present in GENIVI/​Yocto,​ but NOT in Tizen IVI ==
   * Quota   * Quota
   * Libcgroup   * Libcgroup
Line 151: Line 160:
   * "​tcp-wrappers",​ "​os-release"​ and "​volatile-binds"​ are administrative packages used mostly for OS image preparation and boot. For instance, "​os-release"​ customizes the "/​etc/​os-release"​ file, used by most tools to identify the distribution ; Tizen IVI does it too, but in its "​tizen-release"​ package.   * "​tcp-wrappers",​ "​os-release"​ and "​volatile-binds"​ are administrative packages used mostly for OS image preparation and boot. For instance, "​os-release"​ customizes the "/​etc/​os-release"​ file, used by most tools to identify the distribution ; Tizen IVI does it too, but in its "​tizen-release"​ package.
  
-**Suggestions** ​Keep "​quota",​ "​libcgroup"​ and "​os-release"​ from Yocto 1.7. Remove use of "​tcp-wrappers"​ and "​volatile-binds"​ until it proves itself useful. "​os-release"​ could be replaced by a specific package named "​agl-release"​.+__Suggestions__ : Keep "​quota",​ "​libcgroup"​ and "​os-release"​ from Yocto 1.7. Remove use of "​tcp-wrappers"​ and "​volatile-binds"​ until it proves itself useful. "​os-release"​ could be replaced by a specific package named "​agl-release"​. 
 + 
 +----
  
 ===== GENIVI Yocto layer ("​meta-ivi"​) ===== ===== GENIVI Yocto layer ("​meta-ivi"​) =====
Line 166: Line 177:
 | audiomanager_6.2.bb ​      ​| ​ Required by AGL 1.0 specification ​   | GENIVI System - Audio Manager | | audiomanager_6.2.bb ​      ​| ​ Required by AGL 1.0 specification ​   | GENIVI System - Audio Manager |
 | audiomanager_git.bb ​      ​| ​ Required by AGL 1.0 specification ​   | GENIVI System - Audio Manager | | audiomanager_git.bb ​      ​| ​ Required by AGL 1.0 specification ​   | GENIVI System - Audio Manager |
-| common-api-c++_2.1.6-p1.bb ​      | | GENIVI Libraries - Misc (IPC) | +<​nowiki>​common-api-c++_2.1.6-p1.bb</​nowiki> ​      | | GENIVI Libraries - Misc (IPC) | 
-| common-api-c++-dbus_2.1.6-p6.bb ​      | | GENIVI Libraries - Misc (IPC) |+<​nowiki>​common-api-c++-dbus_2.1.6-p6.bb</​nowiki> ​      | | GENIVI Libraries - Misc (IPC) |
 | dlt-daemon_2.11.1.bb ​      ​| ​ Required by AGL 1.0 specification ​  | GENIVI Libraries - Logging daemon | | dlt-daemon_2.11.1.bb ​      ​| ​ Required by AGL 1.0 specification ​  | GENIVI Libraries - Logging daemon |
 | encryptfs-utils_104.bb ​      ​| ​ GENIVI configuration - disable NSS dependency ​  | Base - Utilities | | encryptfs-utils_104.bb ​      ​| ​ GENIVI configuration - disable NSS dependency ​  | Base - Utilities |
Line 216: Line 227:
 <​code>#​ find meta-ivi -name *.bbappend | xargs -n 1 basename | sort</​code>​ <​code>#​ find meta-ivi -name *.bbappend | xargs -n 1 basename | sort</​code>​
  
 +\\
 === Explanation of motivations === === Explanation of motivations ===
  
 == AGL 1.0 specification compliance (original packages) == == AGL 1.0 specification compliance (original packages) ==
  
-Most of the non-Yocto ("​specific"​) packages implement parts of the AGL 1.0 specification,​ for which there is no notable implementation in the upstream field nor in Tizen IVI.+Most of the non-Yocto ("​specific"​) packages implement parts of the [[https://​www.automotivelinux.org/​sites/​agl/​files/​pages/​files/​agl_spec_v1.0_final_0.pdf|AGL 1.0 specification]], for which there is no notable implementation in the upstream field nor in Tizen IVI.
  
 Concerned sections of the specification are studied further below (see [AGL 1.0 specification matching]), but here is a short summary : Concerned sections of the specification are studied further below (see [AGL 1.0 specification matching]), but here is a short summary :
Line 239: Line 251:
   * qt4-embedded : **enable the QML/Qt graphical widget definition language**   * qt4-embedded : **enable the QML/Qt graphical widget definition language**
   * ... and other negligible things.   * ... and other negligible things.
 +
 +----
  
 ===== Suggestions for an AGL integration workflow ===== ===== Suggestions for an AGL integration workflow =====
Line 301: Line 315:
  
 4) Write instructions on how to generate the final image using this repository. 4) Write instructions on how to generate the final image using this repository.
 +
 +----
  
 ===== Advanced study ===== ===== Advanced study =====
Line 529: Line 545:
 __Proposal__ : use libav from Yocto. Provide Yocto configuration options to disable restricted codecs in development builds. __Proposal__ : use libav from Yocto. Provide Yocto configuration options to disable restricted codecs in development builds.
  
 +** Personal Information Manager (AGL§5.2.7)**
 +
 +The specification requires a service able to centralize personal data : appointments,​ reminders...
 +
 +Tizen used the "​evolution-data-server"​ (eds) package together with libfolks for this purpose.
 +
 +__Proposal__ : use the evolution-data-server package from Tizen.
 +
 +** Smart Device Link (AGL§5.2.8.2)**
 +
 +The specification requires Smart Device Link capabilities,​ also known as remote control from a smartphone (for capable applications only).
 +
 +There is no Yocto package implementing this ; **Tizen IVI**, though, contains a "​smartdevicelink"​ package, which responds to the requirements.
 +
 +__Proposal__ : use **smartdevicelink** from Tizen IVI.
 +
 +** Speech Services (AGL§5.2.9)**
 +
 +The specification requires "//​voice recognition and synthesis//"​.
 +
 +There is no dedicated package in Yocto. **Tizen IVI**, however, contains the dedicated "​**festival**"​ library, the dedicated "​**sphinx**"​ library, and even a dedicated "​**speech-recognition**"​ daemon, which may however need some modifications.
 +
 +__Proposal__ : use the festival/​sphinx packages from Tizen IVI. Evaluate the speech-recognition daemon of Tizen IVI.
 +
 +=== AGL specification compliance in GENIVI / Upstream projects / Tizen ===
 +
 +In this chapter, for each package group listed in §5.1[Global gap : Tizen IVI / Yocto 1.7], we try to find a match in GENIVI, Upstream and Tizen IVI.
 +
 +** GUI resource management**
 +
 +The Policy Manager (AGL§4.1.3.1.2) requires the following :
 +  * Weston 1.7, for IVI-Shell : in Yocto 1.8 ;
 +  * Policy manager : Tizen IVI contains Murphy, which fulfills the requirement.
 +
 +** Preinstalled applications**
 +
 +Only a HomeScreen is mandatory (AGL§4.1.3.1.2).
 +
 +Tizen IVI contains 2 packages fulfilling the requirement : ICO and Modello,
 +  * ICO is native, whereas Modello is HTML5 ;
 +  * Both are not heavily maintained anymore, though.
 +
 +__Proposal__ : choose one and resume its maintenance.
 +
 +** Screen Sharing**
 +
 +Miracast (AGL§5.1.13.1.2) requires an implementation.
 +
 +Tizen IVI had WiDi, which fulfills the requirement,​ but it was not included due to royalty fees issues.
 +
 +**Digital Multimedia Server**
 +
 +DLNA (AGL§5.1.13.1.3) requires the following :
 +  * Yocto 1.7 contains Dleyna 0.4.0, which fulfills the requirement.
 +
 +**Login and security**
 +
 +From AGL§4.1.6.7 : login/​password is mandatory, NFC and biometric identification COULD be supported.
 +
 +Yocto 1.7 contains Neardal, and Tizen IVI contains nfc-manager-neard. Both are needed in order to fulfill the requirement. Adaptation is needed for nfc-manager-neard.
 +
 +**Applications**
 +
 +An Online Store is needed (AGL§3.1.8.3),​ with support for secure communications.
 +
 +Local databases and multi-user support are needed for applications.
 +
 +**Sound**
 +
 +A Sound Manager is needed (AGL§4.1.4).
 +
 +----
 +
 +===== CONCLUSION =====
 +
 +The gaps between Tizen-IVI and Genivi packages as extracted from Genivi mailing list and Yocto repository originate from 3 main motivations:​ license dependency on GPLV3, specific requirements addressed by Genivi or simplicity of construction.
 +
 +For most of the packages, it should be relatively simple to make a pragmatic choice of which version or a given package should be used or not. For some others nevertheless due to complex dependencies,​ this decision might me more political than technical.
 +
 +Going further and aiming at AGL-1.0 compliance, it looks obvious that even by collecting every packages from Tizen, Genivi and Yocto some functionality would still miss.
 +
 +In order to move forward: first basic version conflict of identical packages in between Yockto/​Genevi/​Tizen should be cleared out. Secondly the AGL architecture group and steering comity should address missing functionality and choose technologies they would like to use to address those requirements.
  
 +----
 +(see [[http://​iot.bzh/​download/​public/​2015/​Audit_on_GENIVI_components_in_AGL_Phase-1_ANNEX.pdf|Appendix]] for additional data)//
eg-gap_genivi_yocto_tizenivi_gap_analysis.1444797792.txt.gz · Last modified: 2015/10/14 04:43 by mbc