EmbeddedLinux&& Nowandthefuture& withLTSI · 2017. 12. 14. · EmbeddedLinux&& Nowandthefuture& withLTSI Hisao&Munakata, Renesas& Tsugikazu&SHIBATA,&NEC& 27.&March&2014& Collaboraon&Summit

Embedded Linux Now and the future

with LTSIHisao Munakata, Renesas Tsugikazu SHIBATA, NEC

27. March 2014 CollaboraDon Summit

Key ac:vi:es of LTSI Long Term Support Ini:a:ve

p  Provide a industry managed kernel and maintain Long term based on LTS

p  Provide a common place for embedded industry to share informaDon: Mailing list, Workshop …

p  Provide place to support upstream acDvity : Help industry developer

LTSI: Industry managed kernel

•  LTSI defines common kernel every year and maintains for 2 years

•  LTSI adopts community Long term kernel as a base. Therefore, bug/security fixes from upstream are applied.

•  LTSI kernel = long term + addiDonal patches •  AUer 2 years term finished, possible to take over maintenance for longer term

LTSI: Common place

•  LTSI provides the place to share informaDon and experience among industry – Mailing list to share problem and discuss how to solve

– Open Workshop to share status – Closed meeDng for more deeper F2F discussion

•  Share the informaDon will reduce the development cost

LTSI: Support upstream ac:vity

•  Developer in the embedded industry may wanted to know how to work with community

•  LTSI provides help upstream acDviDes –  Provide suggesDon, review and discussion for proposed patches to be merged

– Many of discussion under way •  Merging patches to upstream is also reduce the cost of each companies

LTSI history•  Established 2011 in Prague •  We have been released :

– 2011: 3.0 – 2012: 3.4 – 2013: 3.10

•  LTSI = LTS + Industry demanded patch More details about LTSI-‐3.10 is discussed later

White paper: Economic value of LTSI

7

Maintenance cost of single LTS version is about 3M$

http://www.linuxfoundation.org/publications/workgroup/value-of-ltsi

At the product planning using Linux•  Kernel selecDon

–  Latest and Greatest – Most stable and Secure

•  IniDal cost –  Roll up by myself –  Use pre-‐exisDng kernel

•  Running cost – Maintain everything by myself –  Receive bugfix/security fix from community

•  Eco system –  Tools, share informaDon among industries

ü  Upstream Kernel ü  Soc Kernel ü  LTS Kernel ü  LTSI Kernel

Comparison among KernelsKernel source Ini:al cost Running Cost Eco System

Upstream Kernel Latest and Greatest

Roll up myself, validate everything

Should watch bug /security fix in upstream and back port them

Yocto eco system can be used

SoC kernel Depend on SoC

Depend on SoC or validate everything

Depend on SoC, but mostly no support Watch bug/security fix and back port them

Depend on SoC

LTS Kernel Stable and Secure

Validate everything on latest LTS

Be able to get LTS patches

LTSI Kernel LTS+add on

LTS +addiDonal patches +Share informaDon

LTS + share informaDon

Yocto Eco system can be used Be able to ask LTSI

Case of Android

•  6 month release cycle to 12-‐18 month •  All the patches merged into mainline and then becomes no dependency on kernel version

•  ICS : 3.0, Nexus 4=Jelly bean: 3.4 Nexus5=Kitkat: 3.4 •  LTSI is keep sync with Google Android

Case of Google’s move

•  Open AutomoDve Alliance – Established: 2014/2 – With Audi, GM, Honda, Hyundai, NVIDIA

•  Bring the best of Android into Automotive •  Try to enable better integration between

Cars and Android devices •  By end of 2014

Case of Google’s move

•  Android ware – Announced March 2014

•  LTSI will keep sync with Google android Information that moves with you Small, powerful devices, worn on the body. Useful information when you need it most. Intelligent answers to spoken questions. Tools to help reach fitness goals. Your key to a multiscreen world.

Automo:ve Grade Linux

•  Established 2012, Toyota, Nissan, Jaguar Land rover and many of Tier one companies

•  Announcement of reference plaeorm already there with specificaDon and binary based on Tizen IVI

•  Expected life Dme will be around 10 years

Automotive Grade Linux (AGL) is an open collaboration between contributors from the Automotive Industry, the Communications Industry, Semiconductor Industry, Academia, Community and others, combining open source components into a core operating system software stack suitable for automotive applications.

Case of Social Infrastructure Solu:on•  Increasing requirements and possibility for Social infrastructural service –  Arena soluDon for sports event

•  Major Dme, distance../ provide personal infor/ deliver live view with high density resoluDon

–  Control system for social infrastructure •  Dam/Power plant/traffic control/train control

–  AdopDon for more criDcal poDon being considered •  Very long term lifeDme: run over 10 years •  Real Dme-‐ness maybe important in some case •  Reliability is one of key aspects

