Minnowmax-3.18.txt is the list of changes over the arch defconfig. I'm not familiar with the editconfig tooling. You would be served asking in a Debian forum how to incorporate a list of CONFIG_* options into their build system.
-- Darren On 5/21/15 3:22 AM, Ferchu R wrote: > Darren: > > The Debian scripts for building the kernel fail when there is a .config > file in the root of Linux. Besides Minnowmax-3.18.txt, do you have a > list of the changes that should be made to the standard .confing to get > the same results than the merge?. As I see, maybe it would be easer if I > modify the options manually by editconfigs, but its hard to browse to > each config just by the way they appear in the .config. > > Thanks. > > 2015-05-20 18:19 GMT-05:00 Darren Hart <[email protected] > <mailto:[email protected]>>: > > > > On 5/20/15 2:38 AM, Ferchu R wrote: > > Hi: > > > > I have a couple of question regarding the steps enumerated in the wiki > > for the custom kernel: > > <http://www.elinux.org/Minnowboard:MinnowMaxLinuxKernel> > > > > Question 1. When merging Ubuntu standard .config with Minnowmax-3.18.txt > > i am getting two kinds of feedback: > > > > * Several messages like this: > > > > Value of CONFIG_SERIAL_8250_NR_UARTS is redefined by fragment > > Minnowmax-3.18.txt: > > Previous value: CONFIG_SERIAL_8250_NR_UARTS=32 > > New value: CONFIG_SERIAL_8250_NR_UARTS=4 > > > > * This kind of message just one time: > > > > scripts/kconfig/conf --alldefconfig Kconfig > > ./.tmp.config.nxkCkYRh9b:3554:warning: override: > > CPU_FREQ_DEFAULT_GOV_ONDEMAND changes choice state > > # > > # configuration written to .config > > # > > Value requested for CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE not in final > > .config > > Requested value: CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y > > Actual value: # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set > > > > The first one, looks ok to me. But I was wondering if the second is ok. > > > > These occur when the kernel config space changes from kernel version to > kernel version, as well as when your starting .config has different > values in it already. These are not problems that will prevent boot, but > you may wish to fine tune the kernel to your needs once you get it > going. > > > > I wanted to ask too, if the build has to be done with: > > > > $ make -j4 && make -j4 modules > > > > I always use $fakeroot debian/rules editconfigs for editing the config > > and then $fakeroot debian/rules binary-headers binary-generic to start > > the building process. I am afraid that if I use $make && make modules, > > some of the stuff I have done to the kernel previously could be omited. > > > > You should be able to use your debian process instead of the make && > make modules without a problem, there is nothing special there. > > > -- > Darren Hart > Intel Open Source Technology Center > _______________________________________________ > elinux-MinnowBoard mailing list > [email protected] > <mailto:[email protected]> > http://lists.elinux.org/mailman/listinfo/elinux-minnowboard > > > > > _______________________________________________ > elinux-MinnowBoard mailing list > [email protected] > http://lists.elinux.org/mailman/listinfo/elinux-minnowboard > -- Darren Hart Intel Open Source Technology Center _______________________________________________ elinux-MinnowBoard mailing list [email protected] http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
