Thanks for replying. So why do we need 'make kernel_menuconfig'? Is it only for configuring kernel option which later must be compiled not with 'make'? How then externally build kernel will be included into firmware's ' bin' file? I'm really lost. Please could you guide me a little bit more? I'd like to include some features into kernell statically. Or maybe it is easier to do it as module? On Jan 11, 2013 11:36 PM, "HeXiLeD" <[email protected]> wrote:
> You are not doing it right or saving the configuration. There is also a > difference from compiling the needed "feature" as module (m) or static > (*). > You should leave "make kernel_menuconfig" for things you cannot take > care of with just "make menuconfig" > > These are not really openwrt issues. Compiling a kernel is a linux thing > which you can probably find good documentation about how to do it from > your linux distribution of preference. > > > On 01/11/2013 02:46 PM, darius wrote: > > Hello, > > > > Simple question for those who know. I do 'make kernel_menuconfig' then > > select some needed features in kernel and then do 'make -j3' in topdir. > > After image is done, I install it on the router, but my kernel features > > are still not available. So I suppose I've done something wrong with > > kernel compilation. Could someone guide my about compiling custom kernel > ? > > > > -- > > Darius > > > > > > _______________________________________________ > > openwrt-users mailing list > > [email protected] > > https://lists.openwrt.org/mailman/listinfo/openwrt-users > _______________________________________________ > openwrt-users mailing list > [email protected] > https://lists.openwrt.org/mailman/listinfo/openwrt-users >
_______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-users