Case of Internet of Things•  AllSeen alliance had been established December 2013. – Devices can be connected transparent ways to enable seamless sharing informaDon.

– Based on Wifi, Bluetooth, PLC or any other connecDon

•  There will be nearly 26 Billion devices on IoT by 2020 (Gatner, 2013/12)

•  Kernel should be very low footprint with secure and stable

Comparison of new opportunityConsumer Electronics

IoT Social infrastructure

Life Dme 2 years 2-‐5 years Over 10 yearsReliability demand

Normal Normal Hard

Stability /Security demand

Normal Normal Hard

Real Dme some case Nice to have Needed in case CharacterisDcs

Mobile device

Specific role for devices

Depend on Use case

Conclusion

•  Possibility of “Embedded” Linux adopDon is expanding with increasing use case of new business opportunity

•  Stable and reliable Linux eco system is fundamental porDon now and the future

18

THANK YOU

How you can par:cipate LTSI•  Follow on Twimer account:

@LinuxLTSI •  Web:

hmp://ltsi.linuxfoundaDon.org

•  Mailing list: hmps://lists.linuxfoundaDon.org/mailman/lisDnfo/ltsi-‐dev

•  Git tree : hmp://git.linuxfoundaDon.org/?p=ltsi-‐ernel.git;a=summary

19

Why you should consider adopting LTS ?LTSI 3.10 development result review

Conclusion

.

......

Embedded Linux: Now and the future (part 2)LTSI kernel development updates

Tsugikazu Shibata, Hisao Munakata

Linux Foundation Consumer Electronics working group

March 27th 2014

1 / 22 Tsugikazu Shibata, Hisao Munakata Embedded Linux: Now and the future (part 2)


Conclusion

.. Who am I ? (Munakata)

From embedded SoC provider company RenesasLinux Foundation CE1 working Gr. Steering committeemember, LF/CEWG Architecture Gr. co-chairOne of LF/CEWG LTSI2 project initial proposerAt my company, I had been encouraging my teamdevelopers to send a patches upstreamAlso I have supported various CE customers who developdigital-TV, Blu-ray recorder and Smart-phone

1CE = consumer electronics2LTSI =Long Term Support Initiative



Conclusion

.. LTSI kernel update @ February 24, 2014

LTSI 3.0.79 --> 3.0.101 (EOL)LTSI 3.4.46 --> 3.4.81 (update)



Conclusion

kernel release mechanismMessages from Greg KHWhoops, Is it too late ?

Why you should consider adopting LTS ?



Conclusion


.. Upstream kernel @kernel.org

.

......You can find 1)latest released, 2)under development(=mainline, next), and several stable kernels



Conclusion


.. The release record of 3.0 series upstream kernelversion release date durationv3.0 2011-07-21v3.1 2011-10-24 95 daysv3.2 2012-01-04 72 daysv3.3 2012-03-18 74 daysv3.4 2012-05-20 63 daysv3.5 2012-07-21 62 daysv3.6 2012-09-30 71 daysv3.7 2012-12-10 71 daysv3.8 2012-02-18 70 daysv3.9 2013-04-28 69 daysv3.10 2013-06-30 63 daysv3.11 2013-09-02 64 daysv3.12 2013-11-15 74 daysv3.13 2014-01-21 67 days

.

......Release happened regularly at around every 70 days6 / 22 Tsugikazu Shibata, Hisao Munakata Embedded Linux: Now and the future (part 2)


Conclusion


.. However, not all kernels are maintained for longterm

version maintenance statusv3.0 was longterm (3.100) -> now moved to EOLv3.1 maintained till 3.1.9, then now EOLv3.2 longterm (3.2.55), kept maintained (by Debian)v3.3 maintained till 3.3.8, then now EOLv3.4 longterm (3.4.84), kept maintainedv3.5 maintained till 3.5.7, then now EOLv3.6 maintained till 3.6.11, then now EOLv3.7 maintained till 3.7.10, then now EOLv3.8 maintained till 3.8.13, then now EOLv3.9 maintained till 3.9.11, then now EOLv3.10 longterm stable (3.10.34), kept maintainedv3.11 maintained till 3.11.10, then now EOLv3.12 stable release (3.12.14) till 3.13 release



Conclusion


.. Stable release include MUST APPLY essential fixes

version fixesv3.0 -> v3.0.99 3,907v3.1 -> v3.1.9 647v3.2 -> v3.2.55 4,558v3.3 -> v3.3.8 698v3.4 -> v3.4.84 3,909v3.5 -> v3.5.7 816v3.6 -> v3.6.9 676v3.7 -> v3.7.10 718v3.8 -> v3.8.13 996v3.9 -> v3.9.11 746v3.10 -> v3.10.34 2,425v3.11 -> v3.11.10 677v3.12 -> v3.12.14 1,378



Conclusion


