Close Encounters of the Upstream Resource
Hisao Munakata from Renesas discusses the upstream resource.ion gap issue" was common criticism for the embedded industry that pointed low patch submission rate against other business due to not sharing new kernel code. After we start adopting Android as a common embedded Linux base I think situation is changing now. Because it always comes with pretty fresh version of kernel for each release. Of course this is very good trend to shorten the gap between community work.However it looks like majority of industry developers still could not fully utilize upstream resources as they are not accustomed to such situation. In this session I will conduct an analysis of current production design issues and then try to show some hints with examples how to make better sync to the upstream activity. I hope this will be beneficial for both programmer and manager who designs a product with relatively new kernel code. Hisao Munakata, Renesas Solutions Corp Munakata is an executive manager of Renesas Solutions Corp and he is leading opensource development initiative in Renesas. He had made some talk at previous LinuxCon Japan and Automotive Linux Summit.He has an Architecture Gr. co-chair role in Linux Foundation CEWG and he support LTSI (Long Term Stable kernel Initiative) project in CEWG.LTSI is a brand new long term stable kernel maintenance scheme that support new feature integration as well as security/bug fix of community LTS version kernel to help embedded industry Linux utilization.Renesas has tried to add new device driver code in upstream as much as possible, so that anyone can run latest Linux kernel as a major kernel code contributor company. He support product development team with the help of upstream contributor in Renesas as well. Based on those experience he want to build nice teamwork scheme across upstream and production designer.