addubuntu10.04

HowtodecideLinuxKernelforEmbeddedProductsTsugikazuSHIBATANEC20,Feb.
2013EmbeddedLinuxConference2013Parc55@SANFRANCISCOAgendaPointstobeconsideredtodecideLinuxkernelversionKeyactivitiesofLTSIPointstobeconsideredtodecidethekernelversionTechnicalaspectsStabilityMaintenanceCost…TechnicalaspectsPerformanceMemoryBatterylifeRealtimenestsConnectability…TechnicalaspectsPerformanceMemoryBatterylifeRealtimenestsConnectability…Technicalaspectsareheavilydependsonkerneldevelopmentinthecommunity.
WeshouldlookatthecommunityotherwisewecannotchooserightversionofthekernelLinuxkernel:releasedate,#offilesandlinesVersionReleasedate#ofFiles#ofLines3.
82013-2-1941,52016,416,967(+1.
4%)3.
72012-12-1140,90516,191,784(+1.
4%)3.
62012-10-139,73315,868,122(+1.
7%)3.
52012-7-2139,09615,596,464(+1.
4%)3.
42012-5-2238,56615,383,946(+1.
4%)3.
32012-3-1938,08215,166,160(+1.
1%)3.
22012-1-537,61714,998,737(+1.
5%)3.
12011-10-2837,08514,770,555500Filesadded,200,000LinesofcodeaddedforaversionReleased60-70daysLinuxkernel:Dateforrelease0204060801001203.
13.
23.
33.
43.
53.
63.
73.
8StabilityOlderkernelisnotalwaysstableLatestkernelisnotalwaysstable–Communitydevelopmentisalways"Releaseearly,Releaseoften"–Manydevelopersarereviewingandchangingthecode–SolvingtheproblemanddevelopingfeaturesarealwaysforthelatestversionofmainlineStabilityOlderkernelisnotalwaysstableLatestkernelisnotalwaysstable–Communitydevelopmentisalways"Releaseearly,Releaseoften"–Manydevelopersarereviewingandchangingthecode–SolvingtheproblemanddevelopingfeaturesarealwaysforthelatestversionofmainlineFortheproducts,weneedtobackportlatestfeaturetotheproductionkernelWeneedtowatchthedevelopmentcommunitytounderstandwhatishappeningMaintenance–bugandsecurityfixesNumberofbugswillbefoundafterthekernelreleaseNumberofsecurityproblemwillalsobefoundafterthekernelreleaseAllsuchproblemsarefixedinthelatestkernelversionMaintenance–bugandsecurityfixesNumberofbugswillbefoundafterthekernelreleaseNumberofsecurityproblemwillalsobefoundafterthekernelreleaseAllsuchproblemsarefixedinthelatestkernelversionWeshouldwatchthecommunityandeverybugsandsecurityfixesshouldbebackporttotheproductionkernel.
Ifyouwilllostthebackport,yourproductincludessecurityholeandbugs.
Thatwillbeacompany'sriskMaintenance–in-housepatchEveryonehaveownchangesasin-housecode–Sometimefixesthebugsandaddnicefeatures–Butmostofsuchchangesarestayin-houseKerneldevelopmentismovingveryfastandchangingitscodeSo,incaseofnewproductdevelopment,in-housecodemaynotbeabletoapplytothenewertargetkernelMaintenance-in-housepatchIn-housepatchportingprocessWhileeverysinglein-hosepatchesifapatchcannotapplytothetargetkernelInvestigatethereasonrewritethepatchfortargetkerneltestthepatchonthetargetkernelMaintenance-in-housepatchIn-housepatchportingprocessWhileeverysinglein-hosepatchesifapatchcannotapplytothetargetkernelInvestigatethereasonrewritethepatchfortargetkerneltestthepatchonthetargetkernelReasonmaydependsonforbothin-housepatchandkernelitselfMaintenance-in-housepatchIn-housepatchportingprocessWhileeverysinglein-hosepatchesifapatchcannotapplytothetargetkernelInvestigatethereasonrewritethepatchfortargetkerneltestthepatchonthetargetkernelReasonmaydependsonforbothin-housepatchandkernelitselfEngineerwhowrotethepatchmaynotintheteamMaintenance-in-housepatchIn-housepatchportingprocessWhileeverysinglein-hosepatchesifapatchcannotapplytothetargetkernelInvestigatethereasonrewritethepatchfortargetkerneltestthepatchonthetargetkernelReasonmaydependsonforbothin-housepatchandkernelitselfEngineerwhowrotethepatchisnotintheteamNeedreviewthepatchasthecorrectnessMaintenance-in-housepatchIn-housepatchportingprocessWhileeverysinglein-hosepatchesifapatchcannotapplytothetargetkernelInvestigatethereasonrewritethepatchfortargetkerneltestthepatchonthetargetkernelReasonmaydependsonforbothin-housepatchandkernelitselfEngineerwhowrotethepatchisnotintheteamNeedreviewthepatchasthecorrectnessNeedtocreatetestingenvironmentagainMaintenance-in-housepatchIn-housepatchportingprocessReasonmaydependsonforbothin-housepatchandkernelitselfEngineerwhowrotethepatchisnotintheteamNeedreviewthepatchasthecorrectnessNeedtocreatetestingenvironmentagainWhileeverysinglein-hosepatchesifapatchcannotapplytothetargetkernelInvestigatethereasonrewritethepatchfortargetkerneltestthepatchonthetargetkernelPatchportingworkscontinuefor#ofpatchesThesepatchportingworkcontinueforfutureproductswheneverin-housecodeexistsCostDevelopmentcostMaintenancecostHW/ProductcostSales/Marketingcost…CostDevelopmentcost–Specificapplicationormiddleware–Tuningforoverallsystem–Specificdriverforkernel–PatchportingtonewerkernelMaintenancecost–Backportingbugsandsecurityfixes–FixesforownapplicationandmiddlewareHW/ProductcostSales/MarketingcostSummaryProductdevelopmentisdeeplydependingonhowengineersareparticipatingthetothecommunity–Watchthedevelopmentstatus–Howthebugsandsecurityproblemsarefixed–In-housecodeneedtobemergedintoupstream–Decreasethedevelopmentcost–ShareinformationamongtheengineerswillalsodecreasethedevelopmentcostLTSI:KeyactivitiesProvideaindustrymanagedkernelandmaintainLongtermstablyProvideacommonplaceforembeddedindustryProvideplacetosupportupstreamactivityLTSI:IndustrymanagedkernelLTSIdefinescommonkerneleveryyearandmaintainsfor2yearsLTSIadoptscommunityLongtermkernelasabase.
Therefore,bug/securityfixesfromupstreamareautomaticallyappliedtoLTSI.
LTSIkernel=longterm+additionalpatchesAfter2yearstermfinished,possibletotakeovermaintenanceforlongertermCommunity'slongtermkernelsandItsconsumers2.
6.
27:SUSE112.
6.
32:SUSE11SP1/RHEL6/Ubuntu10.
04LTS2.
6.
34:WindRiverLinux2.
6.
35:Embeddedusage,Android(GingerBread)3.
0:LTSI,Android(IceCreamSandwich),SUSE11SP23.
2:Debian7,Bunt12.
04LTS3.
4:LTSI,Android(Jellybean)LTSI:CommonplaceLTSIprovidestheplacetoshareinformationandexperienceamongindustry–Mailinglisttoshareproblemanddiscusshowtosolve–OpenWorkshoptosharestatusamongtheindustry–Closedmeeting:ICM(IndustryContactMeeting)formoredeeperF2FdiscussionSharetheinformationwillreducethedevelopmentcostOpenWorkshopFebruary21,20133:00pm-5:00pmatHearstRoom,4thFloor,Park55HotelTheworkshopwillcover:–BriefUpdatesofLTSI–Updatesfromapartnerproject:Doctor–Discussiononafterreleasepatchacceptancepolicy–DiscussiononSuperLongTermSupport(over2yearssupport)–DiscussiononthenextLTSIreleaseLTSI:SupportupstreamactivityDeveloperintheembeddedindustryneedtoknowhowtoworkwithcommunityLTSIprovideshelpupstreamactivities–Providesuggestionhowtheirpatchescanbemergedintoupstream–Reviewanddiscussionforproposedpatchestobemerged–ManyofdiscussionunderwayMergingpatchestoupstreamisalsoreducethecostofeachcompaniesLTSIUseCaseProgramLTSIwouldliketoexpandusecaseWewouldaskyoutoportLTSItoyourpreferredOS–Android,CyanogenMOD,FirefoxOS–Gentoo,OpenWRT,XBMC,GeeXBoX–Debian,Ubuntu,Fedora,OpenSUSEforARMWewillhelpyouractivitieswithprovidingBoardHWandthatwillbeusedbyyourselfaftertheportingfinishedYouneedtowriteyourporingreporttoeLinuxWikiYouneedtosendpatchtoLTSImailinglistifyouhavechangedDetailscanbediscussedatLTSIBooth6pmtodayHowyoucanparticipateLTSIFollowonTwitteraccount:@LinuxLTSIWeb:http://ltsi.
linuxfoundation.
orgMailinglist:https://lists.
linuxfoundation.
org/mailman/listinfo/ltsi-devGittree:http://git.
linuxfoundation.
org/p=ltsi-ernel.
git;a=summary2930THANKYOU