Hi Dominig, Thanks for all of your assistance so far.
I have a question about how best to integrate the kernel build (and the platform as a whole) for the Renesas and Intel platforms. If both platforms are building the kernel from the same source package, what is the best way to handle the fact that they both require different configurations and build processes? Is it best to test for variable in the spec file and if so, what is the best way to set the variable value? Is setting it in build.conf the best option? I can do this for a local build without too much trouble, but from what I've seen of obs it looks like that means defining a whole new build configuration. Is that the only way to go? Thanks, Damian On 12 September 2014 17:49, Dominig ar Foll (Intel OTC) < [email protected]> wrote: > Le 11/09/2014 17:26, hisao munakata a écrit : > >> >> Personally I have no objection to migrate to 3.14-LTSI for baseline code. >> Possible problem is middleware compatibility and delivery. I will check >> when >> and how we can deliver them using through click-through type easy manner. >> >> Anyway now I can understand your suggestion. I will consider this. >> >> >> Thanks for your comprehension. > > Unfortunately ARM based CPU have always some non open source drivers which > are pain when it come to Kernel upgrade. > Picking up the LTS kernel is the least painful option that we could come > up with. > > The pain point for us at Intel is in the opposite direction as new IA SoC > come with of the shelves support in latest kernel and we will need to > back-port to 3.14. > > Let us know if we can help you in any way to ease your move to 3.14. > > Regards > > Dominig > > _______________________________________________ > IVI mailing list > [email protected] > https://lists.tizen.org/listinfo/ivi >
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
