Hi Andrew Am 10.03.2016 um 18:53 schrieb Andrew: > Hi. > > For common config case you can easily check what real differences are > between configs. > > + kernel upgrade is enough easy: just update common config (be make > oldconfig) and try to generate other configs (looking on cdiff output - > for changed/missed lines); and then look on result of 'make oldconfig' + > maybe correct some subarch-specific settings (for ex., enable new > drivers for i686/x86_64).
But in the end you have to do it for every arch, not only common config. Humans are notoriously weak when looking at changed/missed lines. > > For me, migration to new kernel (when I experimented with different > versions due to crashes with PPPoE on 4.1) takes max 10-15 minutes - > even when I switched from 4.1 to old 3.2. Which I consider very long for just a kernel upgrade. And you still have to generate the full config for every arch. But then time is not the only parameter to look at. We should analyze if there were non necessary steps involved in this process. I looked at my routine to get master in sync with new-initrd. There are considerable differences in all the config files and it requires every arch to be reconfigured. In this context the use of diff files was quite a nuisance. Of course it is possible, but IMHO not the best way. As I said, I believe I was in error when I first suggested it. cheers ET ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140 _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