.. Longterm stable (LTS) kernel release cadence.Target kernel selection rules..

......

Maintainer will choose one LTS version per yearMaintain it for 2 years from its original releaseLTSI-3.0 is moved to EOL when 3.10 became new LTSThen, we have 2 LTS kernels versions like 3.4 and 3.10



Conclusion


.. LTS/LTSI maintainer, Greg says 3.0 moves to EOL

https://lkml.org/lkml/2013/10/13/16010 / 22 Tsugikazu Shibata, Hisao Munakata Embedded Linux: Now and the future (part 2)


Conclusion


.. And, Greg also announced next longterm is 3.10

http://www.linuxfoundation.org/news-media/blogs/browse/2013/08/longterm-kernel-310



Conclusion


.. Upstream kernel 3.10 development (is done)

Whoops, we can not submit our latest device supportcode to 3.0 kernel now! Yes, that is true, because

item datekernel 3.10 merge window open 2013.4.28kernel 3.10 merge window close 2013.5.12kernel 3.10 release 2013.6.30

.

......

As upstream 3.10 patch merge window is already closed,there is no chance to add your code to upstream kernel.Thus a cutting-edge silicon release after development cyclecan not be supported in longterm 3.10 kernel. This might beproblematic for embedded industry Linux adopter.



Conclusion

LTSI 3.10 development resultGovernance

LTSI 3.10 development result review



Conclusion


.. LTSI-3.10 development history

item datekernel 3.10 merge window open 2013.4.28kernel 3.10 merge window close 2013.5.12kernel 3.10 release 2013.6.30Announce of 2013 LTS kernel version 2013.8.4LTSI-3.10 git tree open 2013.9.113.10 becomes LTS (=3.12 release) 2013.11.15LTSI-3.10 merge window open 2013.11.15patch collection period 75 daysLTSI-3.10-rc1 (=merge window close) 2014.1.29validation period 26 daysLTSI-3.10 release 2014.2.24



Conclusion


.. Major contributor for LTSI-3.10

Contributor Patch countDarren Hart (intel) 1,197Simon Horman (for Renesas) 1,122Yoshitake Kobayashi (Toshiba) 123Patrik Jakobsson (for intel) 46Mark Brown (linaro.org) 11Greg Kroah-Hartman (Linuxfoundation) 11Total 2,510



Conclusion


.. Major achievement of LTSI 3.10

LTTngPower efficient workqueuesIntel's BayTrail supportIntel's Minnowboard supportRenesas's R-Car H2/M2 series support backported fromthe latest mainlineXilinx Zynq board support



Conclusion


.. LTSI = community LTS(longterm) + industry extra



Conclusion


.. Yocto and LTSI project coordination is working now



Conclusion


.. Discipline of LTSI project management.

......

Community LTS + industry demanded extra patches.Governed by LF/CEWGFocus on kernel codea, not aiming complete BSPTherefore, can be combined with existing platformbCPU architecture and platform neutralComply with upstream rulescIndustry friendly acceptance (flexible patch forms, etc)Help CE (and others) industry to utilize Linux

adevice drivers are part of kernel, of coursebAndroid, Yocto, Tizen, AGL, WebOS and othersce.g. signed-off-by process



ConclusionResources

Conclusion



ConclusionResources

.. Conclusion

.

......

Correct understanding of the longterm (LTS) cadence isimportant. LF/CEWG develops LTSI version on top ofcommunity longterm kernel. You can gain huge cost reductionif you can fully utilize LTS & LTSI scheme.3.0 longterm maintenance cycle has been moved to EOLand3.10 is the next longterm support target. ALSO, LTSI-3.10was released in February 2014. Now industries can shareLTS-3.10 and LTSI-3.10 kernel.It is too early to determine next LTSI candidate version.However, if you can put device support code (or anything) tocurrent upstream it makes easier for you to use next LTSIkernel. Let's continue upstreaming!



ConclusionResources

.. Resourcesproject web = ltsi.linuxfoundation.orgML

ML subscription =https://lists.linuxfoundation.org/mailman/listinfo/ltsi-devML archives =http://lists.linuxfoundation.org/pipermail/ltsi-dev/ML patchwork =https://patchwork.kernel.org/project/ltsi-dev/list/

git(each patch) = http://git.linuxfoundation.org/?p=ltsi-kernel.git;a=summarydownload (tar ball) =http://ltsi.linuxfoundation.org/downloads/releasestwitter = @LinuxLTSIdocument archives =http://ltsi.linuxfoundation.org/resources


LTSI-CollbSummit2014-finalLTSI-collab2014

Documents

EmbeddedLinux&& Nowandthefuture& withLTSI · 2017. 12. 14. · EmbeddedLinux&& Nowandthefuture& withLTSI Hisao&Munakata, Renesas& Tsugikazu&SHIBATA,&NEC& 27.&March&2014& Collaboraon&Summit